- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: cronjob did not start
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
тАО06-12-2003 11:39 PM
тАО06-12-2003 11:39 PM
I had a problem with cron yesterday. A cronjob to backup the oracle database did not start. The crontab of the oracle user was not modified, and the /var/adm/cron/log file shows no errors at that time.
crontab line from oracle:
30 17 * * 1-5 $HOME/bin/db_rman_backup -l 1 -x 6 -t ARG_PR1 >> $HOME/log/ARG_PR1/onlbck.log 2>&1 || $HOME/bin/mail_backup
cron log file:
! *** cron started *** pid = 525564 Fri May 30 23:55:38 2003
! Max job limit set to 25 jobs Fri May 30 23:55:38 2003
! Log level set to 4 Fri May 30 23:55:38 2003
! *** cron exiting on signal 15 *** pid = 525564 Thu Jun 12 18:26:30 2003
! *** cron started *** pid = 525479 Thu Jun 12 18:34:44 2003
! Max job limit set to 25 jobs Thu Jun 12 18:34:44 2003
! Log level set to 4 Thu Jun 12 18:34:44 2003
(The line containing the cron exit is in the log file because I had to reboot the server at 18:20 - This has nothing to do with the cron problem)
We're running tru64 V5.1a
Any help would be appreciated.
Thanks,
Tim Martens
Solved! Go to Solution.
- Tags:
- crontab
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-13-2003 05:18 AM
тАО06-13-2003 05:18 AM
Re: cronjob did not start
does uerf report any errors prior to the cronjob scheduled start time i.e. disk space errors etc.?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-13-2003 06:02 AM
тАО06-13-2003 06:02 AM
Re: cronjob did not start
Is this a new script or something that has worked for some time?
Did this only happen once?
The the log file you append to get updated?
Is the time and date correct on the machine?
Are all files that need to be executable exectuable?
You may want to put your script in debug mode (ksh -x) and run it that way.
What shell does your script use?
Hope this helps,
Christian Klein
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-13-2003 08:32 AM
тАО06-13-2003 08:32 AM
Re: cronjob did not start
Does your cron deamon run?
Is this new task for cron or you alredy run this in the past?
Caesar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-14-2003 06:03 AM
тАО06-14-2003 06:03 AM
Solution(I had an experience. Together they are working ... strange!)
I would try to submit some jobs to cron (for example, touch /tmp/myfile)
and start/stop cron - it's better to do:
/sbin/rc3.d/S57cron stop
/sbin/rc3.d/S57cron start
In case You will not resolve issue withing one day, it's possible to run:
sleep
(Just to avoid running backup manually at 3.00 AM)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-15-2003 11:53 PM
тАО06-15-2003 11:53 PM
Re: cronjob did not start
We had a problem with cron on all 3 members of our cluster.
uerf didn't show any errors. There were NO modifications (not in the cronjobs, not in the ksh script ).
Stopping and starting the cron daemon did do the job. (It's still strange that all 3 cron daemons on all 3 members of the cluster 'hang' without any errors ).
Hopefully it is a one-time problem.
Thanks all for the response.
Tim.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-18-2003 08:25 AM
тАО06-18-2003 08:25 AM
Re: cronjob did not start
This explains the warning you received.
Increase it and restart the cron daemon.
Hope, I could help
Michael Schulte