FreeBSD 4.7 Syslogs

Micheal Patterson micheal at tsgincorporated.com
Sun May 16 01:12:06 PDT 2004



----- Original Message ----- 
From: "Matt "Cyber Dog" LaPlante" <webmaster at cyberdogtech.com>
To: "'Matthew Seaman'" <m.seaman at infracaninophile.co.uk>;
<freebsd-questions at freebsd.org>
Sent: Saturday, May 15, 2004 12:34 PM
Subject: RE: FreeBSD 4.7 Syslogs


> 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)

<snip>

Something is listening already on port 514 and syslogd is complaining about
that. Do a sockstat |grep 514 and see what's sitting on that port. Also,
"can't open /dev/klog (16)" is another problem. That device is the kernel
log device so syslog can see kernel messages. Syslog may not be too happy
about that either.  You might check and see if you have a klog in /dev

--

Micheal Patterson
TSG Network Administration
405-917-0600

Confidentiality Notice:  This e-mail message, including any attachments, is
for the sole use of the intended recipient(s) and may contain confidential
and privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message.



More information about the freebsd-questions mailing list