From owner-freebsd-questions@FreeBSD.ORG Sun Mar 13 19:19:00 2011 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 1F278106566C for ; Sun, 13 Mar 2011 19:19:00 +0000 (UTC) (envelope-from LConrad@Go2France.com) Received: from mgw1.MEIway.com (mgw1.meiway.com [81.255.84.75]) by mx1.freebsd.org (Postfix) with ESMTP id CBB458FC1B for ; Sun, 13 Mar 2011 19:18:59 +0000 (UTC) Received: from VirusGate.MEIway.com (virusgate.meiway.com [81.255.84.76]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id 8186147184C for ; Sun, 13 Mar 2011 20:19:01 +0100 (CET) Received: from mail.Go2France.com (ms1.meiway.com [81.255.84.73]) by VirusGate.MEIway.com (Postfix) with ESMTP id 031843865B4 for ; Sun, 13 Mar 2011 20:19:02 +0100 (CET) (envelope-from LConrad@Go2France.com) Received: from W500.Go2France.com [69.4.62.57] by mail.Go2France.com with ESMTP (SMTPD32-7.07) id A8B321D801A0; Sun, 13 Mar 2011 20:19:15 +0100 X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Sun, 13 Mar 2011 14:18:49 -0500 To: freebsd-questions@freebsd.org From: Len Conrad In-Reply-To: References: <201103112331.AA2596602004@mail.Go2France.com> <201103122240713.SM06140@W500.Go2France.com> <3E21B80B-7386-4B4F-9B50-E87AA8D843DA@boosten.org> <201103122306135.SM06140@W500.Go2France.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Message-Id: <201103132019510.SM06140@W500.Go2France.com> Subject: Re: syslog-ng logging stopped 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: Sun, 13 Mar 2011 19:19:00 -0000 >May it be a permission issue (fs or /dev/kmem or the like)? syslog-ng or syslogd as root doesn't enable log writing. > Can you >manually start syslog-ng or syslogd with verbose flags enabled? I edited rc.d/syslog-ng script to add -d of course, nothing is logged, so -d doesn't help. Len >Man, you really stumbled upon something weird! > >On 3/12/11, Len Conrad wrote: >> At 03:52 PM 3/12/2011, you wrote: >>>That probably means that it's not syslog-ng causing the problems. >> >> right >> >>>Maybe some firewall rule? >> >> I run pf. pfctl -d didn't allow logging to start. trafshow and tshark >> showed >> all the traffic hitting port 514, not being blocked. >> >> Len >> >> >> >> _______________________________________________ >> 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" >> > > >-- >Iñigo Ortiz de Urbina Cazenave >http://www.twitter.com/ioc32