On Tue, Jan 24, 2012 at 11:53 AM, Ralph Mitchell
<user-00a5e44c48c0@xymon.invalid> wrote:
On Tue, Jan 24, 2012 at 11:43 AM, Asif Iqbal <user-6f4b51ac2a40@xymon.invalid> wrote:
On Tue, Jan 24, 2012 at 11:24 AM, Asif Iqbal <user-6f4b51ac2a40@xymon.invalid> wrote:
On Tue, Jan 24, 2012 at 11:13 AM, Root, Paul <user-76fdb6883669@xymon.invalid>
wrote:
Hi,
We are monitoring a particular port that we are having issues
with. 8022, it's a proxy port for HP NA.
Anyway, I have an expect script that goes in and tests the
functionality of the port. But when it starts to go bad, this script get
stuck in TIME_WAIT, along with the users connecting to the port.
why not use ssh:8022:s in hosts.cfg ?
So, can I look at the port data before I try connecting, and if
there are a bunch of TIME_WAIT connections, just skip the test entirely?
I'm running the test from the xymon server, so I was thinking of
pulling the data out of xymon directly. Would that by xymoncmd?
if you like to pursue your method and just want to count the number of
TIME_WAIT for port 8022, you can run something like this from xymon
server
xymon localhost "clientlog host.example.net section=ports" | grep
8022 | grep TIME_WAIT
This works too:
/home/xymon/server/bin/xymon localhost "xymondlog
server.domain.com.ports"
only if you setup rules for it and have a test column for ports.
Ralph Mitchell
--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?