From owner-freebsd-questions Tue Oct 29 13:26: 6 2002 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 A7F8C37B401 for ; Tue, 29 Oct 2002 13:26:04 -0800 (PST) Received: from portal.aphroland.org (portal.aphroland.org [216.39.174.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C99D43E3B for ; Tue, 29 Oct 2002 13:26:04 -0800 (PST) (envelope-from freebsd@aphroland.org) Received: by portal.aphroland.org (Postfix, from userid 1010) id 8972C27803D; Tue, 29 Oct 2002 13:25:47 -0800 (PST) Received: from saratoga.linuxpowered.net (debian [127.0.0.1]) by portal.aphroland.org (Postfix) with SMTP id ED67027803C for ; Tue, 29 Oct 2002 13:25:42 -0800 (PST) Received: from portal.aphroland.org ([216.39.174.24]) (SquirrelMail authenticated user aphro) by webmail.linuxpowered.net with HTTP; Tue, 29 Oct 2002 13:25:42 -0800 (PST) Message-ID: <16197.216.39.174.24.1035926742.squirrel@webmail.linuxpowered.net> Date: Tue, 29 Oct 2002 13:25:42 -0800 (PST) Subject: syslog-ng dies, whats a good way to monitor it? From: "nate" To: X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal X-Mailer: SquirrelMail (version 1.2.5) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Status: No, hits=3.3 required=5.0 tests=MISSING_MIMEOLE,MISSING_OUTLOOK_NAME,MSG_ID_ADDED_BY_MTA_3, SPAM_PHRASE_00_01 version=2.42 X-Spam-Level: *** X-Sanitizer: This message has been sanitized! X-Sanitizer-URL: http://mailtools.anomy.net/ X-Sanitizer-Rev: $Id: Sanitizer.pm,v 1.54 2002/02/15 16:59:07 bre Exp $ Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hi I've been having this problem all year on several systems, its quite annoying. I'll take my home network as an example. I use syslog-ng 1.4.15 on freebsd 4.6.2. I have a couple debian machines, a redhat machine, a suse machine log to it. Most of the time its fine, but at seemingly random points it stops logging until i kill -HUP it. All the machines are on the same LAN connected together with a high performance 48port switch. I was thinking of trying to write some kind of script that uses the logger command then searches the recent log entries for a result but would prefer something more reliable(I'm not that great at scripting yet) if there is something out there. I've had this problem on freebsd 4.4 and 4.6.0 as well using syslog-ng on those systems as well. Random times syslog-ng just dies and doesn't log. I use logrotate and completely kill and restart syslog-ng each week but that doesn't seem to help. the process itself doesn't exit, it doesn't print any errors, it just stops responding. this particular machine is a k6-3 400 with 2MB L3 cache, 384MB ram, running 2 Ultrawide SCSI disks connected to a 2940UW controller. My other systems with freebsd were p3-1ghz, 512MB ECC ram, with IDE disks connected to a promise ATA/66 controller. no other problems on the systems that I can notice..just syslog-ng. any ideas? searching around on google didn't turn up much for me, most other experiences I see include syslog-ng completely crashing, not just hanging. it's most annoying because sometimes I don't notice it down for a couple days, and all those log entries for that time are gone forever:( thanks nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message