CONN is done by the server, so it is best to look from the server's perspective. Without knowing your network and details of the server it's tough to know where to start, but I would start by seeing when the server fails to ping the host (see if you get ARP, route to it, etc).<br>
<br clear="all">Josh Luthman<br>Office: 937-552-2340<br>Direct: 937-552-2343<br>1100 Wayne St<br>Suite 1337<br>Troy, OH 45373<br>
<br><br><div class="gmail_quote">On Mon, Aug 15, 2011 at 5:11 PM, Poppy, Ben <span dir="ltr"><<a href="mailto:poppy.ben@marshfieldclinic.org">poppy.ben@marshfieldclinic.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">The 2 servers are not using the
same IP. They are tied to each other in the hobbit configs in that they point
to each other.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">My existing hobbit servers,
hobbit1 and hobbit2, are the fail-over for each other. So they have the exact
same configuration, and report data to each other in their client settings. All
servers with hobbit or bbwin clients send data to both servers.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">When I bring the new replacement
server online, I shutdown hobbit2, and have the new server assume it's IP.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">I will try the ping test to see
exactly when it stops responding..<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">The strangest thing, like I
said, is it's the exact same 4 hosts that show red for CONN. This was with
every combination of centos/xymon/hobbit below.. I even cloned one of my
existing centos 5 32-bit servers running hobbit 4.2 in another environment (our
perimeter network that is firewalled off), such that the only thing that was
different was the linux distro, and that also caused the same 4 servers to show
red..<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><u></u> <u></u></span></p>
<div style="border-width: 1pt medium medium; border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span style="font-size: 10pt;">From:</span></b><span style="font-size: 10pt;"> Josh Luthman
[mailto:<a href="mailto:josh@imaginenetworksllc.com" target="_blank">josh@imaginenetworksllc.com</a>] <br>
<b>Sent:</b> Monday, August 15, 2011 4:07 PM<br>
<b>To:</b> Poppy, Ben<br>
<b>Cc:</b> <a href="mailto:xymon@xymon.com" target="_blank">xymon@xymon.com</a><br>
<b>Subject:</b> Re: [Xymon] New server causing issues with CONN test<u></u><u></u></span></p>
</div><div><div></div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<p>Are the two servers using the same IP? Tied to one another in any
way? I would start a ping and turn the other server on and see when it
goes down. <u></u><u></u></p>
<div>
<p class="MsoNormal">On Aug 15, 2011 5:03 PM, "Poppy, Ben" <<a href="mailto:poppy.ben@marshfieldclinic.org" target="_blank">poppy.ben@marshfieldclinic.org</a>>
wrote:<br>
> I'm having a pretty strange issue. We have our existing hobbit servers
running on Fedora servers running hobbit 4.2.0. I'm working on installing brand
new servers that will be running CentOS 6 64-bit and the latest version of
xymon (4.3.3 before I saw 4.3.4 today). I did not see a fix to my issue in the
4.3.4 change log though, so figured I'd post here.<br>
> <br>
> In doing my update, I install the brand new server from scratch. Basically
install CentOS 6 as a web server install, and then add in all the bits xymon
needs (pcre, openssl, openldap, rrdtool, etc).. Then I compile and install
xymon to /usr/lib/xymon. Next I copy over the bb-hosts file to the hosts.cfg,
and follow the "migration" steps to get the data and configuration
files over. Then I turn on xymon on the new server.<br>
> <br>
> Within a few minutes, 4 servers turn to red alerts on CONN on the existing
Fedora based Hobbit servers. They begin flapping on and off of red alert until
I shutdown the new CentOS xymon server. Within a few minutes of the new server
being shut down, the alerts go away for good.<br>
> <br>
> I have tried going to Centos 5 32-bit, 64-bit, even trying xymon 4.2.3, or
all the way back to hobbit 4.2.0 all with the same result, and the exact same 4
servers each time.<br>
> <br>
> I'm completely at a loss here. Does anyone know what may be causing these
issues where the only difference is the OS being used (the distro, that is)?<br>
> <br>
> I just want to get our monitoring server upgraded to a stable OS, with
updates, and get xymon up to date as well.<br>
> <br>
> Thanks,<br>
> -Ben<br>
> <br>
> ______________________________________________________________________<br>
> The contents of this message may contain private, protected and/or
privileged information. If you received this message in error, you should
destroy the e-mail message and any attachments or copies, and you are
prohibited from retaining, distributing, disclosing or using any information
contained within. Please contact the sender and advise of the erroneous
delivery by return e-mail or telephone. Thank you for your cooperation.<u></u><u></u></p>
</div>
</div></div></div><div><div></div><div class="h5">
<hr>The contents of this message may contain private, protected and/or privileged information. If you received this message in error, you should destroy the e-mail message and any attachments or copies, and you are prohibited from retaining, distributing, disclosing or using any information contained within. Please contact the sender and advise of the erroneous delivery by return e-mail or telephone. Thank you for your cooperation.<br>
</div></div></div>
</blockquote></div><br>