<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns="http://www.w3.org/TR/REC-html40" xmlns:ns0="urn:schemas-microsoft-com:office:smarttags"> <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 12 (filtered medium)"> <style>  </style>  </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> I tend to get these when the Windows box his at a high cpu utilization, other times just cycling the service has fixed it when it wasn’t the CPU, 98% of the time I have found it to be CPU.<o:p></o:p> <o:p> </o:p> <div> Thanks,<o:p></o:p> <o:p> </o:p> Karl Yost<o:p></o:p> IQOR<o:p></o:p> karl.yost@iqor.com<o:p></o:p> Vice President, Technology<o:p></o:p> Phone: 614.284.3985<o:p></o:p> </div> <o:p> </o:p> <div> <div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'> From: nagios-users-bounces@lists.sourceforge.net [mailto:nagios-users-bounces@lists.sourceforge.net] On Behalf Of Ed Anderson Sent: Friday, February 22, 2008 5:48 PM To: nagios-users@lists.sourceforge.net Subject: [Nagios-users] Intermittent issues with check_nt and/or NSClient<o:p></o:p> </div> </div> <o:p> </o:p> I'm hoping that someone has run into this before. I'm having intermittent issues with check_nt that produces any of the following error messages:<o:p></o:p> Could not fetch information from server<o:p></o:p> or<o:p></o:p> Connection reset by peer<o:p></o:p> or<o:p></o:p> No data was received from host<o:p></o:p> <o:p> </o:p> This only happens with 2 remote servers (so far), both of which are Windows 2k3 EE / SQL 2k5 database servers. The symptoms last for about 13-15 minutes, enough time for the notifications to be sent out, then snaps back to OK statuses. I’m using NSClient on all of my Windows server, and the check_nt plugin to watch things such as disk utilization, services, CPU, etc. Here are some samples of the check_nt commands I'm using:<o:p></o:p> $USER1$/check_nt -H $HOSTADDRESS$ -p 1248 -v SERVICESTATE -l $ARG1 <o:p></o:p> $USER1$/check_nt -H $HOSTADDRESS$ -p 1248 -v CPULOAD -l $ARG1$ <o:p></o:p> $USER1$/check_nt -H $HOSTADDRESS$ -p 1248 -v USEDDISKSPACE -l $ARG1$ -w $ARG2$ -c $ARG3$ <o:p></o:p> <o:p> </o:p> Something else to note...these Nagios service checks have been in place for quite some time, and it's just recently started acting up. I’d say within the last couple weeks.<o:p></o:p> <o:p> </o:p> Any ideas? Is this as simple as increasing the timeout for check_nt, or does this mean I have some other underlying issues I need to address? I’m thinking 10 seconds should be plenty of time to run the service checks as the servers are all within the same location.<o:p></o:p> <o:p> </o:p> Nagios version = 2.10<o:p></o:p> check_nt version = v1590<o:p></o:p> NSClient version = ?? not sure how to find it.<o:p></o:p> <o:p> </o:p> <o:p> </o:p> Edward Anderson <o:p></o:p> Information Services| BI Administrator/Report Developer <o:p></o:p> <a href="mailto:ed.anderson@nwea.org">ed.anderson@nwea.org</a> | cell: 971.221.7523 | office: 503.624.1951 Ext. 4121<o:p></o:p> <div> NWEA<o:p></o:p> </div> Partnering to help all kids learn <ns0:Street><ns0:address>5885 SW Meadows Road, Suite 200</ns0:address></ns0:Street> <ns0:place><ns0:City>Lake Oswego</ns0:City>, <ns0:State><ns0:State>OR</ns0:State></ns0:State> <ns0:PostalCode><ns0:PostalCode>97035-3256</ns0:PostalCode> </ns0:PostalCode>Fax: 503.639.7873</ns0:place><o:p></o:p> </div> </body> </html>