I have a new client that has a weird problem with their linux file server.
It is rebooting without warning several times a day.
reboot activity
Oct 20 06:26:45 aflsdebprod syslogd 1.4.1#10: restart.
Oct 20 08:48:40 aflsdebprod syslogd 1.4.1#10: restart.
Oct 20 11:45:48 aflsdebprod syslogd 1.4.1#10: restart.
Oct 20 11:52:02 aflsdebprod syslogd 1.4.1#10: restart.
Oct 20 11:58:02 aflsdebprod syslogd 1.4.1#10: restart.
Oct 20 12:07:50 aflsdebprod syslogd 1.4.1#10: restart.
Oct 20 12:15:38 aflsdebprod syslogd 1.4.1#10: restart.
Oct 20 12:45:41 aflsdebprod syslogd 1.4.1#10: restart.
Oct 20 13:15:42 aflsdebprod syslogd 1.4.1#10: restart.
Oct 20 13:24:20 aflsdebprod syslogd 1.4.1#10: restart.
Oct 20 13:38:38 aflsdebprod syslogd 1.4.1#10: restart.
Oct 20 14:04:08 aflsdebprod syslogd 1.4.1#10: restart.
Oct 20 14:15:13 aflsdebprod syslogd 1.4.1#10: restart.
Oct 20 14:37:59 aflsdebprod syslogd 1.4.1#10: restart.
Oct 20 15:10:02 aflsdebprod syslogd 1.4.1#10: restart.
Oct 20 15:43:59 aflsdebprod syslogd 1.4.1#10: restart.
Oct 20 16:00:47 aflsdebprod syslogd 1.4.1#10: restart.
Oct 20 17:13:55 aflsdebprod syslogd 1.4.1#10: restart.
Oct 20 17:22:14 aflsdebprod syslogd 1.4.1#10: restart.
Oct 20 17:36:42 aflsdebprod syslogd 1.4.1#10: restart.
Oct 20 17:41:52 aflsdebprod syslogd 1.4.1#10: restart.
Oct 20 18:00:38 aflsdebprod syslogd 1.4.1#10: restart.
Oct 20 18:30:41 aflsdebprod syslogd 1.4.1#10: restart.
Oct 20 19:00:38 aflsdebprod syslogd 1.4.1#10: restart.
Oct 20 20:00:39 aflsdebprod syslogd 1.4.1#10: restart.
Oct 20 20:05:15 aflsdebprod syslogd 1.4.1#10: restart.
Oct 20 22:23:12 aflsdebprod syslogd 1.4.1#10: restart.
Oct 21 06:26:45 aflsdebprod syslogd 1.4.1#10: restart.
Oct 21 11:45:59 aflsdebprod syslogd 1.4.1#10: restart.
Notice how it happened almost at the exact same time yesterday.
Since it only had a 330W power supply and several extra fans in the case
I replaced the power supply with a 500W power supply last night.
The computer is plugged into a UPS. Yesterday prior to getting a new
power supply I had them plug the machine directly into the wall to see if
it was the UPS causing it, the problem persisted.
I can find nothing in the logs that would indicate that hardware
is failing, they all look like this:
Oct 21 04:23:11 aflsdebprod -- MARK --
Oct 21 11:45:59 aflsdebprod syslogd 1.4.1#10: restart.
Oct 21 11:45:59 aflsdebprod kernel: klogd 1.4.1#10, log source = /proc/kmsg started.
Oct 21 11:45:59 aflsdebprod kernel: Inspecting /boot/System.map-2.4.18-bf2.4
Anyone had this happen to them before?
JD
--
JD Austin
Twin Geckos Technology Services LLC
email: jd@twingeckos.com
http://www.twingeckos.com
phone/fax: 480.288.8195