Results 1 to 2 of 2
Hi Everyone
I hope someone can assist with some info....
We are running a SUSE 8 server (this is however general linux question) which rebooted itself during the course of ...
- 09-01-2008 #1Just Joined!
- Join Date
- Oct 2006
- Posts
- 5
Why did server reboot?
Hi Everyone
I hope someone can assist with some info....
We are running a SUSE 8 server (this is however general linux question) which rebooted itself during the course of the evening.
I have tried to find out what caused the reboot but from the logs I can't find the answer as none of the entries mean anything to me.
Can someone perhaps assist. Here is the entries just before the reboot from the /var/log/messages file:
Sep 1 03:35:21 mxccdbn1 ucd-snmp[28598]: cmaX: subMIB 10 handler has disconnected
Sep 1 03:35:21 mxccdbn1 ucd-snmp[28598]: cmaX: subMIB 11 handler has disconnected
Sep 1 03:35:21 mxccdbn1 ucd-snmp[28598]: cmaX: subMIB 14 handler has disconnected
Sep 1 03:35:21 mxccdbn1 ucd-snmp[28598]: cmaX: subMIB 15 handler has disconnected
Sep 1 03:35:21 mxccdbn1 ucd-snmp[28598]: cmaX: subMIB 16 handler has disconnected
Sep 1 03:35:21 mxccdbn1 ucd-snmp[28598]: cmaX: subMIB 21 handler has disconnected
Sep 1 03:35:21 mxccdbn1 ucd-snmp[28598]: cmaX: subMIB 22 handler has disconnected
Sep 1 03:35:21 mxccdbn1 ucd-snmp[28598]: cmaX: subMIB 23 handler has disconnected
Sep 1 03:35:22 mxccdbn1 hpasmd[3796]: ProLiant System Health Monitor unloading
Sep 1 03:35:43 mxccdbn1 kernel: get_cycles() returned 0x0
Sep 1 03:35:43 mxccdbn1 kernel: get_cycles() returned 0x0
Sep 1 03:35:44 mxccdbn1 rpc.statd[5118]: Caught signal 15, un-registering and exiting.
Sep 1 03:35:45 mxccdbn1 ucd-snmp[28596]: Received TERM or STOP signal... shutting down...
Sep 1 03:35:46 mxccdbn1 sshd[3332]: Received signal 15; terminating.
Sep 1 03:35:46 mxccdbn1 kernel: Kernel logging (proc) stopped.
Sep 1 03:35:46 mxccdbn1 kernel: Kernel log daemon terminating.
Sep 1 03:35:47 mxccdbn1 exiting on signal 15
Sep 1 08:46:53 mxccdbn1 syslogd 1.4.1: restart.
Sep 1 08:46:54 mxccdbn1 modprobe: modprobe: Can't locate module block-major-131
Sep 1 08:46:54 mxccdbn1 modprobe: modprobe: Can't locate module block-major-130
Sep 1 08:46:54 mxccdbn1 modprobe: modprobe: Can't locate module block-major-131
Sep 1 08:46:54 mxccdbn1 modprobe: modprobe: Can't locate module block-major-13
thank you in advance
- 09-01-2008 #2
signal 15 was generated for some reason the logs don't show
This tells the system to shutdown. It could be a program but since you are running ver 8 ,which is very old, I expect your hardware is also very old. Could have been gamma rays or power flux or any number of random events.


Reply With Quote