Gentoo Archives: gentoo-user

From: "Timothy A. Holmes" <tholmes@×××××××××.net>
To: gentoo-user@l.g.o
Subject: RE: [gentoo-user] My Snort server -- I Don't know whats wrong -- It seems to go to sleep
Date: Sun, 12 Nov 2006 16:31:10
Message-Id: 17CD9CE4C0FA574A8B29EF02D49B385D2A95B2@srvexch-01.mcaschool.local
In Reply to: Re: [gentoo-user] My Snort server -- I Don't know whats wrong -- It seems to go to sleep by Hans-Werner Hilse
1 > -----Original Message-----
2 > From: Hans-Werner Hilse [mailto:hilse@×××.de]
3 > Sent: Saturday, November 11, 2006 11:27 AM
4 > To: gentoo-user@l.g.o
5 > Subject: Re: [gentoo-user] My Snort server -- I Don't know
6 > whats wrong -- It seems to go to sleep
7 >
8 > Hi,
9 >
10 > On Fri, 10 Nov 2006 17:32:10 -0500
11 > "Timothy A. Holmes" <tholmes@×××××××××.net> wrote:
12 >
13 > > The short summary is the box
14 > > keeps "going to sleep" on me. It wont respond to ssh or webpage
15 > > requests till I ping it about 10 times after that it works normally.
16 >
17 > First: I assume you've checked all cables and tried to
18 > exchange them against some that are known working? Maybe even
19 > tried another port on the switch for the administrative interface?
20 >
21 > Then it sounds like an ARP problem to me. I'd start with
22 > running tcpdump on the administrative interface in order to
23 > see what that machine's seeing, and when. My blind guess
24 > would be that something irritates the routing, hence my guess
25 > that ARP's a bit broken. The routing table entry would time
26 > out and the machine you're using to connect to the admin
27 > interface needs some time to get a proper ARP answer. Is that
28 > snort machine's kernel somehow patched w/ regard to
29 > ARP/Routing? Did you configure ARP via sysctl to non-default values?
30 > You can check that suggestion by setting a routing table
31 > entry for the target machine manually on your SSH client
32 > machine ("arp -s").
33 >
34 > -hwh
35 > --
36 > gentoo-user@g.o mailing list
37 >
38 >
39
40 Hans:
41
42 Thanks for the suggestions,
43 It turned out that the problem was that the processor was entering a low
44 power state after a period of time and needed to be woken up again --
45 adding no-hld to the kernel line in grub.conf solved the problem
46 completely
47
48 Thanks again
49
50 TIM
51
52 Timothy A. Holmes
53 IT Manager / Network Admin / Web Master / Computer Teacher
54
55 Medina Christian Academy
56 A Higher Standard...
57
58 Jeremiah 33:3
59 Jeremiah 29:11
60 Esther 4:14
61
62
63 --
64 gentoo-user@g.o mailing list