Xymon Mailing List Archive search

Unable to drop content checks

5 messages in this thread

list Mike Burger · Tue, 14 Oct 2014 08:50:01 -0400 ·
 

Good morning, all.

Running Xymon 4.3.17, I've tried every magical incantation of the
"xymon" command with the "drop" parameter that I can think of, but I
haven't been able to get Xymon to drop 3 previously configured content
checks.

I've updated the hosts.cfg file to remove the cont= tests from the
host's entry (content check/column names were ptlcls1, ptlcls2 and
ptlcls3).

I've tried:

xymon <hostname.of.xymon> "drop <client-host-name> ptlcls1" (as well as
ptlcls2 and ptlcls3)

I've also tried:

xymon <hostname.of.xymon> "drop <client-host-name> cont"

But the tests continue to show up in the alarms list or in the disabled
list, as I've now disabled them in order to clear my board of alarms.

Am I missing something, doing something wrong, or am I just going to
have to drop the client from Xymon (thereby losing its history) and
re-add it (obviously, not really a great option)?

Thank you.

-- 
Mike Burger
http://www.bubbanfriends.org

"It's always suicide-mission this, save-the-planet that. No one ever
just stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1
list Jeremy Laidman · Wed, 15 Oct 2014 11:17:06 +1100 ·
Could it be "content" or perhaps "http"?
quoted from Mike Burger


On 14 October 2014 23:50, Mike Burger <user-cc5c6e80f4c5@xymon.invalid> wrote:
 Good morning, all.

Running Xymon 4.3.17, I've tried every magical incantation of the "xymon" command with the "drop" parameter that I can think of, but I haven't been able to get Xymon to drop 3 previously configured content checks.

I've updated the hosts.cfg file to remove the cont= tests from the host's entry (content check/column names were ptlcls1, ptlcls2 and ptlcls3).

I've tried:

xymon <hostname.of.xymon> "drop <client-host-name> ptlcls1" (as well as ptlcls2 and ptlcls3)

I've also tried:

xymon <hostname.of.xymon> "drop <client-host-name> cont"
But the tests continue to show up in the alarms list or in the disabled list, as I've now disabled them in order to clear my board of alarms.

Am I missing something, doing something wrong, or am I just going to have to drop the client from Xymon (thereby losing its history) and re-add it (obviously, not really a great option)?

Thank you.

--
Mike Burger http://www.bubbanfriends.org

"It's always suicide-mission this, save-the-planet that. No one ever just stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1

list Mike Burger · Tue, 14 Oct 2014 20:31:41 -0400 ·
I did run the drop http, but I can try the content option.
quoted from Jeremy Laidman

On 2014-10-14 8:17 pm, Jeremy Laidman wrote:
Could it be "content" or perhaps "http"?

On 14 October 2014 23:50, Mike Burger <user-cc5c6e80f4c5@xymon.invalid>
wrote:
Good morning, all.

Running Xymon 4.3.17, I've tried every magical incantation of the
"xymon" command with the "drop" parameter that I can think of, but I
haven't been able to get Xymon to drop 3 previously configured
content checks.

I've updated the hosts.cfg file to remove the cont= tests from the
host's entry (content check/column names were ptlcls1, ptlcls2 and
ptlcls3).

I've tried:

xymon <hostname.of.xymon> "drop <client-host-name> ptlcls1" (as well
as ptlcls2 and ptlcls3)

I've also tried:

xymon <hostname.of.xymon> "drop <client-host-name> cont"

But the tests continue to show up in the alarms list or in the
disabled list, as I've now disabled them in order to clear my board
of alarms.

Am I missing something, doing something wrong, or am I just going to
have to drop the client from Xymon (thereby losing its history) and
re-add it (obviously, not really a great option)?

Thank you.

--
Mike Burger

http://www.bubbanfriends.org [1]
quoted from Jeremy Laidman

"It's always suicide-mission this, save-the-planet that. No one ever
just stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1

Links:
[1] http://www.bubbanfriends.org
[2]
quoted from Jeremy Laidman
-- 
Mike Burger
http://www.bubbanfriends.org

"It's always suicide-mission this, save-the-planet that. No one ever just stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1
list Ralph Mitchell · Tue, 14 Oct 2014 20:53:26 -0400 ·
The way you wrote:

     xymon <hostname.of.xymon> "drop ......."

