syslog-ng-1.5.21 cannot listen for logging messages from a remote machine via udp. I contacted the authors at info@balabit.hu, and they said that libol 0.3.4 is broken, and to upgrade to 0.3.5 and syslog-ng-1.5.22.
Ive been bitten by this too. I found the following on the syslog-ng list On Wed, Oct 16, 2002 at 12:37:45PM +0200, Christian Hammers wrote: > Hi > > Does someone know why it worked in 1.5.13 and not in 1.5.21? > > destination qdb2 { udp("qdb2.westend.com"); }; > log { source(src); destination(qdb2); }; > > (optionally with port(514) but doesn't matter) this is a bug in libol 0.3.4, please use libol0.3.5 and syslog-ng 1.5.22. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
*** Bug 9584 has been marked as a duplicate of this bug. ***
Not just UDP, but also TCP logging.
updated. work ok for everyone? if so i can remove the ~ testing flag...
i have syslog-ng-1.5.22 and libol-0.3.5 working on PPC.
cfreeze@alumni.clemson.edu tells me that both of the current ebuilds in portage are devel versions, and are broke for udp/tcp remote logging. im not a syslog-ng user, so i've done little testing other than simple build/run excercises. if you all want/need the stable versions of these, can somebody cook up patch/ebuild to the stuff in portage, and i'll add the stuff in. if they work by just cp'ing foo.ebuild bar.ebuild that'd be nice to hear...
thanks to chris, i've added the stable versions of these pks. they are also now the most recent, stable ebuilds, as far as portage is concerned. when the troops come asking why emerge is downgrading their packages, lend a hand and point them here :P
