xymonlaunch stuck purple
Hello,
I just installed my first stand alone client reporting to my xymon server. During setup, I did something that caused xymonlaunch to crash. The xymonlauch red alert said, "- Program crashed Fatal Signal Caught!" I think it had something to do with permissions as I FTP'd the clientlauch.cfg over as root and the file was secured as root:root:. I believe the error was a signal 6??? maybe 5? ... Anyway, I fixed the permissions, and bounced the client, and things came up and are working.
However, my "xymonlaunch" alert is now stuck in a "purple" state. The logs all look good, and I can tell that other xymon alerts for this client are reporting correctly. I also notice that my other system, the server/client system, shows a "-" for the xymonlaunch. This leads me to believe that this "xymonlaunch" alert is not configured to report unless there is a problem. If my assumption is correct, how can I clear the "purple" alert?
-- Michael Beatty Sherwin-Williams IT Analyst/Developer michael.beatty at sherwin.com 216-515-7374
On Thu, Feb 23, 2012 at 5:36 AM, Michael Beatty <Michael.Beatty at sherwin.com> wrote:
believe that this "xymonlaunch" alert is not configured to report unless there is a problem. If my assumption is correct, how can I clear the "purple" alert?
As per the "Hints and Tips" page, use the "xymon" command with a "drop" option. Such as:
~/server/bin/xymon 127.0.0.1 "drop HOSTNAME xymonlaunch"
I have used "drop" plenty of times to remove alerts, and thought about doing that. However, as per the hints and tips it, "permanently removes all traces of a test". Since the xymonlaunch alert is built into the code and not a user defined alert that can be added back, I have a concern about permanently removing all traces of it. If it happens again, I'd like to know about it. If I permanently remove the test via the "drop" command, will it come back should the problem happen again?
Michael Beatty Sherwin-Williams IT Analyst/Developer michael.beatty at sherwin.com 216-515-7374
Jeremy Laidman wrote:
On Thu, Feb 23, 2012 at 5:36 AM, Michael Beatty <Michael.Beatty at sherwin.com> wrote:
believe that this "xymonlaunch" alert is not configured to report unless there is a problem. If my assumption is correct, how can I clear the "purple" alert? As per the "Hints and Tips" page, use the "xymon" command with a "drop" option. Such as:
~/server/bin/xymon 127.0.0.1 "drop HOSTNAME xymonlaunch"
How about setting the status to green with a time of many days?
Paul Root - Senior Engineer Managed Services Systems - CenturyLink
-----Original Message----- From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of Michael Beatty Sent: Thursday, February 23, 2012 6:44 AM To: Jeremy Laidman Cc: xymon at xymon.com Subject: Re: [Xymon] xymonlaunch stuck purple
I have used "drop" plenty of times to remove alerts, and thought about doing that. However, as per the hints and tips it, "permanently removes all traces of a test". Since the xymonlaunch alert is built into the code and not a user defined alert that can be added back, I have a concern about permanently removing all traces of it. If it happens again, I'd like to know about it. If I permanently remove the test via the "drop" command, will it come back should the problem happen again?
Michael Beatty Sherwin-Williams IT Analyst/Developer michael.beatty at sherwin.com 216-515-7374
Jeremy Laidman wrote:
On Thu, Feb 23, 2012 at 5:36 AM, Michael Beatty <Michael.Beatty at sherwin.com> wrote:
believe that this "xymonlaunch" alert is not configured to report unless there is a problem. If my assumption is correct, how can I clear the "purple" alert? As per the "Hints and Tips" page, use the "xymon" command with a "drop" option. Such as:
~/server/bin/xymon 127.0.0.1 "drop HOSTNAME xymonlaunch"
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
Yes it will come back, the drop command only removes it from the logs on the Xymon server, if a client resends the test it will reappear in Xymon.
Steve
On 23 February 2012 12:44, Michael Beatty <Michael.Beatty at sherwin.com>wrote:
I have used "drop" plenty of times to remove alerts, and thought about doing that. However, as per the hints and tips it, "permanently removes all traces of a test". Since the xymonlaunch alert is built into the code and not a user defined alert that can be added back, I have a concern about permanently removing all traces of it. If it happens again, I'd like to know about it. If I permanently remove the test via the "drop" command, will it come back should the problem happen again?
Michael Beatty Sherwin-Williams IT Analyst/Developer michael.beatty at sherwin.com 216-515-7374
Jeremy Laidman wrote:
On Thu, Feb 23, 2012 at 5:36 AM, Michael Beatty <Michael.Beatty at sherwin.com> wrote:
believe that this "xymonlaunch" alert is not configured to report unless there is a problem. If my assumption is correct, how can I clear the "purple" alert? As per the "Hints and Tips" page, use the "xymon" command with a "drop" option. Such as:
~/server/bin/xymon 127.0.0.1 "drop HOSTNAME xymonlaunch"
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
On Thu, Feb 23, 2012 at 11:44 PM, Michael Beatty <Michael.Beatty at sherwin.com> wrote:
However, as per the hints and tips it, "permanently removes all traces of a test".
This should probably read "permanently removes all traces of a test's history". It doesn't disable the test from accepting future events.
J
participants (4)
-
jlaidman＠rebel-it.com.au
-
Michael.Beatty＠sherwin.com
-
Paul.Root＠centurylink.com
-
sjcarr＠gmail.com