SQL Service errors after upgrading to 2014

[msfhr]

I am getting SQL Server check errors after upgrade to 2014. Error is pretty much the same for any SQL Server instance I have. Here's the one example.

***** Nagios XI Alert *****

Nagios has detected a problem with this service.

Notification Type: PROBLEM

Service: SQL Server \__VIM_SQLEXP\__
Host: vcenter.comp.com
Address: 192.168.1.23
State: WARNING
Info:
MSSQL\: Error
Date/Time: 05/13/2014 11:18:40

[lmiltchev]

Can you show the actual command that is run from the command line, along with the output of it? (hide sensitive info)

[msfhr]

Can you show the actual command that is run from the command line, along with the output of it? (hide sensitive info)

Don't know about command line as we are managing XI through web interface. This is the one that shows in "Monitor the service with this command... (Advanced users only)"
check_xi_service_nsclient!!SERVICESTATE!-l MSSQL\\$$MICROSOFT##SSEE -d SHOWALL

[abrist]

Can you run the same check with the verbose flag from the cli?

Code: Select all

check_nt -H <hostip> -s "<password>" -p 12489 -v SERVICESTATE -l MSSQL\\$$MICROSOFT##SSEE -d SHOWALL

And then again as verbose:

Code: Select all

check_nt -H <hostip> -vvv -s "<password>" -p 12489 -v SERVICESTATE -l MSSQL\\$$MICROSOFT##SSEE -d SHOWALL

[snapon_admin]

I was getting the same thing today with a similar service, MSSQL$SCANMAIL. I think it might have something to do with the $ in the service name and the way it's commented out. In XI 2012, in order to include the $ in the service name being checked I had to add '\\$' to the command, like MSSQL\\$$SCANMAIL. After the upgrade, mine was doing the same thing as yours. Notice the service output from the email is MSSQL\: Error. The out put stops when it hits '\$'. I tried a couple of different options and the only one that made the output change back to OK was this:

Code: Select all

check_xi_service_nsclient!!SERVICESTATE!-l MSSQL\$SCANMAIL -d SHOWALL!!!!!

I just used one \ before the $ and the service check went green again. The check still seems a bit different, though, and might not be accurate. This is what the output used to be:

MSSQL$SCANMAIL: Started

and this is what it is now:

OK: All services are in their appropriate state.

Sorry to hijack your thread, but I had a very similar issue and thought some additional info might help out.

[msfhr]

Can you run the same check with the verbose flag from the cli?

Code: Select all

check_nt -H <hostip> -s "<password>" -p 12489 -v SERVICESTATE -l MSSQL\\$$MICROSOFT##SSEE -d SHOWALL

And then again as verbose:

Code: Select all

check_nt -H <hostip> -vvv -s "<password>" -p 12489 -v SERVICESTATE -l MSSQL\\$$MICROSOFT##SSEE -d SHOWALL

Here it comes, I don't have password set for this server.

./check_nt -H 192.168.1.28 -p 12489 -v SERVICESTATE -l MSSQL\\$$MICROSOFT##SSEE -d SHOWALL
MSSQL\29698MICROSOFT##SSEE: Error

./check_nt -H 192.168.1.28 -vvv -p 12489 -v SERVICESTATE -l MSSQL\\$$MICROSOFT##SSEE -d SHOWALL
check_nt: Could not parse arguments
Usage:
check_nt -H host -v variable [-p port] [-w warning] [-c critical]

and here is Print Spooler example
./check_nt -H 192.168.1.28 -p 12489 -v SERVICESTATE -l Spooler -d SHOWALL
Spooler: Started

[msfhr]

I was getting the same thing today with a similar service, MSSQL$SCANMAIL. I think it might have something to do with the $ in the service name and the way it's commented out. In XI 2012, in order to include the $ in the service name being checked I had to add '\\$' to the command, like MSSQL\\$$SCANMAIL. After the upgrade, mine was doing the same thing as yours. Notice the service output from the email is MSSQL\: Error. The out put stops when it hits '\$'. I tried a couple of different options and the only one that made the output change back to OK was this:

Code: Select all

check_xi_service_nsclient!!SERVICESTATE!-l MSSQL\$SCANMAIL -d SHOWALL!!!!!

I just used one \ before the $ and the service check went green again. The check still seems a bit different, though, and might not be accurate. This is what the output used to be:

MSSQL$SCANMAIL: Started

and this is what it is now:

OK: All services are in their appropriate state.

Sorry to hijack your thread, but I had a very similar issue and thought some additional info might help out.

Thanks snapon, that did it for me as well. I always thought that \\$ escape character was rather weird one, this one make more sense. Can Nagios people confirm that this is right escape character for version 2014?

[abrist]

Nick had done quite a bit of work to the MSSQL plugins, so that is a possibility. I will ask him later this week. Apologies though, these type of changes *should* have all been documented.