Date: Sat, 15 May 2004 09:56:21 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Matt Cyber Dog LaPlante <webmaster@cyberdogtech.com> Cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD 4.7 Syslogs Message-ID: <20040515085621.GC56326@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <20040515055255.4790A43D31@mx1.FreeBSD.org> References: <20040515055255.4790A43D31@mx1.FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--q9KOos5vDmpwPx9o
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
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 jo=
b.
> =A0Recently I noticed that the syslog files had stopped collecting data. =
=A0This
> includes /var/log/messages and /var/log/console among others. =A0Up until=
some
> time last week, they'd been full of data, but after some unknown event, a=
ll
> data collection stopped. =A0I 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 look=
ing
> for answers. =A0I ran the newsyslog program to regenerate all the log fil=
es.
> =A0It created them, with the single line stating a new log file was creat=
ed,
> but aside from that one line they remain empty. =A0I tried manually resta=
rting
> syslogd, as well as rebooting the whole machine, neither of which have had
> any effect. =A0I have not manually altered any syslog configuration info,=
and
> I basically have no idea what to try next. =A0I'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
--=20
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
--q9KOos5vDmpwPx9o
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
iD8DBQFApds1iD657aJF7eIRAiVQAKCNZhQaYPgBd/Z0g1Bems6DMWbV+gCfWiDD
xJzn6WT+byGwTOUd04PO39A=
=IDRv
-----END PGP SIGNATURE-----
--q9KOos5vDmpwPx9o--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040515085621.GC56326>