• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

ERROR: WDExc (PLESK 8.6)

Parallels Technology Network

I hope, that guys know how to fix it !!
 
I have the same problem on 9.5.3:

-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
 
Clearly this error is caused by the date change to 2011. Perhaps the format of unix_timestamp has changed now that it's 41 years since unix zero time (1970) ?

Come on Parallels - wake up ! This must be a trivial SQL fix...
 
Same Problem here, psa 9.3 on CentOS 5.4.

Should i open a Support Ticket ?

Regards & A happy new year :)
 
Same problem here for Plesk 8.6 on x86 servers within Virtuozzo. Plesk 8.6 and Plesk 9.5 on servers with x86_64 version of CentOS 5 seems not to be affected.
 
ERROR: WDExc (10.0) /usr/local/psa/libexec/modules/watchdog/cp/pack-sysstats week

Error found from CRON:
/usr/local/psa/libexec/modules/watchdog/cp/pack-sysstats week

Error just started on v 10


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) / 1800, 0) having count(va' at line 3'

0: wdlib.php:1089
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) / 1800, 0) having count(value) > 1 limit 10000;')
1: pack-sysstats:63
pack_statistics(integer '1800', boolean false, boolean false)
2: pack-sysstats:44
 
Last edited:
(yes, started at midnight, Jan. 1, 2011)

I also noticed that my WATCHDOG module think's the date is Dec. 31, 1969.

(see attached screenshot of watchdog email)
 

Attachments

  • watchdog-screenshot.png
    watchdog-screenshot.png
    50.4 KB · Views: 35
Same Error here in 8.6

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.
 
I am wondering if there still are some technical personal of Parallels left, now mostly all Russion technicians have left. This takes too long to be answered or there will be sent a patch or something.
 
Response from SWSoft (via Reseller)

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
---
 
Four (4) Plesk 8.6.0 Servers On Redhat with the issue. (Subscribed)
 
Ditto

Every server that has Watchdog activated is generating this error. Plesk 9.5.3. Happy New Year...
 
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
---

What does pack-sysstats actually do? Is the action of these scripts not working going to cause any problems further down the line?

Rob
 
Hi all and (some late) HNY!

I'm on vacation und just checked my last days emails...
Seems that I have a similar Problem on my host running Plesk Panel 9.5.3.
My daily watchdog emails do show some strange date behaviour in the mails subject,
and also the weekday seems to be one day "behind".
The last correct looking mail has subject:

"Watchdog daily report Dez 30, 2010 (Donnerstag) on [$hostname]"

This mail was sent on Friday, Dec 31st @1:00 AM
The next mail sent on Saturday, Jan 1st @1:00 AM has the subject:
"Watchdog daily report Dez 31, 110 (Donnerstag) on [$hostname]"

As you can see, the weekday is the same as in the former mail...
The next mails do have the subjects:
"Watchdog daily report Jan 1, 111 (Freitag) on [$hostname]"
"Watchdog daily report Jan 2, 111 (Samstag) on [$hostname]"
"Watchdog daily report Jan 3, 111 (Sonntag) on [$hostname]"

BTW: I also have an email from yesterday about the Plesk Web Server beeing down/restartet,
where all date related information looks ok. Mailcontent is:
"The Plesk Web Server service on host [$hostname] is down.
The problem was discovered on Jan 3, 2011 03:25 ."


Addendum:
Host is a VPS (Xen based) running Debian Lenny (5.0.7), 64 Bit version with all OS Patches applied.

Regards,
Christian
 
Last edited by a moderator:
Same problem on our 4 Plesk servers:
2x 9.5.2, 2x 9.3.0, all on Debian Lenny

Cheers
kradi
 
WDExc error - (Plesk 9.3)

Same problem here....

All Virtuozzo VPS's with Plesk 9.3 and watchdog activated affected....
 
Back
Top