>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
That probably means that it's not syslog-ng causing the problems.
Maybe some firewall rule?
Peter
--
HTTP://www.boosten.org
On 12 mrt 2011, at 22:40, Len Conrad wrote:
-- Original Message --
From: Iñigo Ortiz de Urbina
Date: Fri, 11 Mar 2011
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
__
>-- Original Message --
>From: Iñigo Ortiz de Urbina
>Date: Fri, 11 Mar 2011 23:12:49 +0100
>
>>Whats in dmesg and /var/log/? You shared extensive and excellent
>>troubleshooting info but didnt spot none of these.
>>
>>Keep us updated im sure im not the
-- Original Message --
From: Iñigo Ortiz de Urbina
Date: Fri, 11 Mar 2011 23:12:49 +0100
>Whats in dmesg and /var/log/? You shared extensive and excellent
>troubleshooting info but didnt spot none of these.
>
>Keep us updated im sure im not the only one
uname -a
FreeBSD 7.0-RELEASE
syslog-ng --version
syslog-ng 2.0.10
change date on syslog-ng.conf is "Apr 20 2009"
syslog-ng been running untouched for that long. Millions of lines/per day log
from 10 source machine.
about 00:20 today Friday, all syslogging to syslog-ng stopped.
sockstat -4