I am trying to monitor the one service of the Windows Server.
I have provided the following name in the Service Definition:
MSSQL$MICROSOFT##WID
Refer to the Attachment
But when i see on the Nagios Console:
I gets the Error as "Not found" also the Service name shown is different what i provided in the service definition.
MSSQL##WID$
Refer to the Screenshot in the attachment.
Monitoring of Windows Services
-
- Posts: 286
- Joined: Fri Sep 08, 2017 5:53 am
Monitoring of Windows Services
- Attachments
-
- Service Monitoring.docx
- (53.17 KiB) Downloaded 140 times
-
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Monitoring of Windows Services
This same problem was worked through on this thread
https://support.nagios.com/forum/viewto ... =7&t=39317
https://support.nagios.com/forum/viewto ... =7&t=39317
-
- Posts: 286
- Joined: Fri Sep 08, 2017 5:53 am
Re: Monitoring of Windows Services
Thanks for pointing me to the Thread.
I was able to resolve the issue by defining the service name in the resource.cfg file .
Then i mentioned that variable in the service definition.
But one question when i try to run any command manually from the command line then it is giving me the error as follows:
Critical: Socket Timeout After 10 seconds
I am getting the above error for all the service definitions even they are reporting to Nagios Fine.
What could be the reason?
I was able to resolve the issue by defining the service name in the resource.cfg file .
Then i mentioned that variable in the service definition.
But one question when i try to run any command manually from the command line then it is giving me the error as follows:
Critical: Socket Timeout After 10 seconds
I am getting the above error for all the service definitions even they are reporting to Nagios Fine.
What could be the reason?
-
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Monitoring of Windows Services
Can you give an example of your command you are running from the command line??amitgupta19 wrote:Thanks for pointing me to the Thread.
I was able to resolve the issue by defining the service name in the resource.cfg file .
Then i mentioned that variable in the service definition.
But one question when i try to run any command manually from the command line then it is giving me the error as follows:
Critical: Socket Timeout After 10 seconds
I am getting the above error for all the service definitions even they are reporting to Nagios Fine.
What could be the reason?
Just remember you cannot pass anything like $ARG1$ when testing from the command line, these need to be replaced with their actual values.
-
- Posts: 286
- Joined: Fri Sep 08, 2017 5:53 am
-
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Monitoring of Windows Services
The top one looks right but you likely needs -p 12489 added to the command to set the normal port that nsclient++ uses