[Xymon] Unable to drop content checks

[Mike Burger]

Resending to list, as I somehow managed to send the reply only to Ralph.

-------- Original Message --------
Subject: Re: [Xymon] Unable to drop content checks
Date: 2014-10-15 2:46 am
 From: Mike Burger <mburger at bubbanfriends.org>
To: Ralph Mitchell <ralphmitchell at gmail.com>

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
> <mburger at bubbanfriends.org> 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 <mburger at bubbanfriends.org>
>> 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.

-- 
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