On Thu, 22 Jul 1999, Sascha Linn wrote:
> hi all,
>
> I've got an instance of NOCOL running and I'm trying to monitor a bank
> of webservers with it. So, in my portmon config I have the following...
> (IPs changed)
>
> # Web httpd daemon
> HOST www1 100.100.100.1 WWWport 80 Critical GET /
> HTTP/1.0\n
> info HTTP/1.1 200 OK
>
> HOST www2 100.100.100.2 WWWport 80 Critical GET /
> HTTP/1.0\n
> info HTTP/1.1 200 OK
>
> HOST www3 100.100.100.3 WWWport 80 Critical GET /
> HTTP/1.0\n
> info HTTP/1.1 200 OK
>
> HOST www4 100.100.100.4 WWWport 80 Critical GET /
> HTTP/1.0\n
> info HTTP/1.1 200 OK
>
> HOST www5 100.100.100.5 WWWport 80 Critical GET /
> HTTP/1.0\n
> info HTTP/1.1 200 OK
>
> HOST www6 100.100.100.6 WWWport 80 Critical GET /
> HTTP/1.0\n
> info HTTP/1.1 200 OK
>
> HOST www 200.200.200.16 WWWspeed 80 Critical GET /
> HTTP/1.0\n
> TIME 5 10 15 </BODY>
> TIME </Body>
> TIME </body>
>
> I've manually checked each server and all return identical results.
>
> The problem is that protmon only sees the first two servers as up and
> reports all the rest down. Has anyone seen this before? Does anyone have
> any suggestions?
>
> I've run portmon in debug mode and get the following:
>
> (debug) Connected: 'www3:80'
> (debug) portmon: Checking site 'www3:80'
> (debug) Looking for any initial connect string
> (debug) timeout_read(): Reading a line from socket..
> (debug) timeout_read: Read 0 bytes from socket
> (debug) portmon: ignoring connect string ''
> (debug) timeout_read(): Reading a line from socket..
> (debug) timeout_read: Read 0 bytes from socket
> read error for 'www3:80'read: Bad file descriptor
Last line. I've run into the same problems. Try juggling around your
host entries. Also, if one of the hosts you're monitoring is the local
host, try putting it last.
-
Greg Swallow -- Assistant System Administrator (whew!) -- Access Indiana
"The large print giveth and the small print taketh away.." - Tom Waits
http://www.ai.org -- (800) 236-5446 -- (317) 233-2010 -- gswallow@ai.org
|