<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div><br>
</div>
<div>I am running the latest version of xymon, with J.C. Cleaver's patches.</div>
<div><br>
</div>
<div>I have a xymonproxy that sits dual homed, forwarding messages from one network segment to the main xymon display.</div>
<div>It's roughly 4,000 hosts, about half using bbwin as their client, the other half are linux xymon clients.</div>
<div><br>
</div>
<div>The proxy is mostly working, but is dropping/retransmitting messages as well – the log indicates a problem with getting SIGPIPE like this:</div>
<div><br>
</div>
<div>
<div>2014-12-11 10:29:28.204598 conn 8182371, socket 238: error writing to socket: Broken pipe</div>
<div>2014-12-11 10:29:28.204608 conn 8182371, socket 238: attempting recovery from write error to server 0 (192.168.0.100:1984): Broken pipe</div>
<div>2014-12-11 10:29:28 Got SIGPIPE...</div>
<div>2014-12-11 10:29:28.208113 conn 8179105, socket 131: error writing to socket: Broken pipe</div>
<div>2014-12-11 10:29:28.208118 conn 8179105, socket 131: attempting recovery from write error to server 0 (192.168.0.100:1984): Broken pipe</div>
</div>
<div><br>
</div>
<div>I've played around with lqueue settings, and timeout settings, to no avail – it seems to constantly be posting those messages in log no matter what.</div>
<div><br>
</div>
<div>Ulimit for open files for xymon is 65535, and I don't see it going above 200-300 open files</div>
<div><br>
</div>
<div>The report lists this under resources: (also looks like there is a spelling error for resource in xymonproxy.c, which is duplicated in the man pages)</div>
<div><br>
</div>
<div>
<div>Proxy ressources</div>
<div>- Connection table size : 134</div>
<div>- Buffer space : 6504124 kByte</div>
<div><br>
</div>
<div><br>
</div>
<div>Timeout/failure details</div>
<div>- reading from client : 24</div>
<div>- connecting to server : 0</div>
<div>- sending to bfq : 0</div>
<div>- bfq recovered : 0</div>
<div>- sending to server : 593820</div>
<div>- recovered : 53130</div>
<div>- reading from server : 24</div>
<div>- sending to client : 0</div>
</div>
<div><br>
</div>
<div><br>
</div>
<div>On the receiving server, it tells me in xymond.log --> Discarding timed-out partial msg from X.X.X.X</div>
<div><br>
</div>
<div>Wondering what the next steps I can take for troubleshooting/fixing — any thoughts?</div>
<div>Tweaks on receiving server? Changes to xymonproxy? Network pathing issues?</div>
<div><br>
</div>
<div><br>
</div>
<div>-Sean</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div style="font-family: Consolas; font-size: medium; "></div>
</div>
<br>
<hr>
<font face="Arial" color="Gray" size="1">This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely
for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to
this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.<br>
</font>
</body>
</html>