Monitoring a Microsoft SQL Server

[Kaplan, Andrew H.]

Hi there --

Thanks for your reply. I tried your suggestion on the two plugins, and here are
the results.

When the command syntax for check_mssql was the following:

./check_mssql -H <ip address> -U <domain>\\<username> -P <password>

or

./check_mssql -H <ip address> -U '<domain>\\<username>' -P <password>

The error message displayed on-screen was:

UNKNOWN: Invalid characters in the username.

Using a similar command syntax with check_mssql_health:

./check_mssql_health --hostname=<ip address> --username=<domain>\\<username>
--password=<password> --mode=connection-time

Resulted in the following:

CRITICAL - cannot connect to 172.27.45.6. DBI connect(';host=<ip
address>;port=1433','<domain>\<username>',...) failed: (no error string) at
./check_mssql_health line 2175

One thought came to mind: It is possible the port that is the target of either
script, 1433, may not be the correct one. Is there a way to determine what port
the SQL server has open?



-----Original Message-----
From: Spook ZA [mailto:spookza at gmail.com] 
Sent: Thursday, November 17, 2011 2:43 AM
To: Nagios Users List
Subject: Re: [Nagios-users] Monitoring a Microsoft SQL Server

Hi.

On 16 November 2011 19:40, Kaplan, Andrew H. <AHKAPLAN at partners.org> wrote:
> I am trying to monitor several Microsoft SQL Server 2008R2 systems, and I am
experimenting with several plugins.
>
> The first plugin that I am testing is the check_mssql plugin. I am having
problems gaining access to the server,
> and I am not sure where the syntax error is in the command. The command syntax
that is being used is the following:
>
> ./check_mssql -H <ip address> -U <username> -P <password>
>
> The username being entered is a domain user account. The name is used either
by itself or as <domain>\<username>.
> All attempts have resulted in the following error:
>
> CRITICAL: Could not connect to <ip address> as <username>.
>
> Another plugin that I am testing is the check_mssql_health plugin. Using the
command syntax shown below:
>
> ./check_mssql_health --hostname=<ip address> --username=<username>
--password=<password> --mode=connection-time

You may have to escape the backslash - i.e. domain\\username
I have not used these plugins as yet but have had similar issues in
other areas when trying to connect to a windows platform.

>
> The username here is the same as that used in the previous plugin. The
connection attempts all failed with the
> following error message appearing on-screen:
>
> CRITICAL - cannot connect to 172.27.45.252. DBI
connect(';host=172.27.45.252;port=1433','ahk',...)
> failed: (no error string) at ./check_mssql_health line 2175
>
> Has anyone had success working with either of these plugins, and if so, what
would be the correct syntax to use here?
>
Regards,
  Andy.

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any
issue. 
::: Messages without supporting info will risk being sent to /dev/null


The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.


------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null