Support

Hello,
I have a huge problem with the performance of the mysql database. The research why this is so in the review of the mysql process list brought to light:

Querying the table sjt1i_admintools_scanalerts seems to be responsible for the very high CPU load. Below you will find the process list output. The queries do not appear to stop because there are more and more. All that remains for me is to restart mysql.

What is the reason? How can this be turned off?



+------+----------------+-----------------+----------------------+---------+------+----------------+------------------------------------------------------------------------------------------------------+----------+
| Id | User | Host | db | Command | Time | State | Info | Progress |
+------+----------------+-----------------+----------------------+---------+------+----------------+------------------------------------------------------------------------------------------------------+----------+
| 17 | ispp_bandaemon | localhost | ispprotect_bandaemon | Sleep | 2 | | | 0.000 |
| 799 | ispconfig | localhost:33272 | dbispconfig | Sleep | 28 | | | 0.000 |
| 800 | ispconfig | localhost:33274 | dbispconfig | Sleep | 269 | | | 0.000 |
| 1432 | ispconfig | localhost | dbispconfig | Sleep | 23 | | | 0.000 |
| 1435 | usr201 | localhost | db204 | Sleep | 12 | | | 0.000 |
| 1465 | usr201 | localhost | db204 | Query | 1 | Sorting result | SELECT *
FROM `sjt1i_admintools_scanalerts`
WHERE `path` = 'build/plugins/system/core/classes/scss/F | 0.000 |
| 1468 | usr201 | localhost | db204 | Query | 1 | Sorting result | SELECT *
FROM `sjt1i_admintools_scanalerts`
WHERE `path` = 'libraries/fof30/include.php'
ORDER BY `s | 0.000 |
| 1505 | usr201 | localhost | db204 | Query | 1 | Sorting result | SELECT *
FROM `sjt1i_admintools_scanalerts`
WHERE `path` = 'build/template/html/com_content/archive/ | 0.000 |
| 1506 | usr201 | localhost | db204 | Query | 0 | Sorting result | SELECT *
FROM `sjt1i_admintools_scanalerts`
WHERE `path` = 'libraries/fof/form/field/email.php'
ORDE | 0.000 |
| 1507 | usr201 | localhost | db204 | Query | 1 | Sorting result | SELECT *
FROM `sjt1i_admintools_scanalerts`
WHERE `path` = 'layouts/libraries/cms/html/bootstrap/end | 0.000 |
| 1510 | usr201 | localhost | db204 | Query | 0 | Sorting result | SELECT *
FROM `sjt1i_admintools_scanalerts`
WHERE `path` = 'build/template/html/layouts/joomla/conte | 0.000 |
| 1511 | usr201 | localhost | db204 | Query | 1 | Sorting result | SELECT *
FROM `sjt1i_admintools_scanalerts`
WHERE `path` = 'layouts/joomla/content/icons/email.php'
| 0.000 |
| 1512 | usr201 | localhost | db204 | Query | 0 | Sorting result | SELECT *
FROM `sjt1i_admintools_scanalerts`
WHERE `path` = 'layouts/joomla/form/field/range.php'
ORD | 0.000 |
| 1513 | usr201 | localhost | db204 | Query | 2 | Sorting result | SELECT *
FROM `sjt1i_admintools_scanalerts`
WHERE `path` = 'libraries/src/Toolbar/Button/SliderButto | 0.000 |
| 1514 | usr201 | localhost | db204 | Query | 1 | Sorting result | SELECT *
FROM `sjt1i_admintools_scanalerts`
WHERE `path` = 'build/template/html/layouts/joomla/conte | 0.000 |
| 1515 | usr201 | localhost | db204 | Query | 1 | Sorting result | SELECT *
FROM `sjt1i_admintools_scanalerts`
WHERE `path` = 'libraries/fof/less/formatter/joomla.php' | 0.000 |
| 1516 | usr201 | localhost | db204 | Query | 0 | Sorting result | SELECT *
FROM `sjt1i_admintools_scanalerts`
WHERE `path` = 'libraries/src/Toolbar/Button/ConfirmButt | 0.000 |
| 1517 | root | localhost | | Query | 0 | init | show processlist | 0.000 |
+------+----------------+-----------------+----------------------+---------+------+----------------+------------------------------------------------------------------------------------------------------+----------+

Hello Davide,
thank you for your help.
After a long search and research I found out that the scan of the files by /cli/admintools-filescanner.php is the cause. I switched off the cron job with the file scanner yesterday and had no performance problems or open queries this morning.

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.