chicken-install fails with TCP connect timeout

[Ivan Raikov]

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

[felix winkelmann]

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

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

[Ivan Raikov]

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.

[felix winkelmann]

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?

[Ivan Raikov]

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?

[felix winkelmann]

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.

[Ivan Raikov]

It seems to be working now.

[felix winkelmann]

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

[Ivan Raikov]

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?

[felix winkelmann]

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.

[felix winkelmann]

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

[felix winkelmann]

Milestone 4.7.0 deleted

[felix winkelmann]

Milestone 4.8.0 deleted