HTTP Timeouts On All Request Types

Message boards : Questions and problems : HTTP Timeouts On All Request Types
Message board moderation

To post messages, you must log in.

AuthorMessage
Doneske

Send message
Joined: 26 May 18
Posts: 8
United States
Message 93845 - Posted: 22 Nov 2019, 18:03:37 UTC

This is a sticky problem. I have started receiving HTTP Transient Errors anytime the client does an HTTP Upload/Download/Scheduler request. This was happening on WCG but when I moved to Asteroids it happens there also. After turning on debugging flags it only shows timeouts after 120000 milliseconds. On the upload and download requests a retval of -184 is returned. This seemed to start after upgrading to 1GB Internet. I know most folks might say, since you upgraded it is probably something with the ISP. It is going to be awfully hard to get the ISP to work on it when the only thing effected is BOINC. Browser works, uploads and downloads of large files work perfectly outside BOINC. Router shows no dropped frames. Speed test from this morning shows 985 Mbps down and 1025Mbps up. The interesting thing is I have a large number of CPDN WUs running. As most may know, these WUs generate and transmit a large amount of data. All CPDN transfers work without fail even while the others to other projects are in retry state. Essentially, if I were to remove BOINC from my system(s), I wouldn't have a problem at all. I don't know what is unique about CPDN but I assume they use HTTP for the transfers like everyone else as they use the BOINC client too. I kind of at my wits end on this as I don't know quite how to go about debugging it other than the transfer debug flags. I don't have access to the servers so I can't see what is happening at that end. Most of the small things like header transfers and testing to google.com seem to work without fail. It's the larger transfers of data that seem to get the timeouts. This is running on Ubuntu 19.10 and 19.04 with BOINC client 7.16.3 I see other messages in the debug output like "Connection is still name resolving; can't reuse" which is flagged as an INFO type message and a message saying there a max connections so deleting oldest. I'm not sure if these are actual problems or just status information. I wouldn't think link speed would have any effect on the HTTP protocol but may there is something in the TCP handshake like window size or something that is messing with the remote end.
ID: 93845 · Report as offensive     Reply Quote
MarkJ
Volunteer tester
Help desk expert

Send message
Joined: 5 Mar 08
Posts: 235
Australia
Message 93859 - Posted: 22 Nov 2019, 22:10:01 UTC - in response to Message 93845.  

Have you tried setting http 1.0? From the BOINC client configuration page:

<http_1_0>0|1</http_1_0>
Set this flag to use HTTP 1.0 instead of 1.1 (this may be needed with some proxies).

Put it under the options tag. After that restart client. I wouldn’t expect any difference if browsers and other things work fine but you never know.
MarkJ
ID: 93859 · Report as offensive     Reply Quote
Profile Dave
Help desk expert

Send message
Joined: 28 Jun 10
Posts: 550
United Kingdom
Message 93870 - Posted: 23 Nov 2019, 7:56:54 UTC
Last modified: 23 Nov 2019, 8:06:36 UTC

Interesting.
I had problems with file transfers to CPDN but not to other projects after upgrading my router so that I have one that will cope when they eventually bring fibre to the box in my street. (Allegedly due towards the end of this year.)

The problem eventually cleared with the second firmware update to the router. I will scout around to see if the problem looks similar or not as I remember posting about it several time when I had the problem.

Edit: did you change the router as part of the upgrade?
ID: 93870 · Report as offensive     Reply Quote
Doneske

Send message
Joined: 26 May 18
Posts: 8
United States
Message 93896 - Posted: 24 Nov 2019, 23:10:53 UTC - in response to Message 93859.  

Have you tried setting http 1.0? From the BOINC client configuration page:

<http_1_0>0|1</http_1_0>
Set this flag to use HTTP 1.0 instead of 1.1 (this may be needed with some proxies).

Put it under the options tag. After that restart client. I wouldn’t expect any difference if browsers and other things work fine but you never know.

I have not tried that but considered it. I'm out of town right but when I get back I will give it a try. I am willing to try anything at this point. Thanks for the tip
ID: 93896 · Report as offensive     Reply Quote
Doneske

Send message
Joined: 26 May 18
Posts: 8
United States
Message 93897 - Posted: 24 Nov 2019, 23:15:34 UTC - in response to Message 93870.  

Interesting.
I had problems with file transfers to CPDN but not to other projects after upgrading my router so that I have one that will cope when they eventually bring fibre to the box in my street. (Allegedly due towards the end of this year.)

The problem eventually cleared with the second firmware update to the router. I will scout around to see if the problem looks similar or not as I remember posting about it several time when I had the problem.

Edit: did you change the router as part of the upgrade?

I did. It is fiber all the way to the router in my house. The router belongs to the vendor (ISP) it is not my router but I may give them a call to see if anyone has reported any similar problem. I just figured they would say it wasn't their problem as everything else works (including HTTP outside BOINC) but still worth a try. Another thing I have considered, is putting their router in bridge mode and use a router that belongs to me to provide routing and wifi. Thanks for the input
ID: 93897 · Report as offensive     Reply Quote
Profile Dave
Help desk expert

Send message
Joined: 28 Jun 10
Posts: 550
United Kingdom
Message 93902 - Posted: 25 Nov 2019, 11:16:32 UTC - in response to Message 93897.  

This is the link to discussion on CPDN boards about the issue I had. The issue with the Windows Tasks running under WINE turned out to be affecting those running native windows tasks at the time too so was a different problem.
ID: 93902 · Report as offensive     Reply Quote
Doneske

Send message
Joined: 26 May 18
Posts: 8
United States
Message 93959 - Posted: 30 Nov 2019, 14:20:29 UTC - in response to Message 93902.  

Update: Contacted the ISP concerning the errors and they were quite helpful in resolving the situation. Their opinion is there is a routing issue somewhere. I provided them a traceroute output and then we decided to set their modem/router to bridge mode (essentially making it a modem only) and use my wifi router to do the routing (instead of being in AP mode). After some re-plugging and reconfiguration, the problem disappeared. After running this configuration for about 24 hours, I have not seen any timeouts and WUs are uploading/downloading as expected. Even the things that were completing successfully before seem faster.
ID: 93959 · Report as offensive     Reply Quote

Message boards : Questions and problems : HTTP Timeouts On All Request Types

Copyright © 2020 University of California. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.