Opened 17 years ago
Last modified 13 years ago
#13 closed defect
chicken-install fails with TCP connect timeout — at Version 8
| Reported by: | Ivan Raikov | Owned by: | felix winkelmann |
|---|---|---|---|
| Priority: | critical | Milestone: | 4.9.0 |
| Component: | core tools | Version: | 4.6.x |
| Keywords: | tcp timeout | Cc: | |
| Estimated difficulty: |
Description (last modified by )
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
Change History (8)
follow-up: 2 comment:1 by , 17 years ago
follow-up: 3 comment:2 by , 17 years ago
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.
follow-up: 5 comment:3 by , 17 years ago
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?
comment:4 by , 17 years ago
| Version: | 4.0.0 → 4.0.1 |
|---|
comment:5 by , 17 years ago
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?
comment:6 by , 17 years ago
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.
comment:8 by , 15 years ago
| Description: | modified (diff) |
|---|---|
| Milestone: | → 4.7.0 |
| Resolution: | fixed |
| Status: | closed → reopened |
| Version: | 4.0.1 → 4.6.x |
Is this system-specific, or does it happen always?
Please try to unapply the commit r14101 and check wether it has any influence.