Cron runs only manual on Centos

ASTRAPI · 11-24-2014, 10:31 PM

Hi

I use a cron on Centos to run a backup script:

Code:

5 6 * * * /script/backup.sh

So at 06:05 the cron should start...

Checking by command "date" i have the same time and date with the server and ll done as root on the server....

The cron is not running and from the logs i can't see any related message:

Code:

Nov 25 05:25:01 server CROND[29894]: (root) CMD (/usr/local/rtm/bin/rtm 10 > /dev/null 2> /dev/null)
Nov 25 05:26:01 server CROND[29964]: (root) CMD (/usr/local/rtm/bin/rtm 10 > /dev/null 2> /dev/null)
Nov 25 05:27:01 server CROND[30016]: (nodequery) CMD (bash /etc/nodequery/nq-agent.sh > /etc/nodequery/nq-cron.log 2>&1)
Nov 25 05:27:01 server CROND[30015]: (root) CMD (/usr/local/rtm/bin/rtm 10 > /dev/null 2> /dev/null)
Nov 25 05:27:41 server crontab[30674]: (root) BEGIN EDIT (root)
Nov 25 05:27:47 server crontab[30674]: (root) END EDIT (root)
Nov 25 05:28:01 server CROND[30683]: (root) CMD (/usr/local/rtm/bin/rtm 10 > /dev/null 2> /dev/null)
Nov 25 05:29:01 server CROND[30733]: (root) CMD (/usr/local/rtm/bin/rtm 10 > /dev/null 2> /dev/null)

No logs at 06:05 at all....

When i try to run it using:

cd /script
./backup.sh

Is running and all are great without any errors at all...

Any ideas?

Thanks

ilesterg · 11-25-2014, 12:16 AM

Count the number of ALL processes (which kicked off using cron) in ps which are running currently. I had this issue before when there were 100 process instances of 1 other script (runs every 10 minutes), which prevented ALL OTHER cron jobs to kick off. Maybe you also encounter this? though mine was in AIX.

TenTenths · 11-25-2014, 02:59 AM

Just because your script runs fine when you manually run it does NOT mean it will run correctly as a cron job.

When a job is run from the cron it does not necessarily pick up the whole path or shell environment variables that the user shell session would.

If your script is a bash script then try set -x at the start of your script and redirect the output in the cron job:

Code:

5 6 * * * /script/backup.sh > /script/backup.log

That may give you some clues.

ASTRAPI · 11-25-2014, 12:01 PM

Do you mean chown +x ? If yes then i done it already....

If not how can i do this -x ?

The crazy thing is taht i have the exact same script and path to aother server and with the same cron command it runs great ....

Thanks

TenTenths · 11-25-2014, 12:08 PM

Quote:

Originally Posted by ASTRAPI

Do you mean chown +x ?

No, if I had meant chown +x (which is pointless, did you mean chmod +x?) then I would have said so.

Add set -x as a separate line in your script, after your #!/blah/blah line and it will cause your script to show you each line as its executing, essential for debugging/troubleshooting.

ASTRAPI · 11-25-2014, 04:03 PM

Now it works thanks