Nagios Support Forum

Hello:
We run CommVault on a few servers and it runs a number of Windows services, below (actual service name first and then followed by the human readable name surrounded by quotes):
GxApM(Instance001) "CommVault Application Manager (Instance001)"
GxEvMgrC(Instance001) "CommVault Client Event Manager (Instance001)"
GxEvMgrC(Instance002) "CommVault Client Event Manager (Instance002)"
GxQSDK(Instance001) "CommVault Commands Manager (Instance001)"
GxCVD(Instance001) "CommVault Communications Service (Instance001)"
GxCVD(Instance002) "CommVault Communications Service (Instance002)"
GxJobMgr(Instance001) "CommVault Job Manager (Instance001)"
GxMLM(Instance001) "CommVault Media & Library Manager (Instance001)"
GxMMM(Instance001) "CommVault Media Mount Manager (Instance001)"
GxEvMgrS(Instance001) "CommVault Server Event Manager (Instance001)"
MSSQL$COMMVAULT "SQL Server (COMMVAULT)"
SQLAgent$COMMVAULT "SQL Server Agent (COMMVAULT)"
SQLBrowser "SQL Server Browser"

PROBLEM: Nagios XI 2014R1.5 flags these with an error because of having a "(" in the name, and possibly the "$" character.

I will try to see if the service still can be monitored if I just enter the first part of the service name, ex. GxCVD. "MSSQL$COMMVAULT" will be an issue, though since you can't truncate that.

Second problem: If there are two instances of the service, ex. GxCVD(Instance001) and GxCVD(Instance002), then how will I be able to monitor both incidences then?

This is not good.

Can you post an example of the check you are running and the problematic output thereof?

abrist wrote:Can you post an example of the check you are running and the problematic output thereof?

I installed the latest NSCLient++ client on one of the Windows servers that's running CommVault, then I configured the Windows server monitoring using the Windows Server Wizard and identified the Services:
1). GxEvMgrC(Instance001) "CommVault Client Event Manager (Instance001)"
2). GxCVD(Instance001) "CommVault Communications Service (Instance001)"


Nagios XI identifies the services as, below, in the Service Status, and has error messages:
1). "CommVault Client Event Manager _Instance001_" - (No output on stdout) stderr: /bin/sh: -c: line 0: syntax error near unexpected token `('
2). "CommVault Communications Service _Instance001_" - (No output on stdout) stderr: /bin/sh: -c: line 0: syntax error near unexpected token `('


The service checks that they use are:
1). check_xi_service_nsclient!EDITED!SERVICESTATE!-l GxEvMgrC(Instance001) -d SHOWALL
2). check_xi_service_nsclient!EDITED!SERVICESTATE!-l GxCVD(Instance001) -d SHOWALL

Does the check from from the CLI? Can you show us the output?

lmiltchev wrote:Does the check from from the CLI? Can you show us the output?

Code: Select all

/usr/local/nagios/libexec/check_nt -H <client ip> -s "<password>" -p 12489 -v SERVICESTATE -l "GxEvMgrC(Instance001)" -d SHOWALL
/usr/local/nagios/libexec/check_nt -H <client ip> -s "<password>" -p 12489 -v SERVICESTATE -l "GxCVD(Instance001)" -d SHOWALL

So that I understand you correctly, you wanted me to run the 2 commands at the command line on my Nagios XI monitoring server (filling in the appropriate information, obviously)?

So, when I ran the commands, the responses were (which is fine):
GxEvMgrC(Instance001): Stopped
GxCVD(Instance001): Stopped

I believe there is an upgrade going on today, so that is why the services are stopped - I verified that these services were running yesterday when I installed the NSClient++ client.

