Cron job: [Errno 2] No such file or directory

cronmediatemplepython

On a Mediatemple gridserver, I'm trying to run this by a cron set in the control panel:

usr/bin/python /home/xxxxx/html/sitemap_gen.py --config=/home/xxxxx/html/config.xml

But I get the error "python: can't open file '/home/95809/html/sitemap_gen.py': [Errno 2] No such file or directory." But the files are there. MT requires the paths, and there is no difference in the error without the paths.

I can run it manually from ssh:

python sitemap_gen.py --config=config.xml

and have chmoded the script for execution.

Is there a different way to run this script that will work?

MT doesn't have direct examples of python scripts run by cron, and doesn't offer support.

Is there a way to wrap the script in another script – like a bash script – to get away from having to include the paths or invoke python, which I think might be the problem?

Best Answer

Two things i would suggest:

Try to run the command manually on the command line if you have access
Verify that your user has execute permissions on the file /home/xxxxx/html/sitemap_gen.py

EDIT: oh duh ... try using the full path to python so if the python executable is in /usr/bin it would be : /usr/bin/python /home/xxx/html/sitemap_gen.py <blah blah blah>

Related Solutions

Cron – How to Prevent Duplicate Cron Jobs Running

There are a couple of programs that automate this feature, take away the annoyance and potential bugs from doing this yourself, and avoid the stale lock problem by using flock behind the scenes, too (which is a risk if you're just using touch). I've used lockrun and lckdo in the past, but now there's flock(1) (in newish versions of util-linux) which is great. It's really easy to use:

* * * * * /usr/bin/flock -n /tmp/fcj.lockfile /usr/local/bin/frequent_cron_job

Cron – script works manually but not in cron job

There's an obvious mistake in your cron line: you redirect error output to /dev/null. Don't do this, and look at your mail to see what went wrong.

A common problem with cron jobs is that they get a very limited environment: your .profile is not read. You may need to define some environment variables for your script to run.

ADDED: You did:

cp -rf /opt/rrdtool-1.4.4/lib/perl/5.8.8/i386-linux-thread-multi/* /usr/lib/perl/site_perl

Bad idea! You should not put your own files in /usr (outside /usr/local). That area is reserved to the package manager. Sure, it's easy now, but you will run into trouble tomorrow (for example when you upgrade rrdtool), and it'll be hard to debug then.

Instead, do what people have been recommending and define the necessary environment variables in your script (or source ~/.profile); you need PERL5LIB (and perhaps others).

Best Answer

Related Solutions

Cron – How to Prevent Duplicate Cron Jobs Running

Cron – script works manually but not in cron job

Related Topic