[ale] klogd and syslogd hanging

[Dow_Hurst]

Googling didn't yield much to help with this specific problem.  Noticed that kernel 2.0.x had some tty error messages, but that is back in 1998!  I did notice that syslog 1.4.1 is pretty static for the past year or so as the current version used in suse.  At this point, I'm just trying to recover control so have commented out the line dealing with outputting to tty10 in syslog.conf.  If I can find out how to force the current syslogd to exit without rebooting, I'll recover control.  It won't respond to SIGKILL or SIGTERM.  I wasn't able to switch init levels either on Monday when I started working on second occurence.  I ended up hard rebooting.  Good thing I had Reiserfs on the RAID array!  I don't want to do that again if I can prevent it.  This syslogd error has now appeared three times.

How do kill or flush a queue for a tty?  Is that even possible?
Dow
 

-----Original Message-----
From: Dow_Hurst <dhurst at mindspring.com>
Sent: Jun 8, 2005 10:53 AM
To: ale at ale.org
Subject: [ale] klogd and syslogd hanging

suse 9.1
kernel 2.6.5-7.151-default
syslogd-1.4.1-519
init level 3

I have an error message on tty10 (which is an alternate output for syslogd on suse) that is showing infinite messages:

release_dev: tty10: read/write wait queue active!

Does anyone know what this means?  The syslogd daemon is running on the CPU and the /var/log/messages are no longer being logged.  I've tried cycling syslogd with the /etc/init.d/syslog restart/stop/start.  I've signaled syslogd and klogd with different signals such as HUP, TER, and KILL.  I've only truly recovered what seems to be normal operation with a reboot.  Two issues come to mind:

1.  syslogd can choke with old compatibility libs that don't format the messages to syslogd correctly.

2.  Is the tty10 not released due to its current state when syslogd is killed and that is why I am having to reboot to regain control?  Is there a way to first flush tty10 and regain control of it directly?


I can try running syslogd in debug mode.  This whole issue cropped up in mid April.  I just noticed the CPU was under load (this is a lightly loaded production fileserver).  I used top and saw syslogd and klogd showing significant percentage of the CPU so started investigating.  Ended up frustrated and having to reboot.  Now I've had a second occurence so after more investigation on my own, I ended up rebooting again.  I've seen the third time just 1 day later.  I don't want to have to reboot.  I would like to fix this!

Now that I've got a real error message to deal with, I am going to do some Googling.  
Thanks for your thoughts,
Dow


No sig.
_______________________________________________
Ale mailing list
Ale at ale.org
http://www.ale.org/mailman/listinfo/ale


No sig.