the kernel messages are already disabled

[Jack C. Mahaffey]

Apr 27 10:27:34 host1 syslogd: the kernel messages are already disabled: No such device or address

I got this message when syslogd restarted. syslogd starts with -D argument.

Can anybody give me more info on what the message indicates?

Jack...

[Cheryl Griffin]

How did you kill the syslogd process?

The proper way to stop syslogd is:
# kill -HUP $(cat /var/run/syslog.pid)

or
# kill `cat /var/run/syslog.pid`

kill -9 is not a clean method to stop the daemon and can cause errors.

[Jack C. Mahaffey]

The syslogd daemon was actually already stopped.

jack

[Sung Oh · Accepted solution]

Hi Jack,

Can you check your file system to see if you are out of file system or not?

using "bdf" command.

Sung

[Jack C. Mahaffey]

I have plenty of space for /var. No file system full messages in dmesg output.

[Jeff Schussele]

Hi Jack,

Check your /etc/syslog.conf file and see if there's anything "funny" in there.
If it's a "generic" or out of the box them you might try renaming it & copying down the /usr/newconfig/etc/syslog.conf file & restarting syslogd.
In the syslog.conf file the priority code(s) & facility codes *must* be separated by tab(s).


HTH,
Jeff

[Jack C. Mahaffey]

Jeff, I believe you are on to something. I replaced whitespace in /etc/syslog.conf and then restarted syslogd. Error no longer shows up in the log.


Thanks...

Problem/question solved/answered...

[admunix-tp]

Sometimes that message comes out because the syslogd cannot be lifted because the mail.log file is too large

solution
> /var/adm/syslog/mail.log
/sbin/init.d/syslogd start

regards