Operating System - Linux
1829737 Members
1619 Online
109992 Solutions
New Discussion

Server reboots arbitrarily

 
C Townsend
Occasional Advisor

Server reboots arbitrarily

About every 5 minutes or so my server reboots with the following messges, for no aparent reason. I tried commenting the root cron which runs several checks every 5 min but all to no avail.

In /var/log/messgaes:
Oct 29 23:32:03 buzz1-2 dmnASMCheck: Process [httpd] is not running.
Oct 29 23:33:05 buzz1-2 dmnASMCheck: Process [httpd] is not running.
Oct 29 23:33:05 buzz1-2 dmnASMCheck: Restarting [httpd]...
Oct 29 23:34:10 buzz1-2 dmnASMCheck: Process [httpd] is not running.
Oct 29 23:34:10 buzz1-2 dmnASMCheck: Restarting [httpd]...
Oct 29 23:35:15 buzz1-2 dmnASMCheck: Process [httpd] is not running.
Oct 29 23:35:15 buzz1-2 dmnASMCheck: Restarting [httpd]...
Oct 29 23:36:19 buzz1-2 dmnASMCheck: Process [httpd] is not running.
Oct 29 23:36:19 buzz1-2 dmnASMCheck: Restarting system.
Oct 29 23:36:19 buzz1-2 getty[774]: exiting on TERM signal
Oct 29 23:36:19 buzz1-2 getty[775]: exiting on TERM signal
Oct 29 23:36:20 buzz1-2 dmnASMCheck: dmnASMCheck 2 succeeded
Oct 29 23:36:20 buzz1-2 dmnPFMonitor: dmnPFMonitor shutdown succeeded
Oct 29 23:36:20 buzz1-2 dmnERA: dmnERA shutdown succeeded
Oct 29 23:36:20 buzz1-2 rc: Stopping keytable succeeded
Oct 29 23:36:20 buzz1-2 sshd[535]: Received signal 15; terminating.
Oct 29 23:36:21 buzz1-2 sshd: sshd shutdown succeeded
Oct 29 23:36:21 buzz1-2 sendmail: sendmail shutdown succeeded
Oct 29 23:36:21 buzz1-2 named: named shutdown succeeded
Oct 29 23:36:21 buzz1-2 named: holelogd.named shutdown succeeded
Oct 29 23:36:22 buzz1-2 inet: inetd shutdown succeeded
Broadcast message from root Thu Oct 30 17:14:19 2003...
All views are mine, not my employers. Unless they were given to me by my employer.
1 REPLY 1
Todd McDaniel_1
Honored Contributor

Re: Server reboots arbitrarily

I hope you have resolved this by Monday Nov 3rd, but if not, I would suggest a few things.

1) restore from last good ignite tape.

2) commenting out cron wont stop cron from running in memory... You need to kill the cron daemon and restart it.

3) also, you might look at the /etc/inetd.conf file and possibly restore from a backup or recreate it... could be corrupted.

4) ps -aef |grep root check for any and all procs running as root and see if anything looks suspicous.

5) since your box has rebooted so much your logs will be useless... check your psaction file and look for errors.

""Type psconfig at your login prompt
then select option #5 when the menu comes up. Next select option #1, this
will show a complete current printout of the psaction file. When you are
done type the double slashes as shown at the bottom of the screen then type
"e" to exit.""

6) also check cstm for any errors as well...


Does your syslog show any other errors? OR do you have a crash dump or anything funny in your /var/tombstones/ts99 file?

Hope that this helps if you havent resolved it, but I hope you have.
Unix, the other white meat.