C
Capa
Guest
Parallels Technology Network
I hope, that guys know how to fix it !!
I hope, that guys know how to fix it !!
-bash-3.2# /usr/local/psa/libexec/modules/watchdog/cp/pack-sysstats day
ERROR: WDExc
Error occurred while processing database query: 'MySQL query failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'group by service_id, type, round(unix_timestamp(time) / 200, 0) having count(val' at line 3'
0: wdlib.php:1088
wd__db_query(string 'select service_id, type, unix_timestamp(min(time)) as min_time, unix_timestamp(max(time)) as max_time, avg(value) as avg
from module_watchdog_sys_stat where
group by service_id, type, round(unix_timestamp(time) / 200, 0) having count(value) > 1 limit 10000;')
1: pack-sysstats:63
pack_statistics(integer '200', boolean false, boolean false)
2: pack-sysstats:44
ERROR: WDExc
Error occurred while processing database query: 'MySQL query failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'group by service_id, type, round(unix_timestamp(time) / 200, 0) having count(val' at line 3'
0: /opt/psa/admin/plib/modules/watchdog/wdlib.php:1050
wd__db_query(string 'select service_id, type, unix_timestamp(min(time)) as min_time, unix_timestamp(max(time)) as max_time, avg(value) as avg
from module_watchdog_sys_stat where
group by service_id, type, round(unix_timestamp(time) / 200, 0) having count(value) > 1 limit 10000;')
1: /opt/psa/libexec/modules/watchdog/cp/pack-sysstats:68
pack_statistics(integer '200', boolean false, boolean false)
2: /opt/psa/libexec/modules/watchdog/cp/pack-sysstats:49
note that the "where" statement seems incomplete.
We contacted our hosting reseller (Peer1) to escalate the issue with SWSoft. Here is the response we received:
According to Parallels this is a known issue and they are planning on fixing the issue during the next Plesk update. Unfortunately they did not provide a time frame for the next update.
They did provide the following workaround:
---
As a workaround you can just comment out corresponding lines in cron jobs configuration, so no error notifications will be sent to you.
You should comment all pack-sysstats* lines, and in the end get this:
cat /var/spool/cron/root
1,16,31,46 * * * * /usr/local/psa/admin/sbin/backupmng >/dev/null 2>&1
0 1 * * 1 /usr/local/psa/libexec/modules/watchdog/cp/secur-check
0 1 * * 1 /usr/local/psa/libexec/modules/watchdog/cp/send-report weekly
10 1 * * * /usr/local/psa/libexec/modules/watchdog/cp/clean-sysstats
#15 1 * * * /usr/local/psa/libexec/modules/watchdog/cp/pack-sysstats day
#15 1 * * 1 /usr/local/psa/libexec/modules/watchdog/cp/pack-sysstats week
#15 1 1 * * /usr/local/psa/libexec/modules/watchdog/cp/pack-sysstats month
#15 1 1 * * /usr/local/psa/libexec/modules/watchdog/cp/pack-sysstats year
20 1 * * * /usr/local/psa/libexec/modules/watchdog/cp/clean-events
0 3 * * 7 /usr/local/psa/libexec/modules/watchdog/cp/clean-reports
---