Gentoo Archives: gentoo-user

From: Mark Shields <laebshade@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Gentoo froze after 25 days of being up
Date: Fri, 24 Mar 2006 21:59:11
Message-Id: 642958cc0603241349j38d1b64dq6ada0d35329c1fb2@mail.gmail.com
In Reply to: Re: [gentoo-user] Gentoo froze after 25 days of being up by Philip Webb
1 On 3/24/06, Philip Webb <purslow@×××××××××.ca> wrote:
2 >
3 > 060324 Mark Shields wrote:
4 > > I've had Gentoo on my home server for a little over a year now.
5 > > I've never had a problem with it outright freezing until recently.
6 > > Yesterday I was playing World of Warcraft on my home PC
7 > > I have a kvm switch so I had WoW running on my main PC
8 > > while I was working on the screen for the server.
9 > > I had just typed emerge -av net-ping then typed yes,
10 > > it got 3 lines into the emerge and the server froze.
11 > > Internet access stopped working on the home PC (WoW disconnected),
12 > > screen froze on tty1, could not change virtual screens,
13 > > keyboard would not type & no lock keys (caps, scroll, etc.) would work.
14 > > Ctrl+alt+del wouldn't work, and I couldn't even ssh into it.
15 >
16 > Judging from previous reports of similar problems, it sounds like
17 > hardware.
18 > Overheating ? Bad memory ? Mobo failure somewhere ?
19 >
20 > --
21 > ========================,,============================================
22 > SUPPORT ___________//___, Philip Webb : purslow@××××××××××××××.ca
23 > ELECTRIC /] [] [] [] [] []| Centre for Urban & Community Studies
24 > TRANSIT `-O----------O---' University of Toronto
25 > --
26 > gentoo-user@g.o mailing list
27 >
28 >
29 Thanks for the replies.
30
31 It only did it once. I figured it might possibly be a hardware failure
32 since I'm using used parts/refurbished parts, but I was wanting to
33 know if I can check any log files to see exactly why, or enable some
34 form of extended logging to
35 pick it up if it happens again. I use syslog-ng for my system logger.
36 I checked /var/log/messages and didn't find anything.
37 Here is the last line before it froze from that log file and the first line
38 immediately after:
39
40 Mar 23 20:29:55 laeb named[9770]: lame server resolving '
41 x.x.x.x.in-addr.arpa' (in '128.202.84.in-addr.arpa'?): x.x.x.x#53
42 Mar 23 20:38:39 laeb syslog-ng[8723]: syslog-ng version 1.6.9 starting
43
44 --
45 - Mark Shields