- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: Cron job started 3 hours later
Operating System - Tru64 Unix
1748237
Members
3543
Online
108759
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-05-2006 11:08 PM
тАО07-05-2006 11:08 PM
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
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
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-06-2006 12:46 AM
тАО07-06-2006 12:46 AM
Solution
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
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-06-2006 12:57 AM
тАО07-06-2006 12:57 AM
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.
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
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP