From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Description of problem:
so far only shows up on machines with serial consoles and some
signifcant amount of network and disk activity, but has been
reproduced on three completely different platforms/servers.
after 12-36 hours of moderately busy use (bgpd with ~35 sessions of
full internet tables logging every message to disk), machine stops
responding to almost all activity. they will continue to accept
pings, but will not spawn login consoles (either via ssh or via agetty
or mgetty on serial console), stop sending out data, drop all bgp
sessions, and basically hang.
unfortunately, nothing is logged at all, so not sure where
troubleshooting can go at this point.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. load FC2 default install on a new machine (these were upgraded from
FC1 or RH9)
2. run under somewhat heavy load for a while
3. wait for machine to stop responding
Actual Results: pings work, but no new processes, no login shells,
Expected Results: machine should keep functioning as normal.
Same problem. Running stock core2 on ibm eserver pentium 4. Kernel
We are running apache tomcat (jakarta-tomcat-5.0.25) and a fairly
large but not at all unreasonable application (custom). It is a java
applet running from a .jar file in webapps. Calls some servers through
sockets as well.
I also have found that while using nc (netcat) to port some files it
seems to stall and hang but not the whole system. Oddly enough I
found that after the nc sessions lock up while copying files I can
open another terminal to the server and just silly stuff like ls and
change directories and the nc unhangs for a bit and hangs again.
(core 2 machine) tar zcvOp --same-user <some directory> |nc -w 5
<another machines ip> 6060
(another machine) nc -l -p 6060 |tar zxvp
server locks while executing tomcat app through browsers. The server
can be pinged but no ssh, telnet ,rlogin, rsh etc.... Consoles dead too.
Pinging the server works.
Seems similar problems that may be related are 129103 123445 as well.
Hope this helps.
Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat. The Fedora legacy project will be producing further kernel
updates for security problems only.
If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.