I identified a different service on that server (GxMLM(Instance001) "CommVault Media & Library Manager (Instance001)", modified your command to run with that service, and the result was:
GxMLM(Instance001): Started

So, the CLI appears to be fine, but the Windows Server Wizard and/or Nagios XI is having an issue. I found a "feature" perhaps?

This may be just an "escaping" issue.

Let's to go Home->Service Detail->find one of the services that we tested from the CLI, for example "GxEvMgrC(Instance001)" and click on it.

1. Schedule a forced immediate check, wait for the output, and show us a screenshot of this page.
2. Go to Configure->Re-configure this service and show us the command that is listed in the "Monitor the service with this command" field.

lmiltchev wrote:This may be just an "escaping" issue.

Let's to go Home->Service Detail->find one of the services that we tested from the CLI, for example "GxEvMgrC(Instance001)" and click on it.

1. Schedule a forced immediate check, wait for the output, and show us a screenshot of this page.
2. Go to Configure->Re-configure this service and show us the command that is listed in the "Monitor the service with this command" field.

I will have to do this tomorrow (Fri.) since I just checked this and need to leave for the day. Sorry.

Keep us posted, thanks.

PhilG wrote:

lmiltchev wrote:This may be just an "escaping" issue.

Let's to go Home->Service Detail->find one of the services that we tested from the CLI, for example "GxEvMgrC(Instance001)" and click on it.

1. Schedule a forced immediate check, wait for the output, and show us a screenshot of this page.
2. Go to Configure->Re-configure this service and show us the command that is listed in the "Monitor the service with this command" field.

I will have to do this tomorrow (Fri.) since I just checked this and need to leave for the day. Sorry.

=================================================================================================
UPDATE:
A). I setup a different Windows server with the following Windows Services and then setup monitoring using Windows Server Wizard (Service Name then Display Name):
GxEvMgrC(Instance001), CommVault Client Event Manager (Instance001)
GxCVD(Instance001), CommVault Communications Service (Instance001)
MSSQLFDLauncher$UWCX01, SQL Full-text Filter Daemon Launcher (UWCX01)
MSSQL$UWCX01, SQL Server (UWCX01)

B). Command Line information for each:
GxEvMgrC(Instance001): Started
GxCVD(Instance001): Started
MSSQLFDLauncher: Not found
MSSQL: Not found

C). Message in Service Status:
CommVault Client Event Manager _Instance001_, Warning, (No output on stdout) stderr: /bin/sh: -c: line 0: syntax error near unexpected token `('
CommVault Communications Service _Instance001_, Warning, (No output on stdout) stderr: /bin/sh: -c: line 0: syntax error near unexpected token `('
SQL Full-text Filter Daemon Launcher _UWCX01_, Critical, MSSQLFDLauncher: Not found
SQL Server _UWCX01_, Critical, MSSQL: Not found

D). Their checks used as per Configure Service:
check_xi_service_nsclient!<pass>!SERVICESTATE!-l GxEvMgrC(Instance001) -d SHOWALL
check_xi_service_nsclient!<pass>!SERVICESTATE!-l GxCVD(Instance001) -d SHOWALL
check_xi_service_nsclient!<pass>!SERVICESTATE!-l MSSQLFDLauncher$UWCX01 -d SHOWALL
check_xi_service_nsclient!<pass>!SERVICESTATE!-l MSSQL$UWCX01 -d SHOWALL


E). As per your instructions, above, but edited. The capture is for the GxEvMgrC service, and the second reference, sans capture, is just what was displayed for doing the 3rd Windows Service, provided above: MSSQLFDLauncher: Not found


We may have to not monitor the MSSQL since they may be reference a DSN and that is how that service needs to work (the "$" is how it needs MSSQL's service to recognize which instance it has to work with, perhaps).

However, the Commvault Windows Service should be looked into.

Thank you.

PhilG wrote:check_xi_service_nsclient!<pass>!SERVICESTATE!-l GxEvMgrC(Instance001) -d SHOWALL
check_xi_service_nsclient!<pass>!SERVICESTATE!-l GxCVD(Instance001) -d SHOWALL
check_xi_service_nsclient!<pass>!SERVICESTATE!-l MSSQLFDLauncher$UWCX01 -d SHOWALL
check_xi_service_nsclient!<pass>!SERVICESTATE!-l MSSQL$UWCX01 -d SHOWALL

The brackets and $ signs need to be escaped with a backslash '\'.