MSSQL - Adaptive Server connection failed

[eliassal]

Sorry, but this is a VM provided by Nagios, I havn't installed anything, if I remember well, 6 or 7 months back I downloaded the VM and just running it, nothing is done on my side.
For the sake of discussion I know a little bit linux but not un expert nor PIP

[lmiltchev]

If you are using one of our VMs, then pip should've been installed, but for some reason was not. This is strange as in the newer XI versions (5.x), the mssql prerequisites should be already installed.

You can easily install it by running:

Code: Select all

yum install python-pip -y

Just DO NOT try upgrading it by running:

Code: Select all

pip install --upgrade pip

as I mentioned before as this would break it.

Since all of your checks are working with the exception of the "stolenpages" one, we can probably close this topic. Let us know if you have any further questions. Thank you!

[eliassal]

I did and PIP is installed as you can notice

Downloading Packages:
python-pip-7.1.0-1.el6.noarch.rpm | 1.5 MB 00:00
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Installing : python-pip-7.1.0-1.el6.noarch 1/1
Verifying : python-pip-7.1.0-1.el6.noarch 1/1

Installed:
python-pip.noarch 0:7.1.0-1.el6

Complete!

I went bak to Nagios UI, did a test, I got the following

COMMAND: /usr/local/nagios/libexec/check_mssql_server.py -H 192.168.1.69 -U 'sa' -P 'mypass' -I 'SC2K12' --stolenpages --warning 500 --critical 700
OUTPUT:

[eliassal]

By the way, in the UI, I have a link "Check for Updates", I clicked on it, I was taken to a page where it is indicated

Product Update Check

An Update Is Available!
Your installation of Nagios XI 2014R2.6 is outdated and should be upgraded. The latest version of Nagios XI is 5.5.7, which was released on 2018-11-13.

You mentioned that I should avoid upgrading or should I do the update? If yes, how this VM can be upgraded?

Thanks for your help

[eliassal]

One of the services which was working fine, since 1 hour started to behave in the same way as stolen pages, the service is the "MSSQL Free Pages".

In the UI I am getting

COMMAND: /usr/local/nagios/libexec/check_mssql_server.py -H 192.168.1.69 -U 'sa' -P 'pepv1met' -I 'SC2K12' --freepages --warning 100 --critical 200
OUTPUT:

by email, I started receiving this

Notification Type: PROBLEM

Service: MSSQL Free Pages
Host: sql2k12.salam.net
Address: sql2k12.salam.net
State: WARNING
Info:
(No output on stdout) stderr: Traceback (most recent call last):
Date/Time: 2018-11-30 21:02:15

[lmiltchev]

Both checks - the "stolenpages" and "freepages" may have issues as described in the page I linked:
https://github.com/NagiosEnterprises/ch ... /issues/10
Quote:

I can also report some issues when testing against SQL 2016 with --stolenpages and --freepages:

If these performance counters have been removed/renamed, the check won't work. I am going to talk to our developers and see if they can modify the plugin to work better with newer MSSQL servers. I can submit a feature request on your behalf if you'd like. Please keep in mind that the decision to implement the enhancement is at the sole discretion of our development team.

You mentioned that I should avoid upgrading or should I do the update? If yes, how this VM can be upgraded?

I told you not to upgrade PIP on your system as you are running CentOS 6, and upgrading PIP will break it. I didn't say anything about upgrading Nagios XI. You are running a very old instance of Nagios XI, and I would recommend upgrading it to the latest. Nagios XI 5.5.8 should be out sometime soon. I would recommend that you upgrade to this one, when is out. Here's our official documentation on the upgrade procedure:

https://assets.nagios.com/downloads/nag ... ctions.pdf

[eliassal]

Thanks yes please, do the feature request, appreciate it

[eliassal]

I gave it a go the uypgrade, ran the following 2 commands

wget -O upgrade.sh https://assets.nagios.com/downloads/nagiosxi/upgrade.sh
sh ./upgrade.sh
as indicated in the doc, everythinh worked like a charm.

I reran the freepages service for sql, I get

[[email protected] ~]$ /usr/local/nagios/libexec/check_mssql_server.py -H sql2k12.salam.net -U 'sa' -P 'mypassword' -I 'SC2K12' --freepages --warning 100 --critical 200
<type 'exceptions.TypeError'>
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.

[eliassal]

Some good news, after upgrading I readded my sql server monitoring with windows authentication, and everything works like a charm.
However, in the monitoring config wizard, I gave it of course the same exact FQDN of the server without the instance name, it updated the existing one which had the same FQDN with an instance, is this normal? How in this case we can add several instances running on the same sql server along with the default one?

[lmiltchev]

I am glad that you were able to upgrade your Nagios XI instance successfully!

As far as failing MSSQL checks (freepages & stolenpages) goes, I filed an internal bug report on the issue (task_id=13872). Our developers will be working on it as soon as they can. I expect the issue to be resolved in one of the future versions of the MSSQL wizards.