Has anyone else experienced this, that only the last scheduled disable is shown on the enable/disable page? /Johan From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Johan Sjöberg Sent: den 17 februari 2014 13:58 To: Henrik Størner; xymon at xymon.com Subject: Re: [Xymon] Xymond crashing when scheduling disable in 4.3.15 Hi. Now it’s not crashing, but only the latest scheduled disable is listed under “Scheduled actions”. I don’t know if the other ones are still active even though they are not shown? /Johan From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Henrik Størner Sent: den 17 februari 2014 13:16 To: xymon at xymon.com<mailto:xymon at xymon.com> Subject: Re: [Xymon] Xymond crashing when scheduling disable in 4.3.15 Den 2014-02-17 12:46, Johan Sjöberg skrev: Hi. We recently updated our Xymon installation to 4.3.15. Now it seems like we cannot schedule disable from the “Enable/disable” page. We get this error in the xymond.log: Same in 4.3.16, it seems. Problem is in line 4368 - there is a "NULL" missing in the addtobuffer_many() call. Index: xymond/xymond.c =================================================================== --- xymond/xymond.c (revision 7439) +++ xymond/xymond.c (working copy) @@ -4165,7 +4165,7 @@ for (swalk = schedulehead; (swalk); swalk = swalk->next) { snprintf(tbuf, sizeof(tbuf), "%d|%d", swalk->id, (int)swalk->executiontime); - addtobuffer_many(response, tbuf, "|", swalk->sender, "|", nlencode(swalk->command)); + addtobuffer_many(response, tbuf, "|", swalk->sender, "|", nlencode(swalk->command), NULL); } xfree(msg->buf); Will put this into 4.3.17. Regards, Henrik