I had a similar problem with a www server giving a false Critical. Turns
out, the developer must have uploaded the index.html file in binary mode
since each line ended with a "^M". Running a quick
tr '\r' '\n' < index.html > index.new; mv index.new index.html
removed the characters and nocol brought it's status down to Info.
Don't know if this helps,
Dave LaPorte
> -----Original Message-----
> From: owner-nocol-users@navya.com [mailto:owner-nocol-users@navya.com]On
> Behalf Of Rick Beebe
> Sent: Wednesday, September 30, 1998 3:47 PM
> To: Dinesh Mistry
> Cc: nocol-users@navya.com
> Subject: Re: more portmon problems..
>
>
> Dinesh Mistry wrote:
> >
> > Hey There,
> >
> > Vikas, thanks for the portmon2.c it seems to be working great just a
> > little problems i noticed with it. There are about 5-6 sites that
> > constantly get flagged as being down they are WWW and SMTP but when
> > I check on the status they are all up? I cannot figure out why
> it flags them
> > as being down here is the entry into the portmon.confg for a couple.
> >
> > HOST nile 198.6.114.2 SMTPport 25
> Critical HELO portmon.te
> > st
> > info 250
> >
> > HOST nypg 199.173.2.244 WWWport 80 Critical
> GET /index.html H
> > TTP/1.0\n
> >
> > Thanks for all you help much appreciated..
> >
> > Dinesh
>
> You should try the first one by hand and make sure you get back a 250 when
> you issue HELO portmon.test.
>
> I believe that the device will go to the default severity
> (critical in this
> case) unless the response matches one of the response lines. Ie, for host
> nile you're checking for a 250. If portmon gets a 250 it will set
> the device
> to Info. Since there are no response lines on the web servers it will move
> the devices to Critical. Try
>
> HOST nypg 199.173.2.244 WWWport 80 Critical GET /index.html HTTP/1.0\n
> info HTTP 1.1 200 OK
>
> Try these by hand, though. Some of my web servers return HTTP 1.0
> 200 OK and
> one of them returned HTTP 1.0 200 Retrieving data from cache (so
> I left the
> 'OK' off that entry.
>
> _____________________________________________________________________
>
> Rick Beebe (203) 785-4566
> Network Engineering Manager FAX: (203) 737-4037
> ITS-Med Technology Operations
> Richard.Beebe@yale.edu
> Yale University School of Medicine
> 333 Cedar Street, New Haven, CT 06510
> _____________________________________________________________________
>
|