• 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
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

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