MS SQL Log Cache Hit Rate error

[rdobbsmacu]

I ran the Xi MSSQL Database wizzard and all but one of the created services is work correctly.

Here is the services check command line
check_xi_mssql_database!-U 'nagios' -P '$USER9$' -T 'ICS_NET' -I MSSQLSERVER --logcachehit --warning 0:95 --critical 0:97

here is the message I'm seeing from nagios
Caught unexpected error. This could be caused by your sysperfinfo not containing the proper entries for this query, and you may delete this service check.


I have also tried the password in replacement of the macro and get the same thing.

[Box293]

Are you getting any event log errors on the MSSQL server related to this query?

[rdobbsmacu]

I have been through the logs on the SQL server and couldn't find warnings or errors with the account being used by nagios, or any with with noagios connections.

[tgriep]

Can you login as root on the XI server and run the following command and post the output here?
Be sure to replace xxx.xxx.xxx.xxx with the IP address ans also the correct user name and password.

Code: Select all

/usr/local/nagios/libexec/check_mssql_database.py -H xxx.xxx.xxx.xxx -U 'nagios' -P '$USER9$' -T 'ICS_NET' -I MSSQLSERVER --logcachehit --warning 0:95 --critical 0:97

[rdobbsmacu]

OK i ran that command here is the output

SQL Server message 18456, severity 14, state 1, line 1:
Login failed for user 'nagios'.
DB-Lib error message 18456, severity 14:
General SQL Server error: Check messages from the SQL Server
DB-Lib error message 20002, severity 9:
Adaptive Server connection failed

I was able to find the SQL server event this time. here is the events on the SQL server for connections from my nagios server. the one in red is from running that command. the others are from my other MS SQL monitors running on Nagios. So why is just this one getting this error?

Date,Source,Severity,Message
12/16/2015 15:11:53,Logon,Unknown,Login succeeded for user 'nagios'. Connection made using SQL Server authentication. [CLIENT: 172.18.201.4]
12/16/2015 15:10:51,Logon,Unknown,Login succeeded for user 'nagios'. Connection made using SQL Server authentication. [CLIENT: 172.18.201.4]
12/16/2015 15:10:16,Logon,Unknown,Login succeeded for user 'nagios'. Connection made using SQL Server authentication. [CLIENT: 172.18.201.4]
12/16/2015 15:09:48,Logon,Unknown,Login succeeded for user 'nagios'. Connection made using SQL Server authentication. [CLIENT: 172.18.201.4]
12/16/2015 15:09:47,Logon,Unknown,Login succeeded for user 'nagios'. Connection made using SQL Server authentication. [CLIENT: 172.18.201.4]
12/16/2015 15:09:32,Logon,Unknown,Login failed for user 'nagios'. Reason: Password did not match that for the login provided. [CLIENT: 172.18.201.4]
12/16/2015 15:09:25,Logon,Unknown,Login succeeded for user 'nagios'. Connection made using SQL Server authentication. [CLIENT: 172.18.201.4]
12/16/2015 15:09:23,Logon,Unknown,Login succeeded for user 'nagios'. Connection made using SQL Server authentication. [CLIENT: 172.18.201.4]
12/16/2015 15:08:56,Logon,Unknown,Login succeeded for user 'nagios'. Connection made using SQL Server authentication. [CLIENT: 172.18.201.4]
12/16/2015 15:08:14,Logon,Unknown,Login succeeded for user 'nagios'. Connection made using SQL Server authentication. [CLIENT: 172.18.201.4]

[tgriep]

Does the password have any special characters in it?
When you ran the command, did you put the password in single quotes?

[rdobbsmacu]

Yes I did. here is the command line output with the password in signal quotes

<type 'exceptions.ZeroDivisionError'>
Caught unexpected error. This could be caused by your sysperfinfo not containing the proper entries for this query, and you may delete this service check.

[tgriep]

Can you post back the version of the MSSQL database wizard?
Go in to Admin > Manage Config Wizards to get that info.
The other checks that are passing, can you post how they are ran?

[rdobbsmacu]

all three of the MSSQL wizards are 1.5.6

[lmiltchev]

Does the following command produce the expected output?

Code: Select all

/usr/local/nagios/libexec/check_mssql_database.py -H xxx.xxx.xxx.xxx -U 'nagios' -P '<password>' -T 'ICS_NET' -I MSSQLSERVER --logcachehit --warning 0:95 --critical

Note: Don't use the '$USER9$' in your command - use the actual password.

Go to CCM->Services->View Text Output, and show the config of the "failing" server and another config of a "working" service. Hide sensitive info.