> -----Original Message-----
> From: blueonyx-bounces at blueonyx.it [mailto:blueonyx-bounces at blueonyx.it]
> On Behalf Of Greg Kuhnert
> Sent: Monday, December 07, 2009 3:07 PM
> To: 'BlueOnyx General Mailing List'
> Subject: [BlueOnyx:03032] Re: Troubleshooting lockups/crashes
>
> There are a two options that come to mind...
>
> 1. Security software on your box... Is something building dynamic
> firewall rules? (dfix does this). You might be tripping something. Look
> in /var/log/messages for firewall hits.
If Dfix had created a rule that blocked me, would I still be able to ping
the server? When it happens, no one can access the server, so it would seem
that might not indicate a firewall rule, unless it was set to all ports but
the port for pinging. I dunno. Could something wacky happen with the IP
127.0.0.1 being where it shouldn't?
> 2. interface driver problems... I have a box that has poorly supported
> ethernet drivers. Type ifconfig from the command line, and look for any
> dropped packets ... Mine increase rapidly, and from time to time - that
> ethernet port locks up tight. If this is your problem, let me know, and
> I'll try to help.
Here's ifconfig output:
eth0 Link encap:Ethernet HWaddr 00:0B:CD:41:1B:DE
inet addr:208.77.219.98 Bcast:208.77.219.111
Mask:255.255.255.240
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:953043 errors:0 dropped:0 overruns:0 frame:0
TX packets:1191134 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:142255854 (135.6 MiB) TX bytes:1067211233 (1017.7 MiB)
Interrupt:193 Memory:f7df0000-f7e00000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:49118 errors:0 dropped:0 overruns:0 frame:0
TX packets:49118 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:46916677 (44.7 MiB) TX bytes:46916677 (44.7 MiB)
That looks like no errors, no drops, no overruns.
The 6GB RAM is all new, perhaps I should run a test on it.
And thanks, I appreciate the help.