System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

Cron job started 3 hours later

SOLVED
Go to solution
Vladimir Fabecic
Honored Contributor

Cron job started 3 hours later

I had very strange problem. Cron job (from root crontab) started 3 hours later. It is a backup script that also run database shutdown and startup so database was down in the morning. Have no idea why. There is no single error in any log.
And everything is running OK.
Did anzbody have simular problem?
It is two node TRU64 cluster v 5.1B-3.
By the way, does anybody know a good way how can customer (that do not know much about unix) stop running cron job without destroying crontab file.
Regards
In vino veritas, in VMS cluster
2 REPLIES
Ivan Ferreira
Honored Contributor
Solution

Re: Cron job started 3 hours later

I had a similar problem when changed the timezone to reflect the DST. After that, the cron jobs did not start at the right time. It seems that the Tru64 crond does not handles DST. I had to restart cron and syslog to get the current time.

Your customer can stop running cron by using:

Save your current cron
crontab -l > $HOME/crontab.list

Remove the cron
crontab -r

If he wants to enable cron again, read the file:

crontab $HOME/crontab.list
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Vladimir Fabecic
Honored Contributor

Re: Cron job started 3 hours later

You were right. Nobody changed time zone, but simular.
The problem was in their local NTP server. They have some maintaince on that and had some problem, so servers got wrong time information.
I restarted NTP and cron on unix systems and everything is OK now.
Thants a lot, Ivan.
About crontab: I also recomended this, but not sure if it can stop running job.
In vino veritas, in VMS cluster