From owner-freebsd-questions@FreeBSD.ORG Fri Jul 2 11:28:41 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4134A1065670 for ; Fri, 2 Jul 2010 11:28:41 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id EEFFA8FC27 for ; Fri, 2 Jul 2010 11:28:40 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1OUeQB-0002ZE-Dw for freebsd-questions@freebsd.org; Fri, 02 Jul 2010 13:28:39 +0200 Received: from mar92-9-82-237-75-54.fbx.proxad.net ([82.237.75.54]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 02 Jul 2010 13:28:39 +0200 Received: from gilles.ganault by mar92-9-82-237-75-54.fbx.proxad.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 02 Jul 2010 13:28:39 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: Gilles Date: Fri, 02 Jul 2010 13:28:27 +0200 Lines: 33 Message-ID: <76jr26t3bupismgq47f6ld10mccp0o8mdu@4ax.com> References: <84ir26h1punkutik1dmlbhd77d2npsqupe@4ax.com> <4C2DCB38.6030500@infracaninophile.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: mar92-9-82-237-75-54.fbx.proxad.net X-Newsreader: Forte Agent 3.1/32.783 Subject: Re: /var/log/messages empty since June 26 :-/ X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jul 2010 11:28:41 -0000 On Fri, 02 Jul 2010 12:19:20 +0100, Matthew Seaman wrote: >Is syslogd running? Yes it is: # ps aux | grep -i syslog | grep -v grep root 518 0,0 0,3 1404 1072 ?? Ss Ven19 0:02,07 /usr/sbin/syslogd -s > Restarting syslogd would be a good thing to try in >any case: > > # /etc/rc.d/syslogd restart Looks like it did the trick: # tail -f /var/log/messages Jun 26 16:00:00 freebsd newsyslog[5320]: logfile turned over due to size>100K Jul 2 13:26:45 freebsd syslogd: exiting on signal 15 Jul 2 13:26:45 freebsd syslogd: kernel boot file is /boot/kernel/kernel >This should result in some output to the system logs -- if you don't see >that, then your syslog.conf may be broken: syslogd can die silently in >those circumstances. You'll need to run syslogd with the '-d' debugging >flag in addition to what flags you usually use in order to see what the >problem is. If the same issue pops up again, I'll try the "-d" option. Thank you.