14 May
2004
14 May
'04
7:02 p.m.
--On Friday, May 14, 2004 06:55:17 -0400 "Wyner, Peter" <pwyner@verisign.com> wrote:
All,
I am running into an issue on a previously working syslog_ng 1.6.2 server. There were no configuration changes between when it worked and now (when it doesn't). The syslog sever will process a large number of packets for a period of time and then suddenly the processor utilization goes down to zero, files stop being written, and truss shows:
door_call(6, 0xFFBED340) (sleeping...) signotifywait() (sleeping...) lwp_sema_wait(0xFEF0DE60) (sleeping...)
Looks like a hang on a NSS call (such as gethostbyaddr). sotruss will better show what's going on, but I suspect you're hanging on a DNS lookup. -- Carson