Hi, The other day our main server (running Debian potato) had a fit when syslog and klogd decided to chew almost all CPU, forcing the kernel to kill off various daemons. /var/messages/syslog.? shows the following: Jun 8 09:51:06 holly squid[32049]: Rebuilding storage in Cache Dir #0 (CLEAN) Jun 8 09:51:06 holly squid[32049]: Set Current Directory to /var/spool/squid Jun 8 10:47:21 holly syslogd 1.3-3#33: restart. Jun 8 10:47:21 holly kernel: klogd 1.3-3#33, log source = /proc/kmsg started. Jun 8 10:47:21 holly kernel: Inspecting /boot/System.map-2.2.14 Jun 8 10:47:21 holly kernel: Loaded 6832 symbols from /boot/System.map-2.2.14. Jun 8 10:47:21 holly kernel: Symbols match kernel version 2.2.14. Jun 8 10:47:21 holly kernel: Loaded 71 symbols from 5 modules. Jun 8 10:47:21 holly kernel: VM: killing process imapd Jun 8 10:47:21 holly kernel: VM: killing process rpc.mountd Jun 8 10:47:21 holly kernel: VM: killing process squid Jun 8 10:47:21 holly kernel: VM: killing process rpc.nfsd Jun 8 10:47:21 holly kernel: Unable to load interpreter Jun 8 10:47:21 holly kernel: VM: killing process apache-ssl Jun 8 10:47:21 holly kernel: VM: killing process squid Jun 8 10:47:21 holly kernel: VM: killing process genpowerd Jun 8 10:47:21 holly kernel: VM: killing process syslogd Jun 8 10:47:21 holly kernel: VM: killing process squid Jun 8 10:47:21 holly kernel: VM: killing process python Jun 8 10:47:21 holly kernel: VM: killing process named The messages from squid are part of the normal morning service restart that Debian likes to perform (as I gather from other days logs), and the syslog restart message was when syslog was restarted after finding the system preparing to crash. What I'd like to know is if anyone has had any experiences like this, as we'd really like to find the cause of the crash. -- jamesw ------------------------------ [EMAIL PROTECTED] -- SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au To unsubscribe send email to [EMAIL PROTECTED] with unsubscribe in the text
