• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Getting daily cron error via email every day

Johnny9977

Basic Pleskian
I've a problem. Since some months I'm getting this error via email every night when Plesk runs the daily crons:

Code:
flock: failed to execute /opt/alt/python35/bin/python3: No such file or directory

I have no idea how I can fix this. Please help me! Thanks.
 
Just find related cron task with this strange path and remove this cron task.
 
But which task? I've no idea which one makes the problems.

You have a cron task defined somewhere on your system, outside of Plesk. So you need to check all your cron jobs of all users.

You can list cronjobs for a certain user with "crontab -l -u <user>", for example:
Code:
crontab -l -u user1
Code:
crontab -l
(for the root user)

Also, search for "python35" or "python3" in all files in all those locations:
/var/spool/cron/
/var/spool/cron/crontabs/
/etc/crontab
/etc/cron.d/
/etc/cron.daily/
/etc/cron.weekly/
/etc/cron.hourly/
/etc/cron.monthly/

And be sure to read this: Newbie: Intro to cron
 
I've a problem. Since some months I'm getting this error via email every night when Plesk runs the daily crons:

Code:
flock: failed to execute /opt/alt/python35/bin/python3: No such file or directory

I have no idea how I can fix this. Please help me! Thanks.
Hi Johnny,
after having a similar problem after removing Imunify360 from the server, I found this and used it to clean up the rubbish Plesk never does.

sudo apt-get purge imunify360*

Have a read for yourself and see if this helps you further

Regards Scotty
 
Back
Top