topic Re: syslog message in Operating System - HP-UX

syslog message

Chuck Dugan_2 — Wed, 22 Mar 2000 11:34:27 GMT

I've been getting this message and I don't know what it means. Can you help me?

syslogd: read funix: Resource temporarily unavailable

Thanks,
Chuck Dugan.

Re: syslog message

Ajay Singh_4 — Wed, 22 Mar 2000 11:49:00 GMT

Actually syslogd is a daemon running.
Just go and see /var/adm/syslog/syslog.log

Re: syslog message

Chuck Dugan_2 — Wed, 22 Mar 2000 12:08:41 GMT

Sorry, I guess I didn't state the question clearly. This message was from the
syslog. I just don't know what it is referring to.

Re: syslog message

Atif Malik_2 — Wed, 22 Mar 2000 13:31:07 GMT

This error is usually caused by multiple syslogd daemons running at the same
time. To rectify it:

1) /sbin/init.d/syslogd stop # Stop syslogd
2) ps -ef|grep syslogd # Verify that no syslogd daemons are running
3) /sbin/init.d/syslogd start # Restart syslogd
4) ps -ef|grep syslogd # Verify only one syslogd is running.

This should fix the error message that you're getting.

-Atif

Re: syslog message

user not active — Thu, 23 Mar 2000 00:40:48 GMT

This error is usually caused by having multiple syslogd daemons running.

Check using : ps -ef | grep syslog*

When multiple processes are running, confusion occurs as to which daemon needs
to be writing to the syslog file and the error occurs. To resolve this issue,
stop the syslogd daemons running and restart the one daemon necessary to write
output to the syslog file. Follow these steps:

1. /sbin/init.d/syslogd stop *** This should kill all syslogd ***
daemons.

2. ps -ef | grep syslog* *** Verify you have no
*** daemons running.

3. /sbin/init.d/syslogd start *** Restart the syslogd daemon.

4. ps -ef | grep syslog* *** Verify that you have only one
syslogd daemon running. ***

Then monitor the /var/adm/syslog/syslog.log file for these errors again. This
should resolve the issue.

Re: syslog message

Chuck Dugan_2 — Thu, 23 Mar 2000 06:56:57 GMT

That did the trick, thanks!