Counter wrapping issue

[Slacker T]

Hello,

I'm using a pretty standard config to monitor the remote queue length on an Exchange server.  I'm having a problem, whenever the counter goes over 100 (or 99, not sure) the value returned by check_nt is -1.  Has anyone else encountered this?

Relevant info:

# nagios --version
Nagios 3.0.3
...

#/usr/libexec/check_nt --version
check_nt v1991 (nagios-plugins 1.4.13)

NC_Net 4.4.0 on Server 2003 SP2

%systemroot%\Microsoft.NET\Framework\v2.0.50727\Framework\mscorlib.dll version 2.0.50727.1433

define  command {
        command_name    check_exchange_remote_queue_length
        command_line    $USER1$/check_nt -H $HOSTADDRESS$ -p 1250 -s ******** -v COUNTER -l "\\SMTP Server(_Total)\\Remote Queue Length","
Remote Queue Length is: %.f" -w $ARG1$ -c $ARG2$
        }

define service{
        use             generic-service
        host_name       exchange_server
        service_description     check_exchange_remote_queue_length
        check_command           check_exchange_remote_queue_length
        normal_check_interval   2               ; Check the service every 5 minutes under normal conditions
        retry_check_interval    1               ; Re-check the service every minute until its final/hard state is determined
        contact_groups  netadmins
        servicegroups   sites
        }

Thanks!

[tony]

Sorry for the delay,
The problem may be in Check_nt and not in NC_NEt
the few steps to debug are to check the windows event log for a NC_NEt error or warning associated with the -1 return.
IF there is none, then upgrade to Use Check_nc_net instead of check_nt
I usually just rename Check_nc_net.c to check_nt.c and recompile the plugins.

then run the help command for the counter
check_nc_net --help=COUNTER

I recomend upgrading he check command through check_nc_net to the following syntex (As per help)
-l \&quot;^COUNTERCATEGORY^CounterNAME\&quot;[,\&quot;<Label>\&quot;][,<UOM>][,<MIN>][,<MAX>]\n\ this assists check_nc_net and NC_net in properly interpreting the input appropiatly for differnt UOM types.

I have patched my Check_nc_net.c several times to take care of minor issues and inconsistancies with the way some of the check_nt processed Commands.  I have also submitted patches to check_nt several years ago that I think have still not been commited to the project.

if the upgrade to check_nc_Net does not help then try using the full syntex for the COUNTER command including the UOM since check_nc_net uses these to assist in properly parsing the output (which may have been one of the issues I had with the original Check_nt code???)

other options if the issue is in NC_NEt (which would be indicated by a Event log item or a capture of the content being returned to check_nt) If it is intermittent then the Sample delay in the starup config should be adjusted.

Hope this helps,
TOny
Donations for NC_NEt are accepted via montitech.com