TS - Disabled and cannot Enable it

older
Unable to showing graph, "trends"...

d.tom.schmitt＠L-3com.com

6 Apr 2011 6 Apr '11

5:30 p.m.

I have printer: Printer143

It is disabled and was done so using the command:

            $BB $BBDISP "disable ${HOST}.* -1 offline"    to allow a

'ping' to enable it

It is BLUE and querying it shows that it is BLUE:

            /home/xymon/server/bin/bb 127.0.0.1 "query

Printer142.conn"

           blue &lt;!-- [flags:OrdAsTLe] --> Wed Apr  6 10:58:39 2011

conn ok

If you go to the 'conn' web page for Printer142, it shows:

            BLUE boarder and BLUE ICON but under history, it shows:

            GREEN diamond IP-of-Printer is alive (0.57 ms)

The device answers a 'ping'.

I when into ADMINISTATION: Enable/Disable and enabled the Printer.

There are no devices left to Enable.

I stopped and restarted Xymon also.

I tried to 'enable' the Printer with:

            /home/xymon/server/bin/bb 127.0.0.1 "enable

Printer142.conn"

            Multiple times

But the device still shows BLUE/DISABLED.

I am running Xymon 4.3.0-0.beta2 and have been for over a year and have not experienced this problem.

I monitor multiple printers in multiple buildings and this is happening to 14 out of 28 Printers.

Is there a way to get these devices ENABLED again short of removing and loading them again?

Thanks,

Tom Schmitt

Senior IT Staff - R&D

L-3 Communication Systems West

640 North 2200 West

P.O. Box 16850

Salt Lake City, UT 84116

Phone (801) 594-3030

Cell (801) 231-7230

eFax (413) 480-6873

D.Tom.Schmitt at L-3Com.com

       \\\\||////

         \ ~  ~ /  

         | @  @ |

--oOo---(_)---oOo--

Show replies by date

tlewick＠tradebotsystems.com

6 Apr 6 Apr

6:28 p.m.

New subject: Xymon, external script question

Hi all, we manage several hundred hosts, and we've noticed when doing maintenance that requires shutdown/reboot that occasionally (seldom) on restart one or more of the memory modules in a given host isn't detected. Sometimes it requires reseating the memory, sometimes just a reboot, sometimes the memory is bad. Thus we have a need to write a script that will check the amount of memory each host sees, and send an email/alert if its below a given amount.

So I thought why not make use of xymon and the memory test you get for free. A large percentage of our hosts >60% have exactly 6 GB of memory, but a large percentage does not. So I was wondering if there is a way to make use of the hobbit-clients.cfg script where I could set alert thresholds for a new external script.

The default value for any host would be alert if less than 6.0 GB of memory is detected, but I could set custom alerts for given hosts that have more or less than this amount.

I don't believe its possible to use hobbit-client.cfg file in this way, but wanted to check with the list and hope I'm wrong.

Thanks, Taylor

novosirj＠umdnj.edu

9:02 p.m.

New subject: Xymon, external script question

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Please do not thread hijack (in this case, the thread originated by d.tom.schmitt). Thank you.

On 04/06/2011 02:28 PM, Taylor Lewick wrote:

...

Hi all, we manage several hundred hosts, and we?ve noticed when doing maintenance that requires shutdown/reboot that occasionally (seldom) on restart one or more of the memory modules in a given host isn?t detected. Sometimes it requires reseating the memory, sometimes just a reboot, sometimes the memory is bad. Thus we have a need to write a script that will check the amount of memory each host sees, and send an email/alert if its below a given amount.

So I thought why not make use of xymon and the memory test you get for free. A large percentage of our hosts >60% have exactly 6 GB of memory, but a large percentage does not. So I was wondering if there is a way to make use of the hobbit-clients.cfg script where I could set alert thresholds for a new external script.

The default value for any host would be alert if less than 6.0 GB of memory is detected, but I could set custom alerts for given hosts that have more or less than this amount.

I don?t believe its possible to use hobbit-client.cfg file in this way, but wanted to check with the list and hope I?m wrong.

Thanks,

Taylor

Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon

