• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Watchdog Cronjobs Errors - Plesk 12.5.x

Elompenta

Regular Pleskian
After a fresh installation of Plesk 12.5 on Debian 8 i get the following crontab errors every night.
Any Idea why the binaries not exist?

Cron <root@hostname> /opt/psa/libexec/modules/watchdog/cp/clean-events
-> /bin/sh: 1: /opt/psa/libexec/modules/watchdog/cp/clean-events: not found

Cron <root@hostname> /opt/psa/libexec/modules/watchdog/cp/pack-sysstats day
-> /bin/sh: 1: /opt/psa/libexec/modules/watchdog/cp/pack-sysstats: not found

Cron <root@hostname> /opt/psa/libexec/modules/watchdog/cp/clean-sysstats
-> /bin/sh: 1: /opt/psa/libexec/modules/watchdog/cp/clean-sysstats: not found
 
Hi Elompenta,

did you consider to re-install the watchdog module, to see if this already solves your issue?

Example commands:
Code:
/usr/local/psa/admin/bin/autoinstaller --select-product-id plesk --select-release-current --remove-component watchdog
/usr/local/psa/admin/bin/autoinstaller --select-product-id plesk --select-release-current --install-component watchdog
 
@UFHH01
The same messages again - remove and reinstall doesnt help.
Any Ideas?

I have this Errors only in Debian 8 installation, not in Debian 7 Setups
 
Do you have these files there?

/opt/psa/libexec/modules/watchdog/cp/clean-sysstats
/opt/psa/libexec/modules/watchdog/cp/clean-events

What is output of

# crontab -l

?
 
Do you have these files there?
/opt/psa/libexec/modules/watchdog/cp/clean-sysstats
/opt/psa/libexec/modules/watchdog/cp/clean-events

Yes, boith files are available and executable

root@<host>:~# ls -lah /opt/psa/libexec/modules/watchdog/cp/clean-sysstats
-rwxr-xr-- 1 root psaadm 534 Aug 26 15:22 /opt/psa/libexec/modules/watchdog/cp/clean-sysstats
root@<host>:~#
root@<host>:~#
root@<host>:~# ls -lah /opt/psa/libexec/modules/watchdog/cp/clean-events
-rwxr-xr-- 1 root psaadm 502 Aug 26 15:22 /opt/psa/libexec/modules/watchdog/cp/clean-events


What is output of

# crontab -l

root@<host>:~# crontab -l
##MAILTO=""
47 23 * * * /usr/sbin/ntpdate -b -s ntp.oberberg.net


I will attach the global crontab

root@yhost>:~# cat /etc/crontab
# /etc/crontab: system-wide crontab
# Unlike any other crontab you don't have to run the `crontab'
# command to install the new version when you edit this file
# and files in /etc/cron.d. These files also have username fields,
# that none of the other crontabs do.

SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

# m h dom mon dow user command
17 * * * * root cd / && run-parts --report /etc/cron.hourly
25 6 * * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
47 6 * * 7 root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
52 6 1 * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly )
#

no modifications here - thanks for your help
 
Back
Top