topic Re: Cron in Operating System - HP-UX

Cron

Claire Daelman — Mon, 08 Jul 2002 18:01:47 GMT

We have this alarm on a server S16K-A, Hp-UX 9000, 11.11:
Cron command of root with pid XXX failed

I have no more information, this alarm occured regulary but I can't find with wich cron command it's linked.

Thanks,
Claire

Re: Cron

A. Clay Stephenson — Mon, 08 Jul 2002 18:04:30 GMT

The first thing to do is login as root and do a crontab -l. This will list all of root's crontab entries to stdout. With any luck, there will be only a few entries (maybe even one) with matching time specifications.

Re: Cron

Claire Daelman — Mon, 08 Jul 2002 18:21:29 GMT

Hello,

the problem is that's a production server and we have lot of entries. That's why I can't now which command generates this error.

Re: Cron

Martin Johnson — Mon, 08 Jul 2002 18:26:40 GMT

If you have the output of the cron entries redirected to a logfile, check the logfile(s) for possible errors. If the output is not redirected to a file (it is redirected to /dev/null) modify the cron entries to redirect to a logfile and examine the logfile (one unique logfile for each cron entry).

HTH
Marty

Re: Cron

Sridhar Bhaskarla — Mon, 08 Jul 2002 18:28:58 GMT

Atleast you can look at /var/adm/cron/log file and search for this pid. The line that starts with CMD gives you the script/command it started through cron with this pid.

-Sri

Re: Cron

Rich Wright — Mon, 08 Jul 2002 18:29:00 GMT

Look at /var/adm/cron/log file for any clues.

Re: Cron

James R. Ferguson — Mon, 08 Jul 2002 18:29:42 GMT

Hi:

Given Clay's first suggestion, I would think that between the tasks associated with 'root' (via 'crontab -l') and the 'var/adm/cron/log' history, that you should be able to match the failure with the task.

Have you tried that?

Regards!

...JRF...

Re: Cron

A. Clay Stephenson — Mon, 08 Jul 2002 18:30:20 GMT

Ok, Plan B. Look in /var/adm/cron/log for matching PID's.

If Plan B fails then Plan C. Back to the original method. Use crontab -l to find the subset of possible culprits and then start each one that's ok to run now with at.
e.g.
at -f /root/bin/myscript.sh now

The reason you need to do this via at rather than simply running it from the shell is that you want to duplicate cron's sparse runtime environment.

Re: Cron

Claire Daelman — Mon, 08 Jul 2002 18:39:49 GMT

Thanks. In fact, we have a problem with cronification of backup and it's the cell server that's why we have so many alarms.

Re: Cron

Claire Daelman — Mon, 08 Jul 2002 18:44:54 GMT

Thanks a lot to everybody. Thanks A.Clay for funny answers...

Re: Cron

Martin Johnson — Mon, 08 Jul 2002 19:21:18 GMT

A. Clay,

Were your answers meant to be funny? If so, they sure went over MY head!

:-)
Marty

Re: Cron

A. Clay Stephenson — Mon, 08 Jul 2002 19:28:59 GMT

Beats me too. I had no idea I was being funny; silly me, I thought I was giving perfectly straightforward answers.