syslogd: read funix: Resource temporarily unav.

[Uwe Sydow]

the syslog.log file on a v-class HP-UX 11.00 has several entries (+- 1 per minute) of

Jul 19 15:05:10 system1 syslogd: read funix: Resource temporarily unanvailable

Does anybody know what's wrong (i.e. what is the missing resource)? Where should I start searching?

[Cheryl Griffin]

Uwe,

Check for more than one syslogd process running.

# ps -ef |grep syslog

If you do, execute:
# /sbin/init.d/syslogd stop

Check again
# ps -ef |grep syslog
If there is another, I would try the stop first, if it does not stop, then kill (without the -9).

Once you get them cleared out, restart syslogd
# /sbin/init.d/syslogd start

Best Wishes,
Cheryl

[Brian M. Fisher]

You are getting this error because you are running two swagentd processes.

To resolve your problem:

1. Kill the swagentd processes.

2. Re-start swagentd.

Brian
<*(((>< er

[Brian M. Fisher]

As another option:
This error is usually caused by having multiple syslogd daemons running. As
seen in the output from this particular system, there is one syslogd daemon
spawned by init upon boot up and three started by user karekamg. 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.

Brian
<*(((>< er

[Uwe Sydow]

Thanks to all. Multiple syslogd processes caused the error message. But so far I was not able to find out what/who started up to 10 syslogd processes over a period of 4 weeks. Anyway, following your advices only 1 syslogd process is running now and everthing looks o.k.