CRON Spontaneously Shuts Itself Down

System:
The system is an HP 715 running HPUX 10.20

Background:
From time to time and seemingly without reason, CRON will shut itself down. A look at the log file reveals that its last action was to attempt to execute a job in the crontab at an odd time. I've deactivated, then reactivated the crontab which seems to have helped at least for the time being. The problem with this solution is that I've done this before as a quick fix, but the problem resurfaces after a time.

Question:
What could I check to gain a little more visibility into what CRON is doing and when, and how can I prevent CRON from shutting itself down again? What could affect CRON to force it down?

pdouglasAsked:
Who is Participating?
 
moduloConnect With a Mentor Commented:
Finalized as proposed

modulo

Community Support Moderator
Experts Exchange
0
 
cymru_ladCommented:
What do you mean by an 'odd time' ?  Also what cron entry was it trying to start ?

As a quick check, check that disk space is available in /var and whether any messages are being logged in /var/adm/syslog/syslog.log.  If possible please post the tail entry of the cron log file /var/adm/cron/log.

Mike
0
 
ecwCommented:
Don't put crap in /var/spool/cron/crontab dir.  Only proper crontabs should be here, not backups or the usual dross people leave.  I've seen cron die quite often on HP boxes when people have left crap lying around.
0
[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

 
pdouglasAuthor Commented:
More Info:

- The system is running CDE (Common Desktop Environment)
- Disk space in /var is at 61%
- Only 1 crontab exists in the /var/spool/cron/crontabs dir.
- The /var/adm/cron/log file does not contain anything unusual.
- The /var adm/syslog/syslog.log *does* contain some odd [or at least I believe they're odd] entries:

     DTSESSION: pmauthenticate status=9
     DTSESSION: pmauthenticate status=0
     inetd[585]: rpc.cmsd/udp: Died on signal 11



0
 
jlmsCommented:
Can't you put the crontab file here?
0
 
pdouglasAuthor Commented:
jlms,

I can't post the crontab file here since the system from which it comes is security sensative.
0
 
TalmashCommented:
type :

crontab -l
to verify if the machine you use for cron job
is not occupied yet .

crontab -r : erase existing cron job from machine :

tip :

you can use those 2 commands while your cron-file .

Talmash
0
 
cymru_ladCommented:
rpc.cmsd is the CDE Calender Manager Service.  I'd check out the latest patches for this and the cron process.  Patches are available for download from the HP website.

Mike
0
 
tfewsterCommented:
I don't know if you ever solved this problem, but reading this one and
http://www.experts-exchange.com/Operating_Systems/Unix/Q_20290519.html

reminded me of a problem I once saw.

A crontab file automagically reset itself once a day to a "standard" setup, destroying any changes I had made to it. The timestamp on /var/spool/cron/crontabs/username corresponded with the time of a cron job IN the crontab, so it was just a matter of tracing what the cron job did. (in fact, it started a ServiceGuard package, which executed other scripts, one of which was `crontab < /long/and/obscure/path/to/model/crontab` so it took a while to trace it :-)

If your system is doing something similar, it may be that the act of refreshing the crontab is causing cron to hang. Even so, patching cron is recommended.
0
 
tfewsterCommented:
No comment has been added lately, so it's time to clean up this TA.
I will leave a recommendation for this question in the Cleanup topic area as follows:
- PAQ & refund points

Please leave any comments here within the next 7 days

PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER !

tfewster (I don't work here, I'm just an Expert :-)
0
All Courses

From novice to tech pro — start learning today.