Mailing List Archive

Dave Lyon wrote:
> I'm seeing a ton of these errors:
> [Thu May 15 15:53:36 2003] [warn] (4)Interrupted system call: connect()
> timed out
> They only happen on one of our test web servers. Any ideas or
> suggestions? Thanks.

That would happen if a machine receiving a request attempts to backhand it to
another machine that just went down and hasn't yet being marked down yet by
mod_backhand.

--
Theo Schlossnagle
Principal Consultant
OmniTI Computer Consulting, Inc. -- http://www.omniti.com/
Phone: +1 410 872 4910 x201 Fax: +1 410 872 4911
1024D/82844984/95FD 30F1 489E 4613 F22E 491A 7E88 364C 8284 4984
2047R/33131B65/71 F7 95 64 49 76 5D BA 3D 90 B9 9F BE 27 24 E7

We found a post about it earlier and disabled connection pooling as he
did and we are no longer receiving the error. We were getting hundreds
of lines of this error every 4 seconds or so on one of the two web
servers. Thanks for the reply.

On Fri, 2003-05-16 at 13:00, Theo E. Schlossnagle wrote:
> Dave Lyon wrote:
> > I'm seeing a ton of these errors:
> > [Thu May 15 15:53:36 2003] [warn] (4)Interrupted system call: connect()
> > timed out
> > They only happen on one of our test web servers. Any ideas or
> > suggestions? Thanks.
>
> That would happen if a machine receiving a request attempts to backhand it to
> another machine that just went down and hasn't yet being marked down yet by
> mod_backhand.

We ran into this problem also when using a one-tier, multi-point cluster. To
reduce the problem we switched to a two-tier multipoint cluster, turned
BackhandConnectionPools off, and turned off keep alives. I still find that
the problem reappears once any of the servers in first tier servers hits
it's max clients. The only solution i found to stop that was to add more
servers to the second tier.

I would be interested in hearing about other configurations out there and if
others are running into this problem and their solutions.


-----Original Message-----
From: backhand-users-admin@lists.backhand.org
[mailto:backhand-users-admin@lists.backhand.org]On Behalf Of Dave Lyon
Sent: Friday, May 16, 2003 1:13 PM
To: backhand-users@lists.backhand.org
Subject: Re: [m_b_users] Interrupted System Call


We found a post about it earlier and disabled connection pooling as he
did and we are no longer receiving the error. We were getting hundreds
of lines of this error every 4 seconds or so on one of the two web
servers. Thanks for the reply.

On Fri, 2003-05-16 at 13:00, Theo E. Schlossnagle wrote:
> Dave Lyon wrote:
> > I'm seeing a ton of these errors:
> > [Thu May 15 15:53:36 2003] [warn] (4)Interrupted system call: connect()
> > timed out
> > They only happen on one of our test web servers. Any ideas or
> > suggestions? Thanks.
>
> That would happen if a machine receiving a request attempts to backhand it
to
> another machine that just went down and hasn't yet being marked down yet
by
> mod_backhand.



_______________________________________________
backhand-users mailing list
backhand-users@lists.backhand.org
http://lists.backhand.org/mailman/listinfo/backhand-users

Hi there,

I'm using mod_backhand on a 3 machine-webserver-cluster for about 3 weeks now.
On the "Master" I always have this error in our apache-error-log:
[Wed Apr 7 16:50:57 2004] [warn] (4)Interrupted system call: connect() timed
out

every 2-5 minutes or so, about 100 lines each time.
I've just read about this problem but there was no real solution for this and
the posts where quite old so I ask again carefully:
Is there a solution or some workaround for this beneath switching keepalive
off or something?

I already tried to switch off the connectionpool but my apache didn't wanted
it this way and just hung.

Tobi