Hi All,
Facing issue while configuring Check_mssql_health plugin on following.
OS-CentOS Linux release 7.2.1511 (Core)
Nagios - Nagios Core 4.2.1
check_mssql_healt - check_mssql_health $Revision: 2.6.4.7 $ [http://labs.consol.de/nagios/check_mss_health]
-----------------------------------------------------------------------------------------------
While executing following command using root and nagiosn users, on command line it is giving correct output. but on nagios configuration it is giving error.
Command-
./check_mssql_health --server DBNAME --mode connection-time --username 'USERNAME --password 'PASSWORD' --commit
Result
OK - 0.01 seconds to connect as USERNAME | 'connection_time'=0.01;1;5;;
Nagios Error
Service State Information
Current Status: CRITICAL (for 1d 11h 3m 10s)
Status Information: CRITICAL - DBD::Sybase initialisation failed: Can't locate object method "driver" via package "DBD::Sybase" at /usr/lib64/perl5/vendor_perl/DBI.pm line 820.
Perhaps the capitalisation of DBD 'Sybase' isn't right. at /usr/local/nagios/libexec/check_mssql_health line 6245.
Plesase help to get this fixed, I have already spent time to get this fixed.
Thanks in advance.
Regards,
Milind Chafekar.
Nagios Core Check_mssql_health
Re: Nagios Core Check_mssql_health
You'd probably have better luck contacting the people who maintain that plugin since we didn't write it.
Did you follow a particular guide for installing the Perl dependencies? If so, can you share that guide with us?
Can you also share the CLI command that produced the error? It's not immediately clear since the only command I see is producing an OK result based on the context of your post.
Did you follow a particular guide for installing the Perl dependencies? If so, can you share that guide with us?
Can you also share the CLI command that produced the error? It's not immediately clear since the only command I see is producing an OK result based on the context of your post.
Former Nagios employee
https://www.mcapra.com/
https://www.mcapra.com/
Re: Nagios Core Check_mssql_health
Thanks Matt for the reply, I have followed the suggested installation document. and configure the plugin in the command and widows cfg files.
On the command line I could see the correct expected output
but on the nagios page showing following error.
Command Defination
Service Defination
I will also try to coordinate with the plugin manager team.
On the command line I could see the correct expected output
Code: Select all
[nagios@monitor-nobo libexec]$ ./check_mssql_health --server testdb --mode connection-time --username 'nagiosadmin' --password 'password' --commit
OK - 0.01 seconds to connect as nagiosadmin | 'connection_time'=0.01;1;5;;
[nagios@monitor-nobo libexec]$
Service State Information
Current Status: CRITICAL (for 2d 7h 31m 34s)
Status Information: CRITICAL - DBD::Sybase initialisation failed: Can't locate object method "driver" via package "DBD::Sybase" at /usr/lib64/perl5/vendor_perl/DBI.pm line 820.
Perhaps the capitalisation of DBD 'Sybase' isn't right. at /usr/local/nagios/libexec/check_mssql_health.pl line 6246.
Performance Data:
Current Attempt: 3/3 (HARD state)
Last Check Time: 04-08-2017 18:11:32
Check Type: ACTIVE
Check Latency / Duration: 0.000 / 0.094 seconds
Next Scheduled Check: 04-08-2017 18:21:32
Last State Change: 04-06-2017 10:48:01
Last Notification: 04-07-2017 09:39:04 (notification 44)
Is This Service Flapping? NO (0.00% state change)
In Scheduled Downtime? NO
Last Update: 04-08-2017 18:19:26 ( 0d 0h 0m 9s ago)
Command Defination
Code: Select all
define command{
command_name check_mssql_health
command_line $USER1$/check_mssql_health.pl --server testdb --mode $ARG1$ --username ''nagiosadmin' --password 'password' --commit
}
Code: Select all
define service{
use generic-service
host_name Test_DB
service_description DB Connection Time
check_command check_mssql_health!connection-time
}
- Box293
- Too Basu
- Posts: 5126
- Joined: Sun Feb 07, 2010 10:55 pm
- Location: Deniliquin, Australia
- Contact:
Re: Nagios Core Check_mssql_health
This sounds like a global environment issue.
This KB article shows an example of how to fix it. In your case I think you need your path statement to include the location of the DBI.pm file.
https://support.nagios.com/kb/article.php?id=489
Even though the KB article is for Nagios XI it still applies to Nagios Core.
This KB article shows an example of how to fix it. In your case I think you need your path statement to include the location of the DBI.pm file.
https://support.nagios.com/kb/article.php?id=489
Even though the KB article is for Nagios XI it still applies to Nagios Core.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.