That's not sufficient. I have to go into the process and connect to it. But we think it may be exasperating the problem.
I'm watching how many connections we have in ports, but I'm also running my expect script test. What I'm thinking now, is tying them together. If we see it having trouble in ports, there's no reason to run the expect script.
Paul Root - Engineer III Managed Services Systems - CenturyLink
-----Original Message----- From: Asif Iqbal [mailto:vadud3 at gmail.com] Sent: Tuesday, January 24, 2012 10:25 AM To: Root, Paul Cc: xymon at xymon.com Subject: Re: [Xymon] Can I monitor how many connections are in TIME_WAIT for a specific port
On Tue, Jan 24, 2012 at 11:13 AM, Root, Paul <Paul.Root at centurylink.com> 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 thefunctionality 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, andif 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 thinkingof pulling the data out of xymon directly. Would that by xymoncmd?
Thanks, Paul.
Paul Root - Engineer III Managed Services Systems - CenturyLink
This communication is the property of CenturyLink and may contain
confidential or privileged information. Unauthorized use of this communication is strictly
prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
-- 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?
This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.