Operating System - HP-UX
1748014 Members
4297 Online
108757 Solutions
New Discussion юеВ

the kernel messages are already disabled

 
SOLVED
Go to solution
Jack C. Mahaffey
Super Advisor

the kernel messages are already disabled

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...
7 REPLIES 7
Cheryl Griffin
Honored Contributor

Re: the kernel messages are already disabled

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.
"Downtime is a Crime."
Jack C. Mahaffey
Super Advisor

Re: the kernel messages are already disabled

The syslogd daemon was actually already stopped.

jack
Sung Oh
Respected Contributor
Solution

Re: the kernel messages are already disabled

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
Super Advisor

Re: the kernel messages are already disabled

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

Re: the kernel messages are already disabled

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
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
Jack C. Mahaffey
Super Advisor

Re: the kernel messages are already disabled

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
Visitor

Re: the kernel messages are already disabled

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