Henrik,
It could well be. We had no pages go out last night and I think it is because there is an 8k limit on macros in alerts.cfg. xymond_alert seg faults when one of the macros exceeds the 8k limit. Should we just assume an 8k limit and work around that or do you see making that configurable in the future? I see the limit may be set in load_alerts.c.
~David
-----Original Message----- From: henrik at hswn.dk [mailto:henrik at hswn.dk] Sent: Thursday, April 07, 2011 13:29 To: Gore, David W Cc: xymon at xymon.com Subject: Re: [Xymon] core dump, Xymon 4.3.2, loadalerts.c:308, i686 Linux RedHat 5
On Thu, 07 Apr 2011 11:52:24 +0000, "Gore, David W" <david.gore at verizonbusiness.com> wrote:
#3 0x0805ee13 in sigsegv_handler (signum=11) at sig.c:57 #4 <signal handler called> #5 0x006b2eca in strcmp () from /lib/libc.so.6 #6 0x08053e4f in preprocess (buf=<value optimized out>) at loadalerts.c:138 #7 0x08054272 in load_alertconfig (configfn=0x0, defcolors=56, defaultinterval=1800) at loadalerts.c:308 #8 0x0804aafa in main (argc=1918990080, argv=0xbff783a4) at xymond_alert.c:831
Looks like it is related to some macro in your config file.
Is there an easy way to verify your files in analysis.d when it refers to line numbers in the logs and you use multiple include files?
"xymoncmd xymoncfg analysis.cfg" will dump the file following all the include's.
Regards, Henrik