Sure, let us know. If the worst case scenario, you could still use the SQL user credentials, but Windows authentication should work on CentOS 7. FYI, during our tests, Windows auth worked also on CentOS 6 but ONLY when the system was not on a domain. Again, we will need to do some more testing on CentOS/RHEL 6.OK, but I remember that in both places service was not working. I will reconfigure and try win authentication and let you know.
My understanding was that you are receiving notifications on OK states. These two notifications are with State = WARNING... The plugin may have some "hard-coded" thresholds. If you are not using any thresholds in your check, you may be running into some "non-ok" states. I would recommend that you use thresholds that make sense in your environment.Also, when Nagios monitors SQL, several services does not have an input and still it sends alerts, and even when service is OK it sends alerts. Is it possible to configure Nagios not to send alerts when status is OK?
Here's an example of OK, WARNING, and CRITICAL output with different thresholds used:
Code: Select all
/usr/local/nagios/libexec/check_mssql_server.py -H x.x.x.x -U 'username' -P 'password' -I 'instance' --freepages --warning 500 --critical 1000
OK: Free pages is 247.0|free_pages=247.0;500;1000;;
/usr/local/nagios/libexec/check_mssql_server.py -H x.x.x.x -U 'username' -P 'password' -I 'instance' --freepages --warning 50 --critical 1000
WARNING: Free pages is 247.0|free_pages=247.0;50;1000;;
/usr/local/nagios/libexec/check_mssql_server.py -H x.x.x.x -U 'username' -P 'password' -I 'instance' --freepages --warning 50 --critical 100
CRITICAL: Free pages is 247.0|free_pages=247.0;50;100;;