The ignore/triggercount bug has been fixed in trunk and the 4.3.18 branch,
but not released yet (https://sourceforge.net/p/xymon/code/7462/)
Also, it's worth re-iterating that logfetch uses POSIX regex's, not PCRE
ones, so some of the syntactic sugar is a different there...
Regards,
-jc
On Fri, September 12, 2014 5:36 am, Betsy Schwartz wrote:
Sorry meant to cc the previous message to the list. Correcting the line
wrapping made my lines start to take effect but also caused logfetch to
dump core
This causes a core dump:
log:/appdata/logserver/local7.log:102400
trigger brocade
ignore %.*(apcontroller|cli.WARNING|cli.NOTICE).*
This works
log:/appdata/logserver/local7.log:102400
trigger brocade
ignore apcontroller
so now, question is how to ignore more than one thing :-)
It sounds from this thread (Thanks Jeremy) that maybe multiple bogus
trigger lines would help:
http://lists.xymon.com/archive/2013-August/038002.html
---------- Forwarded message ----------
From: Betsy Schwartz <user-c61747246f66@xymon.invalid>
Date: Fri, Sep 12, 2014 at 7:44 AM
Subject: Re: [Xymon] client-local.cfg ignore a complicated line - syntax
issue?
To: Jeremy Laidman <user-71895fb2e44c@xymon.invalid>
Hm, somewhere in there I had gotten onto one line, thanks
this is for client-launch.cfg
I tried this
ignore %(?-i)apcontroller|cli.WARNING|cli.NOTICE
and got a core dump on the client
upgraded the client from 4.3.12 to 4.3.17
still got a core dump
[root at syslog1 logs]# tail xymonclient.log
/home/xymon/client/bin/xymonclient.sh: line 60: 33209 Segmentation
fault (core dumped) $XYMONHOME/bin/logfetch $LOGFETCHCFG
$LOGFETCHSTATUS >> $MSGTMPFILE