It actually looks like the host matching in the filter was the culprit. Running it as Drew suggested pointed that out very quickly. It's just using the first match, so what's the best way to get some better hostnames logged to the file? If I don't have an entry in the hosts file, can I turn off resolution for it completely so it only looks at the IP address? Looks like the long_hostnames(yes) option may work for matching my hosts file, can anyone confirm this for me? Thanks for the help! -Robin -----Original Message----- From: syslog-ng-admin@lists.balabit.hu [mailto:syslog-ng-admin@lists.balabit.hu] On Behalf Of Michael Breton Sent: Wednesday, February 19, 2003 2:10 PM To: 'syslog-ng@lists.balabit.hu' Subject: RE: [syslog-ng]Trouble using syslog-ng on Solaris 8
-----Original Message----- From: Robin Brown [mailto:robin_brown@totalcomm.com] Sent: Wednesday, February 19, 2003 1:36 PM To: syslog-ng@lists.balabit.hu Subject: [syslog-ng]Trouble using syslog-ng on Solaris 8
Hi, running solaris 8 and syslog-ng 1.5.26. It all seems to start just fine, no errors at startup or when running. But none of the logs get populated and I can see the UDP traffic is still coming in. Any way to see if it's simply not matching the host criteria for some reason?
Below is my config, any help is appreciated:
Config looks fine. What verison of libol did you install? There was a bug in a prior version that did the same thing to me. Just upgrade to the latest version of libol and recompile syslog-ng. libol does not need to be installed (Although it can be), but make sure syslog-ng isn't being compiled with the old version of libol. Michael Breton Commtel _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html