cron

[eric stewart_2]

Some tine last thursday, on a machine that uses cron very little, the following message showed up on my cron log entry:
root 7623 c Thu May 23 23:30:03 EDT 2002 ts=139

Does anyone lnow what the ts=139 means?

[Jeff Schussele · Accepted solution]

Hi Eric,

That's a Termination Signal or error code for a cron job that died.
ts=termination signal
rc=return code

You need to look at cron to determine what job may have been running at that time & check to see if it's been setup poperly. Could also be the cron daemon itself that died.

See the following thread

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x95d2d06ed8c8d4118fef0090279cd0f9,00.html

HTH,
Jeff

[Stefan Farrelly]

ts=139 is a signal called SIGCLEANUP. This is normally run if a process detects a SIGHUP (hangup or kill -1 command) and passes to its cleanup procedure before closing.

You might be able to get more info from;
man 5 signal

I think your cron process, whatever it was, received a termination call and cleaned itself up then stopped running.

[eric stewart_2]

Here is more info for later reference:
Here is the cron entry

>crontab -l
* * * * * /usr/bin/date >> /tmp/crontest
/tmp

>date
Tue May 28 09:25:11 EDT 2002
/tmp
ls -l /tmp/crontest
/tmp/crontest not found
/tmp
>
Here is the cron log:
>CMD: /usr/bin/date >> /tmp/crontest
>estewar1 25413 c Tue May 28 09:25:00 EDT 2002

[eric stewart_2]

This problem showed up last Thursday.
Friday at 23:30, operations does an automatic reboot of the system.
All cron jobs are still getting the ts=139

As soon as the operation person gets in I will convince him to restart cron.
I will keep everyone informed.
Thanks for the support and rapid responses.

[PIYUSH D. PATEL]

Hi,

Its a termination signal and your cron process has got terminated due to some problems.

Check out if your cron process had some problems. You can check in the syslog also if some errors are logegd in or in the cron log ../var/cron/log.

Piyush

[eric stewart_2]

operations stopped and started cron
It seems to be working now.
No idea exactly what caused the problem. just glad it has gone away.