/var/log/messages empty since June 26 :-/

Gilles gilles.ganault at free.fr
Fri Jul 2 11:28:41 UTC 2010

On Fri, 02 Jul 2010 12:19:20 +0100, Matthew Seaman
<m.seaman at infracaninophile.co.uk> wrote:
>Is syslogd running?

Yes it is:

# ps aux | grep -i syslog | grep -v grep
root    518  0,0  0,3  1404  1072  ??  Ss   Ven19     0:02,07
/usr/sbin/syslogd -s

> Restarting syslogd would be a good thing to try in
>any case:
>   # /etc/rc.d/syslogd restart

Looks like it did the trick:

# tail -f /var/log/messages
Jun 26 16:00:00 freebsd newsyslog[5320]: logfile turned over due to
Jul  2 13:26:45 freebsd syslogd: exiting on signal 15
Jul  2 13:26:45 freebsd syslogd: kernel boot file is

>This should result in some output to the system logs -- if you don't see
>that, then your syslog.conf may be broken: syslogd can die silently in
>those circumstances.  You'll need to run syslogd with the '-d' debugging
>flag in addition to what flags you usually use in order to see what the
>problem is.

If the same issue pops up again, I'll try the "-d" option.

Thank you.

More information about the freebsd-questions mailing list