Summary

chicken-install fails with TCP connect timeout

Metadata

Description

The TCP connect timeout error is back! I cannot install nemo under either Linux or Mac OS X. Any help is appreciated.

 /bin/chicken/bin/chicken-install nemo
 resolving alias `kitten-technologies' to: http://chicken.kitten-technologies.co.uk/henrietta.cgi
 retrieving ...
 connecting to host "chicken.kitten-technologies.co.uk", port 80 ...
 requesting "/henrietta.cgi?name=nemo&mode=default" ...
 reading response ...
 TCP connect timeout
 resolving alias `call-cc.org' to: http://code.call-cc.org/cgi-bin/henrietta.cgi
 connecting to host "code.call-cc.org", port 80 ...
 requesting "/cgi-bin/henrietta.cgi?name=nemo&mode=default" ...
 reading response ...
 TCP connect timeout

Changes and comments

[2009-04-21 09:11:15 UTC] felix wrote:

Is this system-specific, or does it happen always?

Please try to unapply the commit r14101 and check wether it has any influence.

[2009-04-21 09:23:34 UTC] iraikov wrote:

The problem occurs on several identically configured Debian Linux systems with slightly different kernel versions, ranging from 2.6.24 to 2.6.26. Patch r14101 seems to have no influence. I have tried both Chicken 4.0.0, which does not include the patch, and 4.0.1, which does, but I get this error in both cases.

Replying to felix: > Is this system-specific, or does it happen always? > > Please try to unapply the commit r14101 and check wether it has any influence.

[2009-04-21 10:56:56 UTC] felix wrote:

Replying to iraikov: > > The problem occurs on several identically configured Debian Linux systems with slightly different kernel versions, ranging from 2.6.24 to 2.6.26. Patch r14101 seems to have no influence. I have tried both Chicken 4.0.0, which does not include the patch, and 4.0.1, which does, but I get this error in both cases. > > Replying to felix: > > Is this system-specific, or does it happen always? > > > > Please try to unapply the commit r14101 and check wether it has any influence.

If you comment the call to `(close-output-port out)` out does increasing the TCP timeout help? Is this a particularly slow connection?

[2009-04-21 10:57:06 UTC] felix changed version from 4.0.0 to 4.0.1

[2009-04-22 02:37:11 UTC] iraikov wrote:

Increasing the tcp-read-timeout to 20000 (20 seconds) allows the installation of sxml-transforms to proceed without problems. The connection is indeed somewhat slow.

Replying to felix:

> If you comment the call to `(close-output-port out)` out does increasing the TCP > timeout help? Is this a particularly slow connection?

[2009-04-23 09:52:10 UTC] felix wrote:

Please try r14397. I increased the read/write timeout to 20 secs and close both in- and output ports together at the end.

If this works you can close the ticket.

[2009-04-27 06:19:43 UTC] iraikov changed status from new to closed

[2009-04-27 06:19:43 UTC] iraikov set resolution to fixed

[2009-04-27 06:19:43 UTC] iraikov wrote:

It seems to be working now.

[2011-04-30 06:12:33 UTC] iraikov changed status from closed to reopened

[2011-04-30 06:12:33 UTC] iraikov changed version from 4.0.1 to 4.6.x

[2011-04-30 06:12:33 UTC] iraikov removed resolution fixed

[2011-04-30 06:12:33 UTC] iraikov changed description

[2011-04-30 06:12:33 UTC] iraikov set milestone to 4.7.0

[2011-04-30 22:44:27 UTC] felix wrote:

Does increasing the timeout help, or is this caused by something different?

[2011-05-01 03:59:12 UTC] iraikov wrote:

Yes, increasing the timeout to from 20 to 30 seconds helps with this particular egg. However, shouldn't there be a more robust download procedure that first determines if the egg exists on the particular server, then tries to fetch it using increasing timeout values?

Replying to felix: > Does increasing the timeout help, or is this caused by something different?

[2011-05-02 12:52:31 UTC] felix wrote:

Replying to iraikov: > Yes, increasing the timeout to from 20 to 30 seconds helps with this particular egg. However, shouldn't there be a more robust download procedure that first determines if the egg exists on the particular server, then > tries to fetch it using increasing timeout values? >

To test for the egg being existant, we have to connect, which may timeout. I think there is not much we can do but increase the timeout values or fix your network connection.

I'll increase the timeout to 30 secs, then.

[2011-05-02 14:10:49 UTC] felix changed status from reopened to closed

[2011-05-02 14:10:49 UTC] felix set resolution to worksforme

[2011-05-02 14:10:49 UTC] felix wrote:

I increased the connection and read/write timeouts to 30 secs (merge into "master","experimental" and "prerelease").

[2011-06-01 09:00:41 UTC] felix changed milestone from 4.7.0 to 4.8.0

[2011-06-01 09:00:41 UTC] felix wrote:

Milestone 4.7.0 deleted

[2012-09-24 21:47:48 UTC] felix changed milestone from 4.8.0 to 4.9.0

[2012-09-24 21:47:48 UTC] felix wrote:

Milestone 4.8.0 deleted