---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Sr. Systems Programmer |$&| |__| | | |__/ | \| _| |novosirj at umdnj.edu - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/CST-Academic Svcs. - ADMC 450, Newark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk2c1PEACgkQmb+gadEcsb6fEACg4jOli7nblRixRTnj+6VQrgLM cW4AniIwCLD8mATnkvG4oLPW2K8N6tCa =vd7B -----END PGP SIGNATURE-----

david.baldwin＠ausport.gov.au

7 Apr 7 Apr

3:17 a.m.

New subject: Xymon, external script question

Taylor,

...

Hi all, we manage several hundred hosts, and we’ve noticed when doing maintenance that requires shutdown/reboot that occasionally (seldom) on restart one or more of the memory modules in a given host isn’t detected. Sometimes it requires reseating the memory, sometimes just a reboot, sometimes the memory is bad. Thus we have a need to write a script that will check the amount of memory each host sees, and send an email/alert if its below a given amount.

So I thought why not make use of xymon and the memory test you get for free. A large percentage of our hosts >60% have exactly 6 GB of memory, but a large percentage does not. So I was wondering if there is a way to make use of the hobbit-clients.cfg script where I could set alert thresholds for a new external script.

The MEMORY thresholds are percentage only rather than absolute amounts.

...

The default value for any host would be alert if less than 6.0 GB of memory is detected, but I could set custom alerts for given hosts that have more or less than this amount.

I don’t believe its possible to use hobbit-client.cfg file in this way, but wanted to check with the list and hope I’m wrong.

You could easily do this by checking the incoming client reports using check-client:

http://xymonton.org/doku.php/monitors:check-client

The memCheck in that test was written for incorrectly configured ESX service consoles by checking the [free] section. Easily enough modified to check [memory] section's "phys" line.

David.

-- David Baldwin - IT Unit Australian Sports Commission www.ausport.gov.au Tel 02 62147830 Fax 02 62141830 PO Box 176 Belconnen ACT 2616 david.baldwin at ausport.gov.au Leverrier Street Bruce ACT 2617

Keep up to date with what's happening in Australian sport visit http://www.ausport.gov.au

This message is intended for the addressee named and may contain confidential and privileged information. If you are not the intended recipient please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you receive this message in error, please delete it and notify the sender.

Phil.Crooker＠orix.com.au

5:01 a.m.

New subject: Xymon, external script question

Hi Taylor,

I'm new at xymon and am also looking at using the client data.

I found the xymon command itself lets you query current status:

/usr/local/xymon/server/bin/xymon 127.0.0.1 "xymondlog

hostname.domain.com.memory"

hostname.domain.com|memory|green||1301551188|1302151594|1302153394|0|0|10.10.10.1|-1|||Y| green Thu Apr 7 14:46:28 EST 2011 - Memory OK Memory Used Total Percentage &green Physical 9905M 11881M 83% &green Actual 514M 11881M 4% &green Swap 0M 10239M 0%

The above was run on the xymon server, hence the localhost address. It appears to display the current service status page (on the webserver) in text. So it would be pretty easy to parse out the physical memory and compare that with a value you set in the script itself.

cheers.

...

...
...
On 4/7/2011 at 3:58 AM, in message <2CB6F3BD6F4BE04EA34D80E087163D35E6073BB7 at tbmail01.tradebot.com>, Taylor Lewick <tlewick at tradebotsystems.com> wrote: Hi all, we manage several hundred hosts, and we've noticed when doing

...

maintenance that requires shutdown/reboot that occasionally (seldom) on restart one or more of the memory modules in a given host isn't detected.
Sometimes it requires reseating the memory, sometimes just a reboot,

...

sometimes the memory is bad. Thus we have a need to write a script that will check the amount of memory each host sees, and send an email/alert if its below a given amount.

So I thought why not make use of xymon and the memory test you get for free. A large percentage of our hosts >60% have exactly 6 GB of memory, but a large percentage does not. So I was wondering if there is a way to make use of the hobbit-clients.cfg script where I could set alert thresholds for a new external script.

The default value for any host would be alert if less than 6.0 GB of memory is detected, but I could set custom alerts for given hosts that have more or less than this amount.

I don't believe its possible to use hobbit-client.cfg file in this way, but wanted to check with the list and hope I'm wrong.

Thanks, Taylor

david.baldwin＠ausport.gov.au

5:30 a.m.

New subject: Xymon, external script question

