topic Re: syslog.log empty in Operating System - HP-UX

syslog.log empty

khilari — Wed, 07 Jun 2006 09:21:09 GMT

Hi people,well it seems that my /var/adm/syslog/syslog.log is empty. How do i go about resetting it so that it starts filling up again??
Thanks.

Re: syslog.log empty

Patrick Wallek — Wed, 07 Jun 2006 09:25:09 GMT

I would for check /etc/syslog.conf and make sure it is configured to send messages to syslog.log. If that look good then I would stop and restart the syslog daemon (syslogd).

# /sbin/init.d/syslogd stop

# /sbin/init.d/syslogd start

# ps -ef |grep syslog

to verify that it is now running.

To see if it is working you can do:

# logger This is a test message to syslog.

Re: syslog.log empty

Peter Godron — Wed, 07 Jun 2006 09:25:55 GMT

Hi,
is the syslog daemon (syslogd) running ?

Re: syslog.log empty

Robert-Jan Goossens — Wed, 07 Jun 2006 09:25:58 GMT

Could you check your /etc/syslog.conf file.

*.info;mail.none /var/adm/syslog/syslog.log

there should be a tabs between the columns.

Regards,
Robert-Jan

Re: syslog.log empty

DCE — Wed, 07 Jun 2006 10:50:27 GMT

run
/sbin/init.d/syslog stop
/sbin/init.d/syslog start
to recycle the syslog daemon.

The most common cause I have come across for this problem is a new sysadmin wants to reset the syslog.log file because it has gotten to big. They either move or delete the syslog.log file without shutting down the daemon

if it moved and an empty syslog.log file is created, the logging will continue to the moved file, not the new file.

if it deleted and a new syslog.log file created. the daemon continues to atempt to send to deleted files disk location (but does not write as the file does not exist there anymore) the new file remains empty

SAM will prune the syslog if you want to decrease its size

you can also COPY the syslog.log to another file with the daemon running and cat /dev/null > /var/adm/syslog/syslog/log to zero out the syslog.log file

Re: syslog.log empty

S.Rider — Wed, 07 Jun 2006 12:14:19 GMT

We've had a few occurances here where the filesystem (/var) filled up, The offending files in /var were removed but syslog.log didn't have anything new written to it, untill syslogd was stopped/started.