<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content="text/html; charset=us-ascii" http-equiv=Content-Type> <META name=GENERATOR content="MSHTML 8.00.6001.19154"></HEAD> <BODY> <DIV dir=ltr align=left>Hi there --</DIV> <DIV dir=ltr align=left> </DIV> <DIV dir=ltr align=left>I finally got both the check_mssql and check_mssql_health scripts to work with the server in question. Listed below are the notes</DIV> <DIV dir=ltr align=left>that I took during the testing process. I hope they are of use, and if there are any questions, please feel free to contact me at your</DIV> <DIV dir=ltr align=left>convenience. Thanks again to everyone for the help.</DIV> <DIV dir=ltr align=left> </DIV> <DIV dir=ltr align=left> NOTE: The SQL Server in this scenario uses named instances, which result in dynamic TCP/IP ports being used rather than static ones. The ports can be identified by running the SQL Server Configuration Manager utility. Once the utility is open, go to the SQL Server Network Configuration section. Select the database in question from the list of Protocols for… entries. Double-click on the TCP/IP option listed in the right pane. Select the IP Addresses tab of the window that appears on-screen. Scroll down to the IPAll section, and make note of the value that is listed next to the TCP Dynamic Ports field. That value is what will be used in the command syntax when running the script.<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p> <o:p> </o:p> The user account, sa, along with its password will be needed to successfully access the database. The command syntax, with the resulting output is shown below. <o:p></o:p> <o:p> </o:p> check_mssql -H <ip address> --username sa --password <password> --port <dynamic TCP port> <o:p> </o:p> OK: Connect time=0.022503 seconds.<o:p></o:p> <o:p> </o:p> When using the check_mssql_health plugin, the first thing that needs to be done is to add an entry of the SQL server to the /etc/freetds/freetds.conf file. This file is used by the plugin to connect to the server. An excerpt of the file is shown below:<o:p></o:p> <o:p> </o:p> # <SQL Server Name> [name of sql server] <- name of the server used in the command syntax<o:p></o:p> host = <ip address> or <fqdn> port = <dynamic tcp port> <- TCP Dynamic port used by the server instance <o:p></o:p> tds version = 7.0<o:p></o:p> <o:p> </o:p> An example of the command syntax that is used to connect to the server is the following:<o:p></o:p> <o:p> </o:p> /usr/local/nagios/libexec/check_mssql_health --server=<name of sql server> --username=sa <o:p></o:p> --password=<password> --port=<dynamic tcp port> --mode=connection-time<o:p></o:p> <o:p> </o:p> The output of the above command is shown below:<o:p></o:p> <o:p> </o:p> OK - 0.06 seconds to connect as sa | connection_time=0.06;1;5<o:p></o:p></DIV> <DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left> <HR tabIndex=-1> From: Claudio Kuenzler [mailto:ck@claudiokuenzler.com] Sent: Thursday, November 17, 2011 3:33 PM To: Kaplan, Andrew H. Cc: Nagios Users List Subject: Re: [Nagios-users] Monitoring a Microsoft SQL Server </DIV> <DIV></DIV>The other ports don't appear like typical MSSQL ports. Do you have by any chance the Windows firewall still active? Maybe the port is being blocked there? <A href="http://support.microsoft.com/kb/968872">http://support.microsoft.com/kb/968872</A> Or do you use a named instance? I found this information on <A href="http://benchmarkitconsulting.com/colin-stasiuk/2009/02/02/what-tcp-port-is-sql-server-running-under/">http://benchmarkitconsulting.com/colin-stasiuk/2009/02/02/what-tcp-port-is-sql-server-running-under/</A>: "If you have a named instance the TCP port is dynamically configured." I've never seen this in a practical way before though. <DIV class=gmail_quote>On Thu, Nov 17, 2011 at 8:59 PM, Kaplan, Andrew H. <<A href="mailto:AHKAPLAN@partners.org">AHKAPLAN@partners.org</A>> wrote: <BLOCKQUOTE style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class=gmail_quote> <DIV> <DIV dir=ltr align=left>Hi there --</DIV> <DIV dir=ltr align=left> </DIV> <DIV dir=ltr align=left>I tried connecting to port 1433 of the SQL server, and the connection was refused. It appears that efforts to connect via the default</DIV> <DIV dir=ltr align=left>port will not work in this case. I took the liberty of running the nestat -abn command syntax on the console of the SQL server, and</DIV> <DIV dir=ltr align=left>searched for all references to the sqlservr.exe binary. The results are shown below:</DIV> <DIV dir=ltr align=left> </DIV> <DIV dir=ltr align=left> Active Connections [sqlservr.exe] TCP <A href="http://0.0.0.0:58477" target=_blank>0.0.0.0:58477</A> <A href="http://0.0.0.0:0" target=_blank>0.0.0.0:0</A> LISTENING [sqlservr.exe] TCP <A href="http://0.0.0.0:62502" target=_blank>0.0.0.0:62502</A> <A href="http://0.0.0.0:0" target=_blank>0.0.0.0:0</A> LISTENING [sqlservr.exe] TCP <A href="http://0.0.0.0:65249" target=_blank>0.0.0.0:65249</A> <A href="http://0.0.0.0:0" target=_blank>0.0.0.0:0</A> LISTENING [sqlservr.exe] TCP <A href="http://127.0.0.1:58751" target=_blank>127.0.0.1:58751</A> <A href="http://0.0.0.0:0" target=_blank>0.0.0.0:0</A> LISTENING [sqlservr.exe] TCP <A href="http://127.0.0.1:62503" target=_blank>127.0.0.1:62503</A> <A href="http://0.0.0.0:0" target=_blank>0.0.0.0:0</A> LISTENING [sqlservr.exe] TCP <A href="http://127.0.0.1:63954" target=_blank>127.0.0.1:63954</A> <A href="http://127.0.0.1:63955" target=_blank>127.0.0.1:63955</A> ESTABLISHED [sqlservr.exe] TCP <A href="http://192.168.40.114:62502" target=_blank>192.168.40.114:62502</A> <A href="http://192.168.40.122:50342" target=_blank>192.168.40.122:50342</A> ESTABLISHED [sqlservr.exe] TCP <A href="http://192.168.40.114:62502" target=_blank>192.168.40.114:62502</A> <A href="http://192.168.40.125:60257" target=_blank>192.168.40.125:60257</A> ESTABLISHED [sqlservr.exe] TCP <A href="http://192.168.125.1:139" target=_blank>192.168.125.1:139</A> <A href="http://0.0.0.0:0" target=_blank>0.0.0.0:0</A> LISTENING [sqlservr.exe] TCP [::]:58477 [::]:0 LISTENING [sqlservr.exe] TCP [::]:62502 [::]:0 LISTENING [sqlservr.exe] TCP [::]:65249 [::]:0 LISTENING [sqlservr.exe] TCP [::1]:58751 [::]:0 LISTENING [sqlservr.exe] TCP [::1]:62005 [::1]:62006 ESTABLISHED [sqlservr.exe] UDP <A href="http://0.0.0.0:123" target=_blank>0.0.0.0:123</A> *:* If the default port, 1433, is not reachable would one the above ports be the alternate means of connecting to the server? </DIV> <DIV dir=ltr lang=en-us align=left> <HR> From: Claudio Kuenzler [mailto:<A href="mailto:ck@claudiokuenzler.com" target=_blank>ck@claudiokuenzler.com</A>] Sent: Thursday, November 17, 2011 1:39 PM <DIV class=im> To: Nagios Users List Subject: Re: [Nagios-users] Monitoring a Microsoft SQL Server </DIV> </DIV> <DIV> <DIV></DIV> <DIV class=h5> <DIV></DIV>Please let us know if you get it working - I might have to add such a check soon as well. To answer your question: 1433 is the standard port of MSSQL so that should be ok. You can launch nmap or a simple telnet to double-check that. <DIV class=gmail_quote>On Thu, Nov 17, 2011 at 4:34 PM, Jim Avery <<A href="mailto:jim@jimavery.me.uk" target=_blank>jim@jimavery.me.uk</A>> wrote: <BLOCKQUOTE style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class=gmail_quote> <DIV>On 17 November 2011 15:17, Kaplan, Andrew H. <<A href="mailto:AHKAPLAN@partners.org" target=_blank>AHKAPLAN@partners.org</A>> wrote: > 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. </DIV>The check_mssql plugin is way too fussy about what characters it will allow in host names and user names. On my system I edited the plugin to remove the if/else sections entirely below the comments "// Validate the hostname" and "// Validate the username". hth, Jim <DIV> <DIV></DIV> <DIV> ------------------------------------------------------------------------------ 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. <A href="http://p.sf.net/sfu/splunk-novd2d" target=_blank>http://p.sf.net/sfu/splunk-novd2d</A> _______________________________________________ Nagios-users mailing list <A href="mailto:Nagios-users@lists.sourceforge.net" target=_blank>Nagios-users@lists.sourceforge.net</A> <A href="https://lists.sourceforge.net/lists/listinfo/nagios-users" target=_blank>https://lists.sourceforge.net/lists/listinfo/nagios-users</A> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null </DIV></DIV></BLOCKQUOTE></DIV> </DIV></DIV> <DIV class=im> 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 <A href="http://www.partners.org/complianceline" target=_blank>http://www.partners.org/complianceline</A> . 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.</DIV></DIV></BLOCKQUOTE></DIV> </BODY></HTML>