From owner-freebsd-questions@FreeBSD.ORG Sat May 15 13:04:18 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A62C16A4D0 for ; Sat, 15 May 2004 13:04:18 -0700 (PDT) Received: from mta9.adelphia.net (mta9.adelphia.net [68.168.78.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00C5043D53 for ; Sat, 15 May 2004 13:04:17 -0700 (PDT) (envelope-from Barbish3@adelphia.net) Received: from barbish ([67.20.101.71]) by mta9.adelphia.net (InterMail vM.5.01.06.08 201-253-122-130-108-20031117) with SMTP id <20040515200416.SFSU26615.mta9.adelphia.net@barbish>; Sat, 15 May 2004 16:04:16 -0400 From: "JJB" To: "Matt \"Cyber Dog\" LaPlante" , "'Matthew Seaman'" , Date: Sat, 15 May 2004 16:04:15 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 In-Reply-To: <20040515173448.1B25943D2F@mx1.FreeBSD.org> Importance: Normal Subject: RE: FreeBSD 4.7 Syslogs X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Barbish3@adelphia.net List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 May 2004 20:04:18 -0000 Well since you are new to FBSD and since the syslogd -d commands shows that you do not have logging specified in /etc/syslog.conf for the messages file. You just do not know what you are looking at. Who ever was sysadmin before you probably commented it out for what ever reason. By the way I tried using the logger command on my 4.9 system and it did not write any messages at all. So it is no help in debugging this problem. I read the man logger info and as usual the man page is useless. Who ever writes those must work real hard at writing sentences that convey no meanings. To verify the conclusion that no logging is enabled for messages file, first do halt command, power off box, wait 1 minute, power back on to boot system, then, post the complete contents of these files. /var/run/dmesg.boot /etc/rc.conf /etc/syslog.conf /etc/newsylog.conf /etc/crontab The output of this command ls -l /var/log/* to see all the details about your log files. The output of this command ps ax -----Original Message----- From: owner-freebsd-questions@freebsd.org [mailto:owner-freebsd-questions@freebsd.org]On Behalf Of Matt "Cyber Dog" LaPlante Sent: Saturday, May 15, 2004 1:34 PM To: 'Matthew Seaman'; freebsd-questions@FreeBSD.org 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) 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: owner-freebsd-questions@freebsd.org [mailto:owner-freebsd-questions@freebsd.org] On Behalf Of Matthew Seaman Sent: Saturday, May 15, 2004 4:56 AM To: Matt Cyber Dog LaPlante Cc: freebsd-questions@freebsd.org 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 _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"