Windows 10 Explorer Serrvice

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
kwhogster
Posts: 644
Joined: Wed Oct 14, 2015 6:51 pm
Location: Wood Ridge NJ USA
Contact:

Re: Windows 10 Explorer Serrvice

Post by kwhogster »

spoke too soon

Got the error again today

What is up with Windows 10 support?
User avatar
lmiltchev
Bugs find me
Posts: 13589
Joined: Mon May 23, 2011 12:15 pm

Re: Windows 10 Explorer Serrvice

Post by lmiltchev »

What is the error that you are getting when you run the command below?

Code: Select all

./check_nt -H 10.2.8.69 -p 12489 -v PROCSTATE -l explorer.exe -s xxxxxxxxxxx
Do you get

Code: Select all

CRITICAL: explorer.exe: not running
or something else?

Can you verify that "explorer.exe" is indeed running? What is the output of the following command run from the CMD prompt on the Windows 10 machine?

Code: Select all

tasklist | find "explorer.exe"
Be sure to check out our Knowledgebase for helpful articles and solutions!
kwhogster
Posts: 644
Joined: Wed Oct 14, 2015 6:51 pm
Location: Wood Ridge NJ USA
Contact:

Re: Windows 10 Explorer Serrvice

Post by kwhogster »

Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>tasklist | find "explorer.exe"
explorer.exe 5404 Console 1 84,416 K

C:\WINDOWS\system32>


It is always running just Nagios thinks it is not receiving data from client sometimes very strange that this is the only one at of all the clients I have.

Thank you

Tom
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: Windows 10 Explorer Serrvice

Post by rkennedy »

Does it just happen intermittently or is it saying that the service isn't running completely? At this point it's starting to sound more like an NSClient++ / Windows 10 issue. Can you post your NSClient++ log file for us to look at? It might have information on why it's failing.
Former Nagios Employee
kwhogster
Posts: 644
Joined: Wed Oct 14, 2015 6:51 pm
Location: Wood Ridge NJ USA
Contact:

Re: Windows 10 Explorer Serrvice

Post by kwhogster »

Does it just happen intermittently YES

see log file
Attachments
nsclient.log
log file
(10.7 KiB) Downloaded 394 times
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: Windows 10 Explorer Serrvice

Post by rkennedy »

It sounds like a network or NSClient++ issue as the log files don't seem to indicate anything. I would adjust your max check attempts to a higher number, and this should help to reduce the false positive.
Former Nagios Employee
kwhogster
Posts: 644
Joined: Wed Oct 14, 2015 6:51 pm
Location: Wood Ridge NJ USA
Contact:

Re: Windows 10 Explorer Serrvice

Post by kwhogster »

this is my service def for the windows 10

Code: Select all

define service{
        use                     generic-service
        host_name               TGKW001
        service_description     NSClient++ Version
        servicegroups           nsclients
        check_command           check_nt!CLIENTVERSION
        }
so add this

max_check_attempts #n

Where do I found the default value ?
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: Windows 10 Explorer Serrvice

Post by rkennedy »

There really isn't a 'default', but because you have the template generic-service assigned, it's most likely inheriting it through there. Yep, you could change it to for example -

Code: Select all

define service{
        use                     generic-service
        host_name               TGKW001
        service_description     NSClient++ Version
        servicegroups           nsclients
        check_command           check_nt!CLIENTVERSION
        max_check_attempts 20
        }
Former Nagios Employee
kwhogster
Posts: 644
Joined: Wed Oct 14, 2015 6:51 pm
Location: Wood Ridge NJ USA
Contact:

Re: Windows 10 Explorer Serrvice

Post by kwhogster »

Great will make that change lets see what happens
User avatar
tgriep
Madmin
Posts: 9190
Joined: Thu Oct 30, 2014 9:02 am

Re: Windows 10 Explorer Serrvice

Post by tgriep »

Another thing to try is to increase the timeout settings for the NSClient and see if that helps.
Find this section in the nsclient.ini file and increase it to 60 seconds and also change the command in Nagios and increase it to 60 seconds as well.

Code: Select all

[/settings/NSClient/server]
# TIMEOUT
timeout=60
Be sure to check out our Knowledgebase for helpful articles and solutions!
Locked