[Spread-users] mod_log_spread errors in error_log

[George Schlossnagle]

I've never seen this behaviour actually.  The SP_connect is only done in
child_init, so it shouldn't be due to the Apache's double-loading of
modules.  It is possible for this to occur if a connection is broken to
spread, I guess, m_l_s works like

if(SP_multicast() < 0) {
    error_log();
    SP_disconnect();
    SP_connect();
    if(SP_multicast()< 0) {
        error_log();
    }
}

still, weird that that would be the first error.   Also, the lack of
multicast errors is strange as well (this implies that the sending is
working).  Logging is working, right?


----- Original Message -----
From: "Jonathan Stanton" <jonathan at cnds.jhu.edu>
To: <spread-users at lists.spread.org>
Sent: Thursday, August 16, 2001 10:35 AM
Subject: Re: [Spread-users] mod_log_spread errors in error_log


> On Thu, Aug 16, 2001 at 09:16:20AM -0500, Monte Ohrt wrote:
> > Hi,
> >
> > I got spread 3.15.2 and mod_log_spread working, however there are some
> > errors I am seeing in the Apache error_log that concern me:
> >
> > Here is the output to error_log when I start the server:
> >
> > [Thu Aug 16 09:05:43 2001] [notice] Create log to group test for daemon
> > 0
> > [Thu Aug 16 09:05:44 2001] [notice] set_spread_daemon(4803) for index 0
> > [Thu Aug 16 09:05:44 2001] [notice] Create log to group test for daemon
> > 0
> > [Thu Aug 16 09:05:45 2001] [notice] mod_backhand -- UnixSocketDir set to
> > /export/apache/backhand
> > [Thu Aug 16 09:05:45 2001] [notice] mod_backhand -- Broadcast
> > 10.131.192.255:4445 added
> > [Thu Aug 16 09:05:45 2001] [notice] mod_backhand -- Multicast accept
> > 10.131.192.0/24
> > [Thu Aug 16 09:05:45 2001] [notice] backhand_init(12292) spawning
> > moderator (PID 12293)
> > [Thu Aug 16 09:05:45 2001] [notice] mod_backhand moderator ready to go
> > [Thu Aug 16 09:05:45 2001] [error] (9)Bad file number: Could not connect
> > to spread  with private_name ap12294. Error -6
> > [Thu Aug 16 09:05:45 2001] [error] (9)Bad file number: Could not connect
> > to spread  with private_name ap12295. Error -6
> > [Thu Aug 16 09:05:45 2001] [error] (9)Bad file number: Could not connect
> > to spread  with private_name ap12296. Error -6
> > [Thu Aug 16 09:05:45 2001] [error] (9)Bad file number: Could not connect
> > to spread  with private_name ap12297. Error -6
> > [Thu Aug 16 09:05:45 2001] [notice] Apache/1.3.20 (Unix) mod_ssl/2.8.4
> > OpenSSL/0.9.6b mod_gzip/1.3.17.1a balanced_by_mod_backhand/1.2.0
> > configured -- resuming normal operations
> > [Thu Aug 16 09:05:45 2001] [error] (9)Bad file number: Could not connect
> > to spread  with private_name ap12298. Error -6
> >
> >
> > Although spread seems to be working fine, the "Bad file number" errors
> > are what concern me, what could be causing this?
>
> This erroor means that the private name used to connect to spread was not
> "unique" meaning some other connection using the same name was already
> established. It means the attempt to connect failed. If they only show up
> transiently when the system starts up I wouldn't worry about it. I'll
think
> and see why they happen -- probably an interaction between mod_log_spread,
> the way Apache starts processes and how spread accepts connections.
>
> If they continue regularaly after it has started then tell me. As long as
> it does succesfully connect 'quickly' (i.e. it doesn't keep failing for
> seconds) you should be ok.
>
> The mod_log_spread authors are here on this list also, they might have
seen
> this error before and have a better answer.
>
> Jonathan
> --
> -------------------------------------------------------
> Jonathan R. Stanton         jonathan at cs.jhu.edu
> Dept. of Computer Science
> Johns Hopkins University
> -------------------------------------------------------
>
>
> _______________________________________________
> spread-users mailing list
> spread-users at lists.spread.org
> http://lists.spread.org/mailman/listinfo/spread-users
>