suggests you're not doing this on the Xymon server?  If not, you might want
to try that.  The server may not accept drops from remote sources.

     xymon localhost "drop ....."

Ralph Mitchell


On Tue, Oct 14, 2014 at 8:31 PM, Mike Burger <user-cc5c6e80f4c5@xymon.invalid>
quoted from Mike Burger
wrote:
I did run the drop http, but I can try the content option.


On 2014-10-14 8:17 pm, Jeremy Laidman wrote:
Could it be "content" or perhaps "http"?

On 14 October 2014 23:50, Mike Burger <user-cc5c6e80f4c5@xymon.invalid>
wrote:

 Good morning, all.
Running Xymon 4.3.17, I've tried every magical incantation of the
"xymon" command with the "drop" parameter that I can think of, but I
haven't been able to get Xymon to drop 3 previously configured
content checks.

I've updated the hosts.cfg file to remove the cont= tests from the
host's entry (content check/column names were ptlcls1, ptlcls2 and
ptlcls3).

I've tried:

xymon <hostname.of.xymon> "drop <client-host-name> ptlcls1" (as well
as ptlcls2 and ptlcls3)

I've also tried:

xymon <hostname.of.xymon> "drop <client-host-name> cont"

But the tests continue to show up in the alarms list or in the
disabled list, as I've now disabled them in order to clear my board
of alarms.

Am I missing something, doing something wrong, or am I just going to
have to drop the client from Xymon (thereby losing its history) and
re-add it (obviously, not really a great option)?

Thank you.

--
Mike Burger
http://www.bubbanfriends.org [1]

"It's always suicide-mission this, save-the-planet that. No one ever
just stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1

Links:
[1] http://www.bubbanfriends.org
[2]
--
Mike Burger
http://www.bubbanfriends.org

"It's always suicide-mission this, save-the-planet that. No one ever just
stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1

list Mike Burger · Wed, 15 Oct 2014 08:28:11 -0400 ·
Resending to list, as I somehow managed to send the reply only to Ralph.
quoted from Mike Burger

-------- Original Message --------
Subject: Re: [Xymon] Unable to drop content checks
Date: 2014-10-15 2:46 am
 From: Mike Burger <user-cc5c6e80f4c5@xymon.invalid>
To: Ralph Mitchell <user-00a5e44c48c0@xymon.invalid>

On 2014-10-14 8:53 pm, Ralph Mitchell wrote:
The way you wrote:

     xymon <hostname.of.xymon> "drop ......."

suggests you're not doing this on the Xymon server?  If not, you might
want to try that.  The server may not accept drops from remote
sources.

     xymon localhost "drop ....."

Ralph Mitchell

On Tue, Oct 14, 2014 at 8:31 PM, Mike Burger
<user-cc5c6e80f4c5@xymon.invalid> wrote:
I did run the drop http, but I can try the content option.

On 2014-10-14 8:17 pm, Jeremy Laidman wrote:

Could it be "content" or perhaps "http"?

On 14 October 2014 23:50, Mike Burger <user-cc5c6e80f4c5@xymon.invalid>
wrote:

Good morning, all.

Running Xymon 4.3.17, I've tried every magical incantation of the
"xymon" command with the "drop" parameter that I can think of, but
I
haven't been able to get Xymon to drop 3 previously configured
content checks.

I've updated the hosts.cfg file to remove the cont= tests from the
host's entry (content check/column names were ptlcls1, ptlcls2 and
ptlcls3).

I've tried:

xymon <hostname.of.xymon> "drop <client-host-name> ptlcls1" (as
well
as ptlcls2 and ptlcls3)

I've also tried:

xymon <hostname.of.xymon> "drop <client-host-name> cont"

But the tests continue to show up in the alarms list or in the
disabled list, as I've now disabled them in order to clear my board
of alarms.

Am I missing something, doing something wrong, or am I just going
to
have to drop the client from Xymon (thereby losing its history) and
re-add it (obviously, not really a great option)?

Thank you.
Actually, I am running the commands locally, from the actual xymon server...I've just had better luck running the command while specifying the actual hostname of FQDN than I have specifying localhost, in the past.

I've tried "localhost" as well, to no avail.
quoted from Ralph Mitchell

-- 
Mike Burger
http://www.bubbanfriends.org

"It's always suicide-mission this, save-the-planet that. No one ever just stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1