I don't see a problem with those servers. I checked yesterdays logs around your time but everything was working. Maybe a temporary issue at your ISP. Do you still see that?
I don't see a problem with those servers. I checked yesterdays logs around your time but everything was working. Maybe a temporary issue at your ISP. Do you still see that?
Yes, still the same here - 188 transfers stalled across five machines (at the moment, I'm running exclusively BRP4 for intel_gpu, so they mount up quickly). No sign of any problems with other projects or with web browsing, all over the same ISP link. I'll grab some coffee and start poking around.
Can you confirm that DNS has resolved the correct IP address for me - I sometimes find that DNS resolution is the weakest link in British Telecom's internet backbone.
OK, tried that using Chrome browser on one of the affected machines - the same browser/machine as I'm using to post this reply. No dice - "This site can't be reached", ERR_CONNECTION_TIMED_OUT. Same with the download url.
No response to a ping, either. Here's the tracert:
1 1 ms 1 ms 1 ms BThomehub.home
2 * * * Request timed out.
3 * * 11 ms 31.55.185.181
4 12 ms 11 ms 12 ms 31.55.185.180
5 11 ms 11 ms 11 ms 195.99.127.208
6 13 ms 12 ms 13 ms core3-hu0-14-0-7.faraday.ukcore.bt.net [195.99.127.64]
7 12 ms 11 ms 12 ms 62.6.201.145
8 23 ms 12 ms 12 ms 213.137.183.102
9 30 ms 29 ms 29 ms t2c4-xe-0-0-0-0.de-fra.eu.bt.net [166.49.208.32]
10 * * * Request timed out.
11 40 ms 39 ms 39 ms cr-han2-be6.x-win.dfn.de [188.1.144.134]
12 36 ms 70 ms 36 ms kr-han68-0.x-win.dfn.de [188.1.232.206]
13 39 ms 38 ms 38 ms fwgw-2-ext.connect.uni-hannover.de [130.75.78.232]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Host is Windows 7, network is 10 Mbit upload over fibre - it's just sent over 100 MByte to another project without problems. BOINC is a homebuild, later than v7.6.33 and with minor tweaks for debugging, but nothing affecting the network functions.
That is strange. I can reach both from different networks(Germany and USA). You must get a ping back from each of them . There are only three hidden hops between fwgw-2-ext.connect.uni-hannover.de and the actual server. I'm sorry but I can't reproduce.
Can you send me your current IP, the filename and the time of your latest trial for testing the download server in a PM? I can look up those things in the logfile of einstein1 to see if your request reaches the server. Maybe there is an issue with routing the answer back to you.
Hi Richard, I don't see a
)
Hi Richard,
I don't see a problem with those servers. I checked yesterdays logs around your time but everything was working. Maybe a temporary issue at your ISP. Do you still see that?
Christian Beer wrote:Hi
)
Yes, still the same here - 188 transfers stalled across five machines (at the moment, I'm running exclusively BRP4 for intel_gpu, so they mount up quickly). No sign of any problems with other projects or with web browsing, all over the same ISP link. I'll grab some coffee and start poking around.
Can you confirm that DNS has resolved the correct IP address for me - I sometimes find that DNS resolution is the weakest link in British Telecom's internet backbone.
Yes, it's the correct IP. You
)
Yes, it's the correct IP. You can try to access the upload handler via a browser
which should display text like this:
<data_server_reply> <status>1</status> <message>no command</message> </data_server_reply>OK, tried that using Chrome
)
OK, tried that using Chrome browser on one of the affected machines - the same browser/machine as I'm using to post this reply. No dice - "This site can't be reached", ERR_CONNECTION_TIMED_OUT. Same with the download url.
No response to a ping, either. Here's the tracert:
Host is Windows 7, network is 10 Mbit upload over fibre - it's just sent over 100 MByte to another project without problems. BOINC is a homebuild, later than v7.6.33 and with minor tweaks for debugging, but nothing affecting the network functions.
That is strange. I can reach
)
That is strange. I can reach both from different networks(Germany and USA). You must get a ping back from each of them . There are only three hidden hops between fwgw-2-ext.connect.uni-hannover.de and the actual server. I'm sorry but I can't reproduce.
Can you send me your current IP, the filename and the time of your latest trial for testing the download server in a PM? I can look up those things in the logfile of einstein1 to see if your request reaches the server. Maybe there is an issue with routing the answer back to you.
PM sent.
)
PM sent.