• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Problems with crontabs

H.W.B

Regular Pleskian
Hello,

After the 19th of april my crontabs stop to work.
I didn't change anything but there are microupdates from plesk installed

I use /usr/bin/wget -O /dev/null 'http://<path>/cron.php'

I got a -: /usr/bin/wget: No such file or directory error

But when i manually enter the command everything is working ok.

This is already used for 5 Years, but stops working then.
Also other scheduled task don't run

There seems to be a problem.
Can you help me

Henk
 
Hello,

After the 19th of april my crontabs stop to work.
I didn't change anything but there are microupdates from plesk installed

I use /usr/bin/wget -O /dev/null 'http://<path>/cron.php'

I got a -: /usr/bin/wget: No such file or directory error

But when i manually enter the command everything is working ok.

This is already used for 5 Years, but stops working then.
Also other scheduled task don't run

There seems to be a problem.
Can you help me

Henk

http://forum.parallels.com/showthread.php?109965-how-do-I-get-crontab-to-work-!
 
Hello,

Just found out what the problem was.

For some reason when you edit the scheduled task in Plesk, there is a line added :

SHELL=/usr/local/psa/bin/chrootsh

I think this is done by plesk.
But that line is preventing the commands i use in the cron-tabs.
So deleting this line (or put ## infront of it) is solving the problem.

Henk
 
Back
Top