Duane,

If WUG completes a protocol handshake, that is enough for it to think the
service is running. In a Custom Service, if you have nothing for any of the
4  fields, then WUG will still think the service is up, because it connected
(at least for some time!). But if you have a 'send command' and an 'expected
response', WUG will try to send the command and when it does not get the
expected response, it should show the service as down.

If you have text in the 'Expect on connect' only, WUG should only say the
service is up when the response matches the text. I have had to reduce the
amount of text in the Expect, like when checking several different hosts and
the hostname is part of the response. Also, when the response gives a
varying number (IMail's services show two fields at the end of the line,
total number of connections since service start and current number of
connection) within its 220 line.

What do you have in all the Custom Service fields??

It would also be a good idea if you stopped polling, then open Debug Log and
then select that host and 'Check Now'. This will cause WUG to poll that host
only and the Debug log will show the complete communications with the host.
Paste that into email.

Daniel Donnelly
________________________________________________________


----- Original Message -----
From: "Duane Waddle" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 23, 2001 11:34 PM
Subject: [WhatsUp Forum] Custom TCP/IP -- expected response not triggered on
silent disconnect


> I'm using WUG 6.02 and wondered if anyone else has seen something similar
> to this.  I'm defining a custom TCP/IP service with an command on connect
> and an expected command response.  When the application I'm connecting to
> is broken, however, the response is to close the connection without
sending
> anything in response to my command.  WUG sees this as a service OK
> condition.  I would understand a silent disconnect as being SVCUP if there
> wasn't an expected response.  But, in this case, I think that a silent
> disconnect should not match an expected response.  Anyone else able to
> confirm this behaviour?  Are my expectations as to the 'Right Thing (tm)'
> skewed?
>
> --D
>
> Duane Waddle
> [EMAIL PROTECTED]
> "With sufficient thrust, pigs fly just fine..."  -- RFC1925
>
>
> Please visit http://www.ipswitch.com/support/mailing-lists.html
> to be removed from this list.
>


Please visit http://www.ipswitch.com/support/mailing-lists.html 
to be removed from this list.

An Archive of this list is available at:
http://www.mail-archive.com/whatsup_forum%40list.ipswitch.com/

Reply via email to