syslogd hang

[Tarun Jain_1]

One of processes in my machine called syslog() to log a message in syslog and hanged there. I tried truss on the process and syslogd, both are stucked in write(). Here is the output of some commands:


# ls -lsrt /var/adm/syslog/
total 1472
80 -rw-r--r-- 1 root root 40818 May 27 05:45 OLDsyslog.log
112 -r--r--r-- 1 root root 52737 Jun 8 10:56 mail.log
1280 -rw-r--r-- 1 root root 643013 Jun 8 17:05 syslog.log
# date
Fri Jun 9 04:49:17 IST 2006
# ps -eaf|grep syslogd
root 25950 25914 0 04:49:26 pts/tg 0:00 grep syslogd
root 989 1 0 May 27 ? 0:03 /usr/sbin/syslogd -D

# truss -p 989
( Attached to process 989 ("/usr/sbin/syslogd -D") [32-bit] )
writev(11, 0x7fffa800, 6) [sleeping]
( Detaching from process 989 ("/usr/sbin/syslogd -D") )

# truss -p 14841
( Attached to process 14841 ("/opt/myproc") [32-bit] )
write(10, "J u n 8 1 7 : 0 6 : 0 6 ".., 83) [sleeping]

###Output of another simple program which ###tries to write in syslog

# ./a.out
syslog:: Resource temporarily unavailable

# uname -a
HP-UX sharedhpia12 B.11.23 U ia64 0997230416 unlimited-user license



I am running HP-UX 11.23 (May 05) version.

Is this HP-UX kernel or syslogd bug ?

Thanks in Advance for your help.

[Steven E. Protter]

Shalom,

If its a bug, it surely would be handled in the most recent quarterly update. I suggest that, whether or not the cause is a bug.

I would suggest killing the processes manually and then starting syslog again.

Usually, I let the system write to syslog and let my homegrown scripts write their output elsewhere. I consider this a good practice.

SEP

[Tarun Jain_1]

I am sure after restarting syslogd, stuff will start working. But I would like to know if anyone faced this before. dmesg is also showing some error messages:


mem: could not lock: 0x4048833
mem: could not lock: 0x404881e
mem: could not lock: 0x404886e
mem: could not lock: 0x404881e
mem: could not lock: 0x404881e
mem: could not lock: 0x404881e
mem: could not lock: 0x404881e
mem: could not lock: 0x404882a
mem: could not lock: 0x4048853
mem: could not lock: 0x4048802
mem: could not lock: 0x4048848
mem: could not lock: 0x404882a
mem: could not lock: 0x4048853
mem: could not lock: 0x4048802
mem: could not lock: 0x4048848
mem: could not lock: 0x404882a
mem: could not lock: 0x4048853
mem: could not lock: 0x4048802
mem: could not lock: 0x4048871
mem: could not lock: 0x4048871
mem: could not lock: 0x404882a
mem: could not lock: 0x4048853
mem: could not lock: 0x4048802
mem: could not lock: 0x404882a
mem: could not lock: 0x4048853
mem: could not lock: 0x4048802
mem: could not lock: 0x4048868
mem: could not lock: 0x4048864
mem: could not lock: 0x4048821
mem: could not lock: 0x404882e



thanks,
Tarun