nsclient and hosed Win2K performance counters

[David Maynard]

Several bugs that caused the performance counter information to become
corrupted have been fixed in the later service packs.  However, installing
the service pack doesn't fix the problem, it just prevents it from getting
worse.  It seems to be very easy for a 3rd-party app to hose the counters as
well.

Trying to find this information on the Microsoft site is a nightmare.  I
just spent 5 minutes and didn't find any useful references.  I usually have
better luck trying Google searches that reference the Microsoft site.

The commands you need are "unlodctr" and "lodctr" (\winnt\system32).  Also
in that directory, you will find the ".ini" files that contain the
performance counter definitions.  The key is to unload the old information
and then reload it from the ini file.  The trick it to figure out what needs
to be unloaded, what it is called, and then what the associated file name
is.  Sometimes the Event Log will contain clues about which set of
performance counters is invalid.

Microsoft has several articles that tell you how to fix the IIS counters,
but I have often seen other counters become corrupted.  Unfortunately, the
best advise I can offer is to try some searches and start experimenting with
lodctr.

-----Original Message-----
From: Ralf Mellis [mailto:testrm at kisters.com]
Sent: Friday, May 09, 2003 4:38 AM
To: nagios-users at lists.sourceforge.net
Subject: Re: [Nagios-users] nsclient 1.0.7.1 vs 1.0.8.0


Tom DE BLENDE wrote:
> 
> 
> Ralf Mellis wrote:
> 
>> Looking into the eventlog of the servers, there is the entry
>> "NSClient Error: The CPU Processor counter seems to be corrupted, all 
>> CPU values will be reported as 0."
>> which corresponds to the above given result.
> 
> 
> If you check out http://support.tsmgsoftware.com/viewtopic.php?t=4 you 
> will see the small changelog. One of the things they changed was the way 
> corrupt CPU counters are reported and handeled. So you have a problem 
> that has nothing to do with NSClient, only NSCLient handles it 
> differently in the new version.
> 

Oh, I know that the problem is the w2k host, not nsclient. I only wanted 
to expose the differences between the two versions of nsclient in 
behaviour regarding corrupted counters. It may be from interest for the 
admins, who are upgrading (and not have "found" the small changelog, 
because of the difficulties with the tsmg server).

>> ...
>> What makes me crazy is the fact that the ms performance monitor has 
>> absolutely no difficulties to process _all_ indicators related to the 
>> processor object...
> That is strange indeed. Rebooted the box already?
> 

Once? Since I'm trying to "restore" these counters (two weeks or so), I 
have rebooted the server approximately 10 to 15 times...
You say "strange"? Is it so, that when the nsclient reports "corrupted 
counters" the ms performance tool should complain about these also?

IMHO this would be very logical, but de facto it's ms...


-- 
Ralf Mellis
Abt. DV/ORG
Kisters Maschinenbau GmbH
Germany
47533 Kleve
Boschstr. 1-3
Tel. +49(0)2821-503-0
Fax  +49(0)2821-26110




-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue. 
::: Messages without supporting info will risk being sent to /dev/null


-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null