I tried the logger command, but it didn't reach the messages file (which is
still empty).  Here is the output from the syslogd -d command:

syslogd: bind: Address already in use
logmsg: pri 53, flags 4, from , msg syslogd: bind: Address already in use
Logging to CONSOLE /dev/console
syslogd: bind: Address already in use
logmsg: pri 53, flags 4, from , msg syslogd: bind: Address already in use
Logging to CONSOLE /dev/console
can't open /dev/klog (16)
off & running....
init
cfline("local7.crit;local7.err;local7.notice
/var/log/purchasing", f, "*", "*")
cfline("local0.*                                        /var/log/postgres",
f, "*", "*")
cfline("local2.*
/var/log/qmail/smtpd.log", f, "*", "*")
cfline("local3.*
/var/log/qmail/send", f, "*", "*")
cfline("local4.*
/var/log/qmail/masterlog", f, "*", "*")
cfline("authpriv.*                                      /var/log/authpriv",
f, "local0", "*")
cfline("security.*                                      /var/log/security",
f, "local0", "*")
cfline("mail.info                                       /var/log/maillog",
f, "local0", "*")
cfline("lpr.info                                        /var/log/lpd-errs",
f, "local0", "*")
cfline("cron.*                                          /var/log/cron", f,
"local0", "*")
cfline("*.emerg                                         *", f, "local0",
"*")
cfline("console.info
/var/log/console.log", f, "local0", "*")
X X X X X X X X X X X X X X X X X X X X X X X 5 X FILE: /var/log/purchasing
X X X X X X X X X X X X X X X X 8 X X X X X X X X FILE: /var/log/postgres
X X X X X X X X X X X X X X X X X X 8 X X X X X X FILE:
/var/log/qmail/smtpd.log
X X X X X X X X X X X X X X X X X X X 8 X X X X X FILE: /var/log/qmail/send
X X X X X X X X X X X X X X X X X X X X 8 X X X X FILE:
/var/log/qmail/masterlog
X X X X X X X X X X 8 X X X X X X X X X X X X X X FILE: /var/log/authpriv
(local0)
X X X X X X X X X X X X X 8 X X X X X X X X X X X FILE: /var/log/security
(local0)
X X 6 X X X X X X X X X X X X X X X X X X X X X X FILE: /var/log/maillog
(local0)
X X X X X X 6 X X X X X X X X X X X X X X X X X X FILE: /var/log/lpd-errs
(local0)
X X X X X X X X X 8 X X X X X X X X X X X X X X X FILE: /var/log/cron
(local0)
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 X WALL:  (local0)
X X X X X X X X X X X X X X 6 X X X X X X X X X X FILE: /var/log/console.log
(local0)
logmsg: pri 56, flags 4, from compname, msg syslogd: restart
syslogd: restarted


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Matthew Seaman
Sent: Saturday, May 15, 2004 4:56 AM
To: Matt Cyber Dog LaPlante
Cc: [EMAIL PROTECTED]
Subject: Re: FreeBSD 4.7 Syslogs

On Sat, May 15, 2004 at 01:51:40AM -0400, Matt Cyber Dog LaPlante wrote:
> I've inherited a FreeBSD 4.7 server as part of a system administration
job.
>  Recently I noticed that the syslog files had stopped collecting data.
 This
> includes /var/log/messages and /var/log/console among others.  Up until
some
> time last week, they'd been full of data, but after some unknown event,
all
> data collection stopped.  I did not build/configure the system, nor am I
> very fluent in the ways of BSD, so I do not know where else to begin
looking
> for answers.  I ran the newsyslog program to regenerate all the log files.
>  It created them, with the single line stating a new log file was created,
> but aside from that one line they remain empty.  I tried manually
restarting
> syslogd, as well as rebooting the whole machine, neither of which have had
> any effect.  I have not manually altered any syslog configuration info,
and
> I basically have no idea what to try next.  I'm a relative noob when it
> comes to FreeBSD, so I'd appreciate answers in a simple format.  Thanks in
> advance...

Hmmm... that doesn't sound good.  Can you use logger(1) to write a
test message into the log files?

    % logger -p daemon.info -t TEST "Some test message"

which should appear in /var/log/messages.  If it doesn't, look at
/etc/syslog.conf and verify that it is sensible.  Then try killing
syslogd and starting it up in debug mode:

    # syslogd -d {other syslog flags}

this will not daemonize itself or go into the background and will
print out various debugging information as log messages come in.

        Cheers,

        Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.                       26 The Paddocks
                                                      Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey         Marlow
Tel: +44 1628 476614                                  Bucks., SL7 1TH UK


_______________________________________________
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to