Hi Jeremy, Actually, that is the problem. When I remove the “—no-pin” option from CGI_ACK_OPTS in the cgioptions.cfg file, I cannot acknowledge an alert, and I get the “internal server error”. I am able to acknowledge an alert when the “—no-pin” option is included.
I want to use the “—no-pin” to force people to use an acknowledge code, so they do not acknowledge alerts for machines that they are not responsible for.
Nicole
From: Jeremy Laidman [mailto:jlaidman at rebel-it.com.au] Sent: Thursday, July 02, 2015 4:14 PM To: Nicole Beck; cleaver at terabithia.org Cc: xymon at xymon.com Subject: RE: [Xymon] Errors for acknowledge alerts in 4.3.18
On 03/07/2015 1:07 AM, "Nicole Beck" <nskyrca at syr.edu<mailto:nskyrca at syr.edu>> wrote:
I probably should add that I have removed the “—no-pin” option from the CGI_ACK_OPTS in cgioptions.cfg.
Unlikely to be related to the problem.
I'm not that familiar with working with core files, but here is the output. Hopefully I did it right.
Yes, you've done well.
Program terminated with signal 11, Segmentation fault. #0 0x0000000000402b4f in main (argc=<value optimized out>, argv=<value optimized out>) at acknowledge.c:392 392 if (strncmp(awalk->period, "hour", 4) == 0) awalk->validity *= 60; Ah. This is a bug that is triggered when specifying the ack validity period with the string "hour". I don't know the fix, but a work around might be to specify validity without units (I'm guessing it defaults to minutes).
JC, has this bug been fixed in later versions?
J