Re: [Bigsister-general] Module config Syntax

["Seann Clark" <suppressed>]

One other issue I am having is on a windows system. It is running Windows XP x64bit edition. Only the messages item ends up green, the other ones show up as either unavailable or purple. The only real error stuff I could find is from running 
uxmon.exe manually:

starting
included files:
WARNING: test 'network' without DESCR in uxmon-net is deprecated!
Tue Oct  9 20:54:58 2007: uxmon.exe: check disk failed to start up - ignored
WARNING: test 'procs' without DESCR in uxmon-net is deprecated!
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
WARNING: test 'procs' without DESCR in uxmon-net is deprecated!
WARNING: test 'load' without DESCR in uxmon-net is deprecated!
WARNING: test 'memory' without DESCR in uxmon-net is deprecated!
Tue Oct  9 20:54:59 2007: uxmon.exe: check service failed to start up - ignored
Tue Oct  9 20:54:59 2007: uxmon.exe: check service failed to start up - ignored
current: HASH(0x2e9f280), previous: HASH(0x28c549c)
current: HASH(0x2e9f280), previous: HASH(0x28c549c)
current: HASH(0x2e9f280), previous: HASH(0x28c549c)
current: HASH(0x2e9f280), previous: HASH(0x28c549c)
current: HASH(0x2e73b88), previous: HASH(0x2e5390c)
current: HASH(0x2e73b88), previous: HASH(0x2e5390c)
current: HASH(0x2e73b88), previous: HASH(0x2e5390c)
current: HASH(0x28c231c), previous: HASH(0x2e62bd4)
Tue Oct  9 20:55:59 2007: uxmon.exe: config file /Program Files (x86)/BigSister/
/adm/uxmon-net has changed - reloading
WARNING: test 'network' without DESCR in uxmon-net is deprecated!
Tue Oct  9 20:55:59 2007: uxmon.exe: check disk failed to start up - ignored
WARNING: test 'procs' without DESCR in uxmon-net is deprecated!
WARNING: test 'procs' without DESCR in uxmon-net is deprecated!
WARNING: test 'load' without DESCR in uxmon-net is deprecated!
WARNING: test 'memory' without DESCR in uxmon-net is deprecated!
Tue Oct  9 20:56:00 2007: uxmon.exe: check service failed to start up - ignored
Tue Oct  9 20:56:00 2007: uxmon.exe: check service failed to start up - ignored
current: HASH(0x2e601e0), previous: HASH(0x2eadd9c)
current: HASH(0x2e601e0), previous: HASH(0x2eadd9c)
current: HASH(0x2e601e0), previous: HASH(0x2eadd9c)
current: HASH(0x2e601e0), previous: HASH(0x2eadd9c)
current: HASH(0x2e73ff0), previous: HASH(0x2e6258c)
current: HASH(0x2e73ff0), previous: HASH(0x2e6258c)
current: HASH(0x2e73ff0), previous: HASH(0x2e6258c)
current: HASH(0x2e17df0), previous: HASH(0x2e5378c)
Tue Oct  9 20:58:00 2007: uxmon.exe: config file /Program Files (x86)/BigSister/
/adm/uxmon-net has changed - reloading
WARNING: test 'network' without DESCR in uxmon-net is deprecated!
Tue Oct  9 20:58:00 2007: uxmon.exe: check disk failed to start up - ignored
WARNING: test 'procs' without DESCR in uxmon-net is deprecated!
WARNING: test 'procs' without DESCR in uxmon-net is deprecated!
WARNING: test 'load' without DESCR in uxmon-net is deprecated!
WARNING: test 'memory' without DESCR in uxmon-net is deprecated!
Tue Oct  9 20:58:01 2007: uxmon.exe: check service failed to start up - ignored
Tue Oct  9 20:58:01 2007: uxmon.exe: check service failed to start up - ignored
current: HASH(0x2e62730), previous: HASH(0x2b90164)
current: HASH(0x2e62730), previous: HASH(0x2b90164)
current: HASH(0x2e62730), previous: HASH(0x2b90164)
current: HASH(0x2e62730), previous: HASH(0x2b90164)
current: HASH(0x2bd7e0c), previous: HASH(0x2dcd7c0)
current: HASH(0x2bd7e0c), previous: HASH(0x2dcd7c0)
current: HASH(0x2bd7e0c), previous: HASH(0x2dcd7c0)
current: HASH(0x2bccd70), previous: HASH(0x2e6b764)



I have no clue about what a windows box would need for this to work properly. 


~Seann

On 10/9/07, Seann Clark <suppressed> wrote:

What I have configured right now, almost exactly out of the config for the UPS server is:

localhost(server.example.com)       load memory cpuload
localhost( server.example.com)       nutups runtimewarn=-1% runtimefail=-1% nutups

I have also tried:

localhost( server.example.com)       load memory cpuload
localhost( server.example.com)       nutups runtimewarn=-1 runtimefail=-1nutups

and
localhost(server.example.com )       load memory cpuload
localhost( server.example.com)       nutups runtimewarn=0 runtimefail=0 nutups



and none of them work.


On the other note with the LDAP, it reads all the records I have in the LDAP and reports that it is up and happy, but it also reports connection refused(-1). exactly what does that mean?


~Seann

On 10/9/07, Niels Baggesen < suppressed> wrote:

On Tue, Oct 09, 2007 at 11:53:11AM -0500, Seann Clark wrote:
> I am looking for more detailed information on testers for BigSister and how
> to format them to not always be red due to a non-reported item. What I mean
> is, I am monitoring an UPS and it is always red, runtime crit. I have tried
> the runtimecrit=-1, -1%, 0, null, etc and nothing works (same thing with the
> warn param).

For the nutups test, the proper parameter is runtimefail=

/Niels

--
Niels Baggesen - @home - Århus - Denmark - suppressed
The purpose of computing is insight, not numbers   ---   R W Hamming

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

_______________________________________________
Bigsister-general mailing list
suppressed
https://lists.sourceforge.net/lists/listinfo/bigsister-general