Re: FreeBSD 4.7 Syslogs

From: Matthew Seaman (m.seaman_at_infracaninophile.co.uk)
Date: 05/15/04

  • Next message: ..dusan.: "5.2.1 (5.2 too) installation problems"
    Date: Sat, 15 May 2004 09:56:21 +0100
    To: Matt Cyber Dog LaPlante <webmaster@cyberdogtech.com>
    
    
    

    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
    
    



  • Next message: ..dusan.: "5.2.1 (5.2 too) installation problems"

    Relevant Pages

    • Re: [Testers wanted] /dev/console cleanups
      ... write buffer contents via syslogd ... the point the kernel finished to now", ... Or, better yet, do some syslogd magic to make a logfile that can be appropriately readable but doesn't have any overly sensitive messages directed there. ... These messages then get sent to the appropriate log files. ...
      (freebsd-hackers)
    • Magical vanishing ipfw rule.
      ... I've been running a FreeBSD 5.2.1 firewall for several months now with ... puzzling. ... locate anything in my log files of help. ...
      (comp.unix.bsd.freebsd.misc)
    • Re: XFree86 server crash.
      ... > Compaq Presario sr1053wm. ... > I can't provide log files at this point because freebsd works badly ... > XFREE86 DOES WORK ON MY HARDWARE ...
      (freebsd-questions)
    • Re: Diskspace
      ... >the disk is near 94% of diskspace. ... is most common when you delete log files that are still being written to. ... If they're being written by syslogd, sending a SIGHUP to syslogd will do ...
      (comp.unix.solaris)
    • Re: syslogd not starting
      ... David Williams wrote: ... > I recently noticed I wasn't getting any messages in the log files and ... of some DSOs (including glibc) is not as required. ... now that syslogd is covered by the targeted policy. ...
      (Fedora)