Date: Mon, 28 Nov 2011 18:50:43 -0500 From: Jon Radel <jon@radel.com> To: Kaya Saman <kayasaman@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: Alternative to syslogd that actually writes external logs to files? Message-ID: <4ED41E53.6000403@radel.com> In-Reply-To: <4ED41C5F.3030906@gmail.com> References: <4ED38578.1000501@gmail.com> <CA%2BtpaK0rkWX8G3hiapZkutK6xvb%2Bc0z6aTK=U=RsC=Pk68mCEA@mail.gmail.com> <4ED3CE66.4020903@gmail.com> <4ED3D9BF.701@my.gd> <4ED41C5F.3030906@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/28/11 6:42 PM, Kaya Saman wrote: > > However, when using tcpdump it shows that rsyslog is infact receiving > information but still unfortunately not logging to file??? > > > # tcpdump -tlnvv -i em0 port 514 > tcpdump: listening on em0, link-type EN10MB (Ethernet), capture size 96 > bytes > IP (tos 0x0, ttl 255, id 1875, offset 0, flags [none], proto UDP (17), > length 142) > 192.168.1.1.59189 > 192.168.1.120.514: SYSLOG, length: 114 > Facility local7 (23), Severity notice (5) > Msg: 11578: 011565: Nov 28 23:34:19.475: %SYS-5-CONFIG[|syslog] > > > > File permissions are correct as I got rsyslog to create the file from > scratch....... > > What am I missing here? Have you tried with all firewalling on the machine turned off? [My apologies if this has been covered earlier in the thread and I missed it.] --Jon Radel jon@radel.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4ED41E53.6000403>