Sudden inability to monitor SQL

[dlukinski]

Hello XI support

We are suddenly unable to monitor SQL Databases and Instances on the SQL sever 2012 SP3

DB: "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."

INSTANCE: "Connection to the database failed for an unknown reason."

This worked until it stopped 3 days ago.
I could still login to DB & instance with same credentials (local SQL, no meta chars in password)

CMD sample: -U 'nagiosxi' -P 'checkME123' -I 'FIKCM4DBD01S1' --averagewait --warning 150000 --critical 200000

Would this trouble be known to you?

[avandemore]

What is the full output from the Run Check Command?

[dlukinski]

What is the full output from the Run Check Command?

[nagios@fikc-nagxiprod01.konecranes.com ~]$ /usr/local/nagios/libexec/check_mssql_database.py -H fikc-m4dbd01 -U 'nagiosxi' -P 'checkNAG1' -T 'Siebeldb_T1' -I FIKCM4DBD01S1 --datasize --warning 1500000000 --critical 1700000000
<class &apos;pymssql.InterfaceError&apos;>
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.

That server is accessible (NSclient checks are operational)

[rkennedy]

Are any mssql checks working at all, or did they all stop working between a few different machines?

A couple things to verify -
1. database is accepting mixed auth.
2. any luck if you try the IP? Wondering if it's trying to go over IPv6 and failing.

[dlukinski]

Are any mssql checks working at all, or did they all stop working between a few different machines?

A couple things to verify -
1. database is accepting mixed auth.
2. any luck if you try the IP? Wondering if it's trying to go over IPv6 and failing.

Yes, authentication is mixed

Same results via IPv4
[nagios@fikc-nagxiprod01.konecranes.com ~]$ /usr/local/nagios/libexec/check_mssql_database.py -H 10.102.74.84 -U 'nagiosxi' -P 'checkNAG1' -T 'Siebeldb_T1' -I FIKCM4DBD01S1 --logshrinks --warning 30 --critical 50
<class &apos;pymssql.InterfaceError&apos;>
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.

[tmcdonald]

And as for @rkennedy's question regarding other checks, is it just this one that is failing or are all SQL checks against that machine failing? Are other machines' SQL checks failing as well? We're trying to see if this problem is local to just one machine in which case something might have changed there, or if it is on the Nagios side of things which could point to a broken upgrade of libraries or something else the plugin relies on.

[dlukinski]

And as for @rkennedy's question regarding other checks, is it just this one that is failing or are all SQL checks against that machine failing? Are other machines' SQL checks failing as well? We're trying to see if this problem is local to just one machine in which case something might have changed there, or if it is on the Nagios side of things which could point to a broken upgrade of libraries or something else the plugin relies on.

Yes all the checks are failing (same across multiple machines):

DB-Lib error message 20009, severity 9:
Unable to connect: Adaptive Server is unavailable or does not exist
Net-Lib error during Operation now in progress Error 115 - Operation now in progress

I think I have make a ticket out of this one

Thanks,
Dimitri

[cdienger]

Hi Dimitri, Have you opened a ticket? If so, we'd like to close this thread while you continue to work with us through the ticket.

[dlukinski]

Hi Dimitri, Have you opened a ticket? If so, we'd like to close this thread while you continue to work with us through the ticket.

OK, lets close this thread

/Dimitri