Hi folks we desactivated the fautly module that worked a bit, but we get another crash this nigth, with other modules with category selection, i will determine them exactly)
it seem that your code as issue with large number or article and make crash the server
we need fix urgently
Here is the other fautly modules and the SQL request :
Briks Module
SELECT a.id,a.title,a.alias,a.introtext,a.fulltext,a.checked_out,a.checked_out_time,a.catid,a.created,a.created_by,a.created_by_alias,a.modified,a.modified_by,CASE WHEN a.publish_up IS NULL THEN a.created ELSE a.publish_up END AS publish_up,a.publish_down,a.images,a.urls,a.attribs,a.metadata,a.metakey,a.metadesc,a.access,a.hits,a.featured,a.language,LENGTH(a.fulltext) AS readmore,a.ordering,fp.featured_up,fp.featured_down,CASE WHEN c.published = 2 AND a.state > 0 THEN 2 WHEN c.published != 1 THEN 0 ELSE a.state END AS state,c.title AS category_title,c.path AS category_route,c.access AS category_access,c.alias AS category_alias,c.language AS category_language,c.published,c.published AS parents_published,c.lft,CASE WHEN a.created_by_alias > ' ' THEN a.created_by_alias ELSE ua.name END AS author,ua.email AS author_email,uam.name AS modified_by_name,parent.title AS parent_title,parent.id AS parent_id,parent.path AS parent_route,parent.alias AS parent_alias,parent.language AS parent_language
FROM s8c9k_content AS a
LEFT JOIN s8c9k_categories AS c ON c.id = a.catid
LEFT JOIN s8c9k_users AS ua ON ua.id = a.created_by
LEFT JOIN s8c9k_users AS uam ON uam.id = a.modified_by
LEFT JOIN s8c9k_categories AS parent ON parent.id = c.parent_id
LEFT JOIN s8c9k_content_frontpage AS fp ON fp.content_id = a.id
WHERE a.access IN (1,5,7) AND c.access IN (1,5,7) AND c.published = 1 AND a.state = 1 AND a.catid IN (263,72,73,102,90,91,75,76,92,93,94,95,96,98,99,101,103) AND a.created_by IN (62,724) AND (a.publish_up IS NULL OR a.publish_up <= '2023-07-11 23:56:35') AND (a.publish_down IS NULL OR a.publish_down >= '2023-07-11 23:56:35')
ORDER BY a.created DESC LIMIT 4;
Category 263,72,73,102,90,91,75,76,92,93,94,95,96,98,99,101,103
263 = Cuisine
72 = Cinéma
73 = Livres
102 = Musiques
90 = Actualités internationale
91 = Actualités Française
75 = Tutorial
76 = Astuces Logiciels
92 = Brèves
93 = Sécurité
94 = Jeux vidéo
95 = Actualités scientifiques
96 = Divers
98 = Actualités Higth Tech
99 = Dossiers
101 = NewsFlash
103 = Twilligth Zone
Slide midle Modules
SET timestamp=1689120524;
SELECT a.id,a.title,a.alias,a.introtext,a.fulltext,a.checked_out,a.checked_out_time,a.catid,a.created,a.created_by,a.created_by_alias,a.modified,a.modified_by,CASE WHEN a.publish_up IS NULL THEN a.created ELSE a.publish_up END AS publish_up,a.publish_down,a.images,a.urls,a.attribs,a.metadata,a.metakey,a.metadesc,a.access,a.hits,a.featured,a.language,LENGTH(a.fulltext) AS readmore,a.ordering,fp.featured_up,fp.featured_down,CASE WHEN c.published = 2 AND a.state > 0 THEN 2 WHEN c.published != 1 THEN 0 ELSE a.state END AS state,c.title AS category_title,c.path AS category_route,c.access AS category_access,c.alias AS category_alias,c.language AS category_language,c.published,c.published AS parents_published,c.lft,CASE WHEN a.created_by_alias > ' ' THEN a.created_by_alias ELSE ua.name END AS author,ua.email AS author_email,uam.name AS modified_by_name,parent.title AS parent_title,parent.id AS parent_id,parent.path AS parent_route,parent.alias AS parent_alias,parent.language AS parent_language
FROM s8c9k_content AS a
LEFT JOIN s8c9k_categories AS c ON c.id = a.catid
LEFT JOIN s8c9k_users AS ua ON ua.id = a.created_by
LEFT JOIN s8c9k_users AS uam ON uam.id = a.modified_by
LEFT JOIN s8c9k_categories AS parent ON parent.id = c.parent_id
LEFT JOIN s8c9k_content_frontpage AS fp ON fp.content_id = a.id
WHERE a.access IN (1,5,7) AND c.access IN (1,5,7) AND c.published = 1 AND a.state = 1 AND a.catid IN (90,91,95,96,98,99) AND (a.publish_up IS NULL OR a.publish_up <= '2023-07-11 23:56:37') AND (a.publish_down IS NULL OR a.publish_down >= '2023-07-11 23:56:37')
ORDER BY a.hits DESC LIMIT 50;
90 = Actualités internationale
91 = Actualités Française
95 = Actualités scientifiques
96 = Divers
98 = Actualités Higth Tech
99 = Dossiers
who CRASH, and the team support are woke up in the middle of the nigth because the SQL server as crashed and that as crashed server of OTHER customer TOO !
We need a FIX !
Thanks,
folamour
Hello,
After reviewing the queries you provided, it seems that they are originating from the Joomla core, so there are no unexpected or unusual queries.
The issue you are experiencing could be due to a full disk on your server. Please ensure that you have enough free disk space to handle the queries and other operations.
Another possible cause could be the queries requiring excessive memory. Increasing the memory size for MySQL might be a solution. You can start by looking at parameters such as key_buffer_size, sort_buffer, read_buffer, and table_cache. Additionally, consider checking innodb_buffer_pool_size .
Hope this help.
There are not coming from the joomla core ! its your module ! if we disable the module crash stop, check the category listed in the fautly query (who came again again and again ) they are listed in the selection of the module !
We need fix, we will archive 5K article on monday and give another try
ok, i've a meeting in 30mn will be back in 1hour will give you the admin and the backdoor,
thanks a lot, the host want to fire us because of these crash
kind regards,
f.
there is no Cpanel @ hostpoint
Also the issue is random we have archived 5K articles on the 15k to reduce the load of the query
thanks
folamour
Hi,
After further investigation, i think issue might not because of ja good template. Ja good layouts for mod_articles_category only use joomla module data, no extra db query. You can turn on the module, delete all ja good layout content and monitor this issue again. All layouts you can find at: /templates/ja_good/html/mod_articles_category
Because of your site have a mount of articles, i prefer mysql needs more memory. I made some tests and the result is:
SELECT @@key_buffer_size/1024/1024
128.00000000
SELECT @@max_allowed_packet/1024/1024
64.00000000
SELECT @@sort_buffer_size/1024/1024
8.00000000
SELECT @@read_buffer_size/1024/1024
2.00000000Could you ask db team to increase key_buffer_size, max_allowed_packet, sort_buffer_size and read_buffer_size to 250M?
what this mean i have to delete ja good ? and ask to increase ? without ja good the site don't crash
I call them by phone to ask
folamour
Hi,
All queries you sent come from module mod_articles_category. This is a module of joomla core. Ja Good support some layout override for this module. To test out ja good makes your site crash or not, you can open all override layouts of module mod_articles_category, empty them and monitor template ja good again. The folder is /templates/ja_good/html/mod_articles_category.
Hope this clear.
ok that has to be seen by the level 2 support at hostpoint, but the engineer will be back tomorrow, so i get back in touch with you when he will be back
thanks you a lot for your support because our website is at risk and its 15 year of work,
kind regards,
f.
i'm sorry i dont understood that :
you can open all override layouts of module mod_articles_category, empty them and monitor template ja good again. The folder is /templates/ja_good/html/mod_articles_category.