[syslog-ng] Not all messages getting to program destination
Martin Holste
mcholste at gmail.com
Wed Apr 13 17:52:28 CEST 2011
Swap out the python script with a different python script which simply
writes to a file and verify that looks the way it should (matches your
grep). That should narrow things down.
On Tue, Apr 12, 2011 at 5:51 PM, Bill Anderson
<Bill.Anderson at bodybuilding.com> wrote:
>
> Setup:
> v3.1
> program destination: python script
> secondary file destination in the _same_ log block (so it should be getting everything the program destination gets), no final flag.
> stats turned on, 60s interval.
>
> Problem:
> In the script I am tallying lines parsed per minute. The lines parsed per-minute is not matching a grep -c on the file destination. stats indicate no dropped or queued messages to either destination. If I cat the file to the same destination script on the command line, I get the same counts as I do grepping the file directly. I would expect that the script would return the same results from the shell as when running as a destination in syslog.
>
> Where else can I look/what else can I turn on, to see why the discrepancy exists?
>
>
>
> Cheers,
> Bill
>
> --
> Bill Anderson, RHCE
> Linux Systems Engineer
> bill.anderson at bodybuilding.com
>
>
>
> ______________________________________________________________________________
> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
> Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
> FAQ: http://www.campin.net/syslog-ng/faq.html
>
>
More information about the syslog-ng
mailing list