Gentoo Archives: gentoo-server

From: Sean Cook <scook@×××××.net>
To: gentoo-server@l.g.o
Subject: Re: [gentoo-server] Server lockups (still ping) (OT because not Gentoo-specific?)
Date: Sun, 24 Apr 2005 20:30:29
Message-Id: 1114374619.30458.0.camel@localhost.localdomain
In Reply to: Re: [gentoo-server] Server lockups (still ping) (OT because not Gentoo-specific?) by Robert Sanders
1 Is it a dell 1550 by any chance?
2
3 On Sun, 2005-04-24 at 10:43 -0400, Robert Sanders wrote:
4 > Casey,
5 >
6 > We've been seeing issues like this for probably the last year. I was
7 > never able to pinpoint it to any action. We implemented remote reboot
8 > hardware and called it a day.
9 >
10 > Some of them had strange activity, but over a larger group of machines I
11 > could never find a pattern to it. It almost seems as if it cannot spawn
12 > any new processes.
13 >
14 > I can't help except to say your not alone.
15 >
16 > Rob
17 >
18 > Casey Allen Shobe - SeattleServer Mailing Lists wrote:
19 > > Hey all,
20 > >
21 > > We're seeing occasional issues with a bunch of machines we have in a
22 > > datacenter, most of which are currently running Gentoo. The machines will
23 > > run solid and fine for days, weeks, even months, and then just lock up solid
24 > > - the box still pings and an nmap scan shows all the normal ports open, but
25 > > nothing responds on any port, nothing shows up in system logs, and the times
26 > > we've had console access to a machine at the time, a login prompt would show
27 > > up, but it would just hang if you tried to log in.
28 > >
29 > > This generally indicates hardware issues to me, but it has been happening
30 > > across a wide array of both well-tested and new machines. In addition, it
31 > > happens on machines that are running Red Hat 7.1 through 9.0 as well as
32 > > Gentoo. The problem seems random, and there is almost always close to zero
33 > > load on the machine when it locks up (only once were we presently using the
34 > > machine, and it locked up while uncompressing a tar file).
35 > >
36 > > The Gentoo systems use the deadline I/O scheduler as it's deemed the most
37 > > reliable, but this has shown up with the default anticipatory I/O scheduler
38 > > as well.
39 > >
40 > > The only common factor seems to be that they are all plugged into a
41 > > questionable HP Procurve switch that we've been contemplating replacing.
42 > > Would that simply be wasting our time (I don't think a buggy switch should be
43 > > able to lock up boxes...)? Any recommendations for what to investigate at
44 > > this point?
45 > >
46 > > Cheers,
47 >
48
49 --
50 gentoo-server@g.o mailing list