NSClient++ Help (#1) - CheckServiceState [SOLVED] (#252) - Message List

I have hard time checking for all Automatic Services Status with

newer version (0.3.4). I have to list all Manual not started services in exclude list and this list for some of the servers is quiet huge. Can you include a flag to check for Automatic Services only? If it is already there can you show me how to use it? I looked in to the documentation but couldn't find it. Thanks for doing a wonderful Job!!!

  • Message #764

    there is a bug in the 0.3.4 version, try the "nightly" it shall hopefully solve the checkall issues...

    • Message #766

      I had the same issue and tried the nightly NSClient++-Win32-20080923-2231.zip. The issue is fixed there. Thanks!!

      • Message #1766

        Hi, this problem is back in 3.8.70. A Windows 2008 x64 server is reporting all 'manual' services as an error:

        2010-05-21 12:48:15: debug:NSClient++.cpp:1106: Injecting: CheckServiceState: CheckAll, exclude=TBS
        2010-05-21 12:48:15: debug:NSClient++.cpp:1142: Injected Result: CRITICAL 'CRITICAL: NSClientpp: stopped (critical)'
        2010-05-21 12:48:15: debug:NSClient++.cpp:1143: Injected Performance Result: 'ALG: ERRORAppinfo: ERRORAppMgmt: ERRORaspnet_state: ERRORAudioEndpointBuilder: ERRORAudioSrv: ERRORCertPropSvc: ERRORclr_optimization_v2.0.50727_32: ERRORclr_optimization_v2.0.50727_64: ERRORCOMSysApp: ERRORdot3svc: ERROREapHost: ERRORFCRegSvc: ERRORfdPHost: ERRORFDResPub: ERRORFontCache3.0.0.0: ERRORhkmsvc: ERRORidsvc: ERRORKeyIso: ERRORlltdsvc: ERRORMMCSS: ERRORMSExchangeImap4: ERRORMSExchangeMonitoring: ERRORmsftesql-Exchange: ERRORMSFTPSVC: ERRORMSiSCSI: ERRORmsiserver: ERRORnapagent: ERRORNetman: ERRORose: ERRORPerfHost: ERRORpla: ERRORProtectedStorage: ERRORRasAuto: ERRORRasMan: ERRORRPCHTTPLBS: ERRORRpcLocator: ERRORRqs: ERRORRSoPProv: ERRORsacsvr: ERRORSCardSvr: ERRORSCPolicySvc: ERRORSessionEnv: ERRORSLUINotify: ERRORSNMPTRAP: ERRORSPAdmin: ERRORSPSearch: ERRORSrmReports: ERRORSstpSvc: ERRORswprv: ERRORTapiSrv: ERRORTHREADORDER: ERRORTrkWks: ERRORTrustedInstaller: ERRORUI0Detect: ERRORUmRdpService: ERRORvds: ERRORVSS: ERRORWAS: ERRORwbengine: ERRORWcsPlugInService: ERRORWdiServiceHost: ERRORWdiSystemHost: ERRORWecsvc: ERRORwercplsupport: ERRORWinHttpAutoProxySvc: ERRORwmiApSrv: ERRORWMSvc: ERRORwsbexchange: ERRORWSusCertServer: ERRORwudfsvc: ERROR'
        2010-05-21 12:48:15: error:modules\NRPEListener\NRPEListener.cpp:325: NRPESocketException: To much data cant create return packet (truncate datat)
        

        A reboot after the NSClient upgrade isn't possible now, i can try later on when users are logged off.

        • Message #1771

          This is a bit of a problem... NRPE does not allow more then 1024 (ish) chars return data so if you have many servers you will get this problem unfortunately. Options are using truncate or not having so many "errors" :)

          Michael Medin

          • Message #1774

            But it shouldn't be listing that much at all! It worked well before, i only updated NSClient to 3.8.70 and now i have this problem. All the errors reported in "Injected Performance Result" are services that are set to manual start.

            Before 3.8.70 the CheckServiceState command ignored all the manual startup services and only listed the services that were set to automatic startup and didn't run at that moment.

            Did you change this behaviour by design or is this something else?

            • Message #1787

              Hi Michael,

              Back again with still the same problem. I compared the result of the 'CheckServiceState CheckAll?' with a x64 v0.3.7.494. With the same command from Nagios i get the following in test mode:

              2010-05-27 16:18:55: debug:NSClient++.cpp:1073: Injecting: CheckServiceState: CheckAll, exclude=TBS
              2010-05-27 16:18:55: debug:NSClient++.cpp:1109: Injected Result: CRITICAL 'CRITICAL: NSClientpp: stopped (critical)'
              2010-05-27 16:18:55: debug:NSClient++.cpp:1110: Injected Performance Result: ''
              

              The big difference with v0.3.8.70 is that NO performance results are injected. Can i disable injecting performance results with this command?

              Hope you can help me with this one...

              • Message #1788

                Hum...

                Seems to be an issue with the performance data caluculations. Need to figure out what is causing it since this is not "performance data" it is an error message disdplayed in the performance data.

                In the mean time you can do the following:

                CheckServiceState CheckAll ignore-perf-data
                
                • Message #1789

                  Yes! That worked :)

                  • Message #1790

                    I will try to roll a "take 3" of 0.3.8 tomorrow (building now) which has "fixed" (actually more like broken back) to the old way and thus the error will go away...

                    Michael Medin

                    • Message #1791

                      Fixed in latest version of 0.3.8...

Subscriptions