Unsuspected reboot

English Hardware
1

Hello!

Some days ago I had a unsuspected reboot of my server. I wasn’t home then, so i don’t know if if the electricity was gone, but there are some strange things in /var/log/messages.

Jan 19 18:34:14 conway xinetd[3849]: Reading included configuration file: /etc/xinetd.d/vnc [file=/etc/xinetd.d/vnc] [line=15]
Jan 19 18:34:14 conway xinetd[3849]: xinetd Version 2.3.14 started with libwrap loadavg options compiled in.
Jan 19 18:34:14 conway xinetd[3849]: Started working: 2 available services
Jan 19 18:34:14 conway smartd[3831]: Device: /dev/sdb, 1 Offline uncorrectable sectors
Jan 19 18:34:14 conway smartd[3831]: Sending warning via /usr/lib/smartmontools/smart-notify to root@localhost …
Jan 19 18:34:14 conway smartd[3831]: Warning via /usr/lib/smartmontools/smart-notify to root@localhost produced unexpected output (67 bytes) to STDOUT/STDERR: method return sender=:1.9 -> dest=:1.10 reply_serial=2 uint16 0
Jan 19 18:34:14 conway smartd[3831]: Warning via /usr/lib/smartmontools/smart-notify to root@localhost: successful
Jan 19 18:34:14 conway smartd[3856]: smartd has fork()ed into background mode. New PID=3856.
Jan 19 18:34:14 conway su: (to root) root on none
Jan 19 18:34:14 conway su: (to root) root on none
Jan 19 18:34:14 conway SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 …
Jan 19 18:34:14 conway SuSEfirewall2: using default zone ‘ext’ for interface eth0
Jan 19 18:34:15 conway kernel: eth1: no IPv6 routers present
Jan 19 18:34:15 conway SuSEfirewall2: batch committing…
Jan 19 18:34:15 conway modprobe: WARNING: /etc/modprobe.conf.local line 5: ignoring bad line starting with ‘coretemp’
Jan 19 18:34:15 conway modprobe: WARNING: /etc/modprobe.conf.local line 6: ignoring bad line starting with ‘w83627ehf’
Jan 19 18:34:15 conway modprobe: WARNING: /etc/modprobe.conf.local line 5: ignoring bad line starting with ‘coretemp’
Jan 19 18:34:15 conway modprobe: WARNING: /etc/modprobe.conf.local line 6: ignoring bad line starting with ‘w83627ehf’
Jan 19 18:34:15 conway modprobe: WARNING: /etc/modprobe.conf.local line 5: ignoring bad line starting with ‘coretemp’
Jan 19 18:34:15 conway modprobe: WARNING: /etc/modprobe.conf.local line 6: ignoring bad line starting with ‘w83627ehf’
Jan 19 18:34:15 conway modprobe: WARNING: /etc/modprobe.conf.local line 5: ignoring bad line starting with ‘coretemp’
Jan 19 18:34:15 conway modprobe: WARNING: /etc/modprobe.conf.local line 6: ignoring bad line starting with ‘w83627ehf’
Jan 19 18:34:15 conway modprobe: WARNING: /etc/modprobe.conf.local line 5: ignoring bad line starting with ‘coretemp’
Jan 19 18:34:15 conway modprobe: WARNING: /etc/modprobe.conf.local line 6: ignoring bad line starting with ‘w83627ehf’
Jan 19 18:34:15 conway SuSEfirewall2: Firewall rules successfully set
Jan 19 18:34:15 conway kernel: bootsplash: status on console 0 changed to on
Jan 19 18:37:46 conway kernel: atl1 0000:01:00.0: hw csum wrong, pkt_flag:e00, err_flag:80 //<– This one looks nasty, wrong checksum for hw?
Jan 19 19:04:06 conway dhcpcd[2732]: eth1: renewing lease of 192.168.1.102 //<– Computer seems to restart automatically, is consistent with uptime

$ uname -a
Linux conway 2.6.25.18-0.2-pae #1 SMP 2008-10-21 16:30:26 +0200 i686 i686 i386 GNU/Linux

Is there someone who can read that encrypted stuff and tell me if it’s something to worry about?

Thanks in advance! //Fredrik

2

I don’t think the event at 18:37 had anything to do with it, after all it survived another 30 minutes or so more. I think atl1 is the ethernet chipset and it got a bad packet or something like that which was dropped.

Don’t you have an electric clock, microwave oven, or VCR that would tell you if there was power loss? :slight_smile:

3

Ok, no, sadly not. I live on a student corridor, and the only electric stuff i got is a screen, the server, a laptop and a amplifier/receiver. So no, I can’t see anything. But if its just a wrong arrived package it shouldn’t make any harm. Thanks for fast reply!