Re: Analysing a REDHAT ES4 crash
- From: "ynotssor" <ynotssor@xxxxxxxxxxx>
- Date: Tue, 21 Feb 2006 12:53:12 -0800
In news:1140553559.555898.145430@xxxxxxxxxxxxxxxxxxxxxxxxxxxx,
parvinderb@xxxxxxxxx <parvinderb@xxxxxxxxx> wrote:
its between these two time the crash happened:
Feb 20 23:01:01 LSAGG151 crond(pam_unix)[4183]: session closed for user
root
Feb 21 00:54:41 LSAGG151 syslogd 1.4.1: restart.
You should carefully examine the nature and detail of the cron job that
occurred, perhaps by prefacing it with strace.output to a file, e.g.:
1 * * * * /usr/bin/strace -o /your/output/file`date '+\%d\%H\%M'` \
/your/cron/task -args
Put it on one line; I used continuation "\" because of Usenet line wrap.
Then examine any files (particularly towards the end of the file) that
occurred at the time of a crash, although it appears the crash came
subsequent to the cron job, so maybe it won't be helpful.
.
- References:
- Analysing a REDHAT ES4 crash
- From: parvinderb
- Re: Analysing a REDHAT ES4 crash
- From: Jan Gerrit Kootstra
- Re: Analysing a REDHAT ES4 crash
- From: ynotssor
- Re: Analysing a REDHAT ES4 crash
- From: parvinderb
- Analysing a REDHAT ES4 crash
- Prev by Date: Re: Analysing a REDHAT ES4 crash
- Next by Date: setting default permissions
- Previous by thread: Re: Analysing a REDHAT ES4 crash
- Next by thread: Re: Analysing a REDHAT ES4 crash
- Index(es):