On 29-11-2011 22:21, Gorm J. Siiger wrote:
I'm currently in the progress of upgrading/replacing my old hobbit version 4.2.0 to 4.3.4 I have installed on a brand new server and I'm just testing if everything is ok.
My SMS alert script seems to work ok, but the BBALPHAMSG variable seems to be truncated to around 12-16 characters, leaving the status messages incomplete. I can easily add $DOWNSECS and/or $DOWNSECSMSG and they are added to the message which then is longer of cause.
Does the attached patch solve it ? Against 4.3.6.
Regards, Henrik
On 12/06/11 09:32, Henrik Størner wrote:
On 29-11-2011 22:21, Gorm J. Siiger wrote:
I'm currently in the progress of upgrading/replacing my old hobbit version 4.2.0 to 4.3.4 I have installed on a brand new server and I'm just testing if everything is ok.
My SMS alert script seems to work ok, but the BBALPHAMSG variable seems to be truncated to around 12-16 characters, leaving the status messages incomplete. I can easily add $DOWNSECS and/or $DOWNSECSMSG and they are added to the message which then is longer of cause.
Does the attached patch solve it ? Against 4.3.6.
Hi Henrik. Thanks for the quick patch butI am not sure that his completely fixed the issue. For example, it appears that the first line now looks OK:
I run a printenv > /tmp/SMS>log in my alert script, and BBALPHAMSG looks like:
BBALPHAMSG=host.example.com:cpu yellow [800718] &yellow Load is HIG
^^^^^--- Is that 2nd line to supposed to be there or is this an IFS issue on my end? Either way, it appears just like that with the second line starting with the & and it also appears to be truncated at the 2nd "H" in HIGH
What is the format of the BBALPHAMSG supposed to look like (eg: the format and list of fields) when FORMAT=SMS so I know what I am looking for as we move forward?
Thanks!
-- Bill Arlofski Reverse Polarity, LLC http://www.revpol.com/
On 06-12-2011 22:49, Bill Arlofski wrote:
I run a printenv> /tmp/SMS>log in my alert script, and BBALPHAMSG looks like:
BBALPHAMSG=host.example.com:cpu yellow [800718] &yellow Load is HIG
^^^^^--- Is that 2nd line to supposed to be there or is this an IFS issue on my end? Either way, it appears just like that with the second line starting with the& and it also appears to be truncated at the 2nd "H" in HIGH
What is the format of the BBALPHAMSG supposed to look like (eg: the format and list of fields) when FORMAT=SMS so I know what I am looking for as we move forward?
The SMS format should be like this:
HOSTNAME:TESTNAME COLOR [ACK-COOKIE]
followed by any lines in the status message that begin with "&red", "&yellow" or "&purple".
It would be interesting to see the full status message. Could you run this command while some of the alerts happen:
xymoncmd xymond_channel --channnel=page cat >/var/tmp/alertfeed.txt
and then pick out one or more of the problem alert messages and send to me ?
Thanks, Henrik
On 12/06/11 17:03, Henrik Størner wrote:
It would be interesting to see the full status message. Could you run this command while some of the alerts happen:
xymoncmd xymond_channel --channnel=page cat >/var/tmp/alertfeed.txt
and then pick out one or more of the problem alert messages and send to me ?
Thanks, Henrik
Requested information sent to private email.
-- Bill Arlofski Reverse Polarity, LLC http://www.revpol.com/
On 07-12-2011 22:02, Bill Arlofski wrote:
On 12/06/11 17:03, Henrik Størner wrote:
It would be interesting to see the full status message. Could you run this command while some of the alerts happen:
xymoncmd xymond_channel --channnel=page cat>/var/tmp/alertfeed.txt
and then pick out one or more of the problem alert messages and send to me ?
Requested information sent to private email.
Very helpful, thanks. This patch should put the final touches on fixing this bug.
Regards, Henrik
On 12/07/11 16:46, Henrik Størner wrote:
On 07-12-2011 22:02, Bill Arlofski wrote:
Requested information sent to private email.
Very helpful, thanks. This patch should put the final touches on fixing this bug.
Hi Henrik, just a quick question.
Do I need to apply this patch to xymond/do_alert.c along with the smaller patch that you posted on Dec 6 2011, or just this new one?
In other words, will you be backing the previous patch out, or is it also required as part of a complete fix for this truncating of BBALPHAMSG issue?
I will patch accordingly, then test and report back as soon as I hear from you.
Thanks!
-- Bill Arlofski Reverse Polarity, LLC http://www.revpol.com/
On Thu, 08 Dec 2011 09:29:12 -0500, Bill Arlofski <waa-hobbitml at revpol.com> wrote:
On 12/07/11 16:46, Henrik Størner wrote:
On 07-12-2011 22:02, Bill Arlofski wrote:
Requested information sent to private email.
Very helpful, thanks. This patch should put the final touches on fixing this bug.
Hi Henrik, just a quick question.
Do I need to apply this patch to xymond/do_alert.c along with the smaller patch that you posted on Dec 6 2011, or just this new one?
The new one goes on top of the previous one, so no backing out any patches.
Regards, Henrik
On 12/08/11 09:32, henrik at hswn.dk wrote:
On Thu, 08 Dec 2011 09:29:12 -0500, Bill Arlofski <waa-hobbitml at revpol.com> wrote:
On 12/07/11 16:46, Henrik Størner wrote:
On 07-12-2011 22:02, Bill Arlofski wrote:
Requested information sent to private email.
Very helpful, thanks. This patch should put the final touches on fixing this bug.
Hi Henrik, just a quick question.
Do I need to apply this patch to xymond/do_alert.c along with the smaller patch that you posted on Dec 6 2011, or just this new one?
The new one goes on top of the previous one, so no backing out any patches.
Regards, Henrik
This appears to have fixed it. Since I applied it, I have not seen a single issue with the BBALPHAMSG being truncated including the additional lines that start with &COLOR .....
Thanks!
-- Bill Arlofski Reverse Polarity, LLC http://www.revpol.com/
Henrik... I think I spoke too soon... on recovery, BBALPHAMSG looks like:
--[snip]-- BBALPHAMSG=host.example.com:cpu RECOVERE --[snip]--
This is patched 4.3.6
-- Bill Arlofski Reverse Polarity, LLC http://www.revpol.com/
participants (2)
-
henrik＠hswn.dk
-
waa-hobbitml＠revpol.com