Phil,

...

Hi Taylor,

I'm new at xymon and am also looking at using the client data.

I found the xymon command itself lets you query current status:

/usr/local/xymon/server/bin/xymon 127.0.0.1 "xymondlog

hostname.domain.com.memory"

hostname.domain.com|memory|green||1301551188|1302151594|1302153394|0|0|10.10.10.1|-1|||Y| green Thu Apr 7 14:46:28 EST 2011 - Memory OK Memory Used Total Percentage &green Physical 9905M 11881M 83% &green Actual 514M 11881M 4% &green Swap 0M 10239M 0%

The above was run on the xymon server, hence the localhost address. It appears to display the current service status page (on the webserver) in text. So it would be pretty easy to parse out the physical memory and compare that with a value you set in the script itself.

That gets you the status page which is what the server creates after it's processed the client message it receives.

You can get the client section directly doing:

/usr/local/xymon/server/bin/xymon 127.0.0.1 "clientlog hostname.domain.com section=memory"

[memory] memory Total Used physical: 2047 1020 virtual: 2046 890 page: 3948 1731

David.

...

cheers.

...
...
...
On 4/7/2011 at 3:58 AM, in message <2CB6F3BD6F4BE04EA34D80E087163D35E6073BB7 at tbmail01.tradebot.com>, Taylor Lewick <tlewick at tradebotsystems.com> wrote: Hi all, we manage several hundred hosts, and we've noticed when doing maintenance that requires shutdown/reboot that occasionally (seldom) on restart one or more of the memory modules in a given host isn't detected.
Sometimes it requires reseating the memory, sometimes just a reboot, sometimes the memory is bad. Thus we have a need to write a script that will check the amount of memory each host sees, and send an email/alert if its below a given amount.

So I thought why not make use of xymon and the memory test you get for free. A large percentage of our hosts >60% have exactly 6 GB of memory, but a large percentage does not. So I was wondering if there is a way to make use of the hobbit-clients.cfg script where I could set alert thresholds for a new external script.

The default value for any host would be alert if less than 6.0 GB of memory is detected, but I could set custom alerts for given hosts that have more or less than this amount.

I don't believe its possible to use hobbit-client.cfg file in this way, but wanted to check with the list and hope I'm wrong.

Thanks, Taylor

Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon

Keep up to date with what's happening in Australian sport visit http://www.ausport.gov.au

This message is intended for the addressee named and may contain confidential and privileged information. If you are not the intended recipient please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you receive this message in error, please delete it and notify the sender.

tlewick＠tradebotsystems.com

8 Apr 8 Apr

6:41 p.m.

New subject: Xymon, external script question

Thanks for the responses, I actually just ended up using the method Phil described, which I've used before in other scripts. I was just wanting to know if there was a "better" way.

I used: foreach $host (@host_list) { $host_mem_info=/home/xymon/server/bin/bb 127.0.0.1 "hobbitdlog" $host.$test" |grep -i Physical; etc... }

After my next upgrade to xymon (using xymon 4.3.0-0-beta2) looks like I'll need to use xymondlog instead of hobbitdlog

henrik＠hswn.dk

8:06 p.m.

New subject: Xymon, external script question

Taylor Lewick wrote:

...

After my next upgrade to xymon (using xymon 4.3.0-0-beta2) looks like I'll need to use xymondlog instead of hobbitdlog

I'd recommend doing so, but 4.3.0-release does work with the older "hobbit..." commands.

Regards, Henrik

thomas.eckert＠IT-Eckert.de

6 Apr 6 Apr

7:57 p.m.

No solution, but probably a hint:

Are your printer status-messages generated with a non-default lifetime?

I've seen a similar behaviour for status-msgs with a long lifetime: my suspicion is that xymon (xymongen/bbgen?) does no re-evaluation of the status-color until the lifetime expired in that case.

HTH Thomas

On 04/06/2011 07:30 PM, d.tom.schmitt at L-3com.com wrote:

...

I have printer: Printer143

It is disabled and was done so using the command:
            $BB $BBDISP "disable ${HOST}.* -1 offline"    to allow a
‘ping’ to enable it

It is BLUE and querying it shows that it is BLUE:
            /home/xymon/server/bin/bb 127.0.0.1 "query Printer142.conn"

           blue &lt;!-- [flags:OrdAsTLe] --> Wed Apr  6 10:58:39 2011
conn ok

If you go to the ‘conn’ web page for Printer142, it shows:
            BLUE boarder and BLUE ICON but under history, it shows:

            GREEN diamond IP-of-Printer is alive (0.57 ms)

           
The device answers a ‘ping’.

I when into ADMINISTATION: Enable/Disable and enabled the Printer.

There are no devices left to Enable.

I stopped and restarted Xymon also.

I tried to ‘enable’ the Printer with:
            /home/xymon/server/bin/bb 127.0.0.1 "enable Printer142.conn"

            Multiple times
But the device still shows BLUE/DISABLED.

I am running Xymon 4.3.0-0.beta2 and have been for over a year and have not experienced this problem.

I monitor multiple printers in multiple buildings and this is happening to 14 out of 28 Printers.

Is there a way to get these devices ENABLED again short of removing and loading them again?

*/Thanks,/*

*/ /*

*/Tom Schmitt/*

/Senior IT Staff - R&D/

L-3 Communication Systems West

640 North 2200 West

P.O. Box 16850

Salt Lake City, UT 84116

Phone (801) /594-3030/

Cell (801) 231-7230

eFax (413) /480-6873/

*/D.Tom.Schmitt at L-3Com.com/*

*/ /**\\\\||////**//*

*/ /**\ ~ ~ / **//*

*/ /**| @ @ | **//*

*--oOo---(_)---oOo--**//*

Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon

henrik＠hswn.dk

7 Apr 7 Apr

6:09 a.m.

...

I have printer: Printer143

It is disabled and was done so using the command:

$BB $BBDISP "disable ${HOST}.* -1 offline" to allow a ‘ping’ to enable it

It is BLUE and querying it shows that it is BLUE:

/home/xymon/server/bin/bb 127.0.0.1 "query Printer142.conn"

blue  Wed Apr 6 10:58:39 2011 conn ok

I think you made a typo here - is it Printer143 or Printer142? Assume you're talking about the same printer that you disabled ...

...

If you go to the ‘conn’ web page for Printer142, it shows:

BLUE boarder and BLUE ICON but under history, it shows:

GREEN diamond IP-of-Printer is alive (0.57 ms)

That would point to the device being disabled until some time into the future.

...

I when into ADMINISTATION: Enable/Disable and enabled the Printer.

There are no devices left to Enable.

Then it should go green when the next "conn" status update arrives. Enabling a test doesn't change the status right away, it only changes when the next status update arrives (usually within 5 minutes for the network-based tests).

...

But the device still shows BLUE/DISABLED.

What do you get from a bb 127.0.0.1 "hobbitdboard host=Printer143 test=conn fields=disabletime"

It should return 0 if it is not disabled, -1 if "disabled until OK", and a timestamp (number) if disabled until some time in the future.

...

Is there a way to get these devices ENABLED again short of removing and loading them again?

Worst case, stop Xymon, edit the tmp/hobbitd.chk file and delete the line with the hostname+testname, then start Xymon again.

Regards, Henrik

5556

Age (days ago)

5558

Last active (days ago)

List overview

Download

9 comments

7 participants

participants (7)

d.tom.schmitt＠L-3com.com
david.baldwin＠ausport.gov.au
henrik＠hswn.dk
novosirj＠umdnj.edu
Phil.Crooker＠orix.com.au
thomas.eckert＠IT-Eckert.de
tlewick＠tradebotsystems.com

TS - Disabled and cannot Enable it

d.tom.schmitt＠L-3com.com

tlewick＠tradebotsystems.com

novosirj＠umdnj.edu

david.baldwin＠ausport.gov.au

Phil.Crooker＠orix.com.au

/usr/local/xymon/server/bin/xymon 127.0.0.1 "xymondlog

david.baldwin＠ausport.gov.au

/usr/local/xymon/server/bin/xymon 127.0.0.1 "xymondlog

/usr/local/xymon/server/bin/xymon 127.0.0.1 "clientlog hostname.domain.com section=memory"

tlewick＠tradebotsystems.com

henrik＠hswn.dk

thomas.eckert＠IT-Eckert.de

henrik＠hswn.dk

tags

participants (7)