minor syslog issue
m.seaman at infracaninophile.co.uk
Fri May 1 06:25:13 UTC 2015
On 01/05/2015 00:45, William A. Mahaffey III wrote:
>> syslogd on kabini1 should be accepting traffic from all ports:
>> [root at kabini1, /etc, 6:40:19pm] 366 % ps -ax | grep syslog
>> 783 ?? Is 0:39.07 /usr/sbin/amd -p -a /.amd_mnt -l syslog /host /etc/amd.map /net /etc/amd.map
>> 73506 ?? Is 0:00.10 /usr/sbin/syslogd -a 192.168.0.0/16:* -C -T
>> 8622 4 S+ 0:00.00 grep syslog
>> 73648 7 S+ 0:00.93 tcpdump port
>> i.e. looks like the traffic is there, but syslogd isn't recording it (?) .... Any clues appreciated.
> *Aaaaaaaaaaaaack* !!!! Looks like ipfw was catching it, I had changed my
> rules to allow *some* udp traffic a few days ago, but didn't open it up
> enough. Just changed that & we'll see either later today or tomorrow at
> the next 'syslogd restart' .... Sorry for the noise :-/ ....
Looks like you've pretty much sorted the problem.
A bit late now, but you would have been able to generate syslog traffic
at will on your RPi using logger(1). Although I guess you'll still want
to observe things over a syslog restart to make sure everything works
even if the source port changes.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 971 bytes
Desc: OpenPGP digital signature
More information about the freebsd-questions