[TriLUG] Kernel issues?

[Stephen P. Schaefer]

There's a chance that there's a file system or disk problem which 
prevents recording the syslog messages.  Try sending the syslog messages 
across the network to another system (see syslog.conf(5)).  Just an idea.

     - Stephen

Janyne Kizer wrote:
> Just over a week ago I updated our production servers to
> 2.4.18-27.7.xsmp.  Since that time we have experienced a lot of
> antisocial activity from these servers.  They will continue to respond
> to ping but will not respond to anything else -- ssh, etc. stops and
> even the server console itself is unresponsive.  The only way out of
> this situation is hard booting the server.  The logs just stop when this
> happen so no errors are recorded.  Are any of you experiencing similar
> problems?  The only other update that we did at that time was the glibc
> update.
> 
> Thanks!