Re: monit/process sysdep.c

[Jan-Henrik Haukeland]

Rory Toma <address@hidden> writes:

> Actually, I believe it is generic socket stuff. The connection tests
> also fail with various errors.

Ehh, well it's probably logical with the TIME_WAIT error poping up,
but does this means that monit hasn't worked on FreeBSD for a while? I
have spoken with people using monit on FreeBSD but that was a long
time ago.

Gurgle! I just browsed through Steven's network book and read about
TIME_WAIT, it seems to occur during closing of a socket. If this is
the case monit probably never manage to open a socket or the socket
closes immediately. I'm not sure where to start on this one, could it
be problems with the socket options we set, blocking/non-blocking
mode, the socket library... 


> On Wed, 2002-09-11 at 16:38, Jan-Henrik Haukeland wrote:
> > Rory Toma <address@hidden> writes:
> > 
> > >   I can't connect to the web interface.  I also noticed that I
> > >   can't connect to the web interface on 2.5.1 released, so I am
> > >   looking into that (may be machine config)
> > 
> > I also noticed this when I tested monit at sourceforge's freebsd
> > machine. Running netstat shows:
> > 
> > hauk:[~/monit-3.0]netstat -a |egrep 2812
> > tcp4       0      0  localhost.2812         localhost.3173         TIME_WAIT
> > 
> > While the status should say: LISTEN, I always thought that this was
> > because of some builtin firewall at sourceforge but if you get the
> > same it's probably something else. Hmm...
> > 
> > -- 
> > Jan-Henrik Haukeland
> > 
> > 
> > _______________________________________________
> > Monit-dev mailing list
> > address@hidden
> > http://mail.freesoftware.fsf.org/mailman/listinfo/monit-dev
> > 
> -- 
> Rory Toma             address@hidden
> VP of Run Level 5     http://www.trs80.net
> Digeo Digital         http://www.digeo.com

-- 
Jan-Henrik Haukeland