TIPS Cron Jobs

[womble1]

Hi I am trying to get a Cron job to run everyday to restart asterisk
I have set a cron job to run am portal restart every day at midnight but it fails to run on it's own, if I run the job manually it's fine... Cron is running and I can't see why it's falling...

 

[wardmundy]

What does the cron string look like??

 

[womble1]

amportal restart, it runs manually i.e. if I set a cron job for it and say "run Now"

 

[womble1]

any idea ?

 

[wardmundy]

That's not the proper syntax for a cron job. Look in /etc/crontab for examples.

 

[womble1]

But it runs, I've not added it to cron tab I put it in scheduled cron jobs in webmin

 

[wardmundy]

Are you using full path to amportal? /usr/local/sbin/amportal

 

[womble1]

It runs without it in webmin scheduled commands

 

[wardmundy]

I thought you said it wouldn't run on its own??

 

[womble1]

If you hit the save and run now button it runs fine and you see the output

 

[jerrm]

The environment inside webmin is not the same as cron.

Try what @wardmundy suggests instead of debating it. 99.999999% sure he is right.

 

[womble1]

Not sure what he is suggesting, I'm using the cron plugin in webmin, in there there are PBX Crins as well

 

[jerrm]

In webmin, enter "/usr/local/sbin/amportal restart" instead of "amportal restart"

 

[wardmundy]

If you hit the save and run now button it runs fine and you see the output

Problem is that you're running as root with your root-enabled path when you run it inside WebMin.

 

[womble1]

In webmin, enter "/usr/local/sbin/amportal restart" instead of "amportal restart"

So I have set it as the above it ruins manually will see if it runs automatically... thanks...

 

[wardmundy]

I'm not familiar with what WebMin does under the covers, but here's the deal. For amportal to run successfully, it has to be running with either root or asterisk privileges. If it fails, then you need to set it up under /etc/crontab following the examples in that file.

 

[Dave Gray]

As a safety measure, cron uses an abbreviated path in its environment when it runs an entry. You always want to use a full path for the command in a cron entry, so as to not go through this mess.

As an exercise, try setting a cron job with something like "env > /tmp/env.txt" to see what the cron'd environment looks like. It's pretty empty. Be aware that anything that you're running, that depends on environment variables will not see them, unless you set them as part of the command.