Page 1 of 1
Can't connect with 140.163.4.231
Posted: Mon Apr 21, 2014 2:41 pm
by Foezjie
Hello everyone,
I hope I'm in the correct subforum for this. If not, my apologies.
When trying to get a work unit for my GPU, it never begins downloading.
Log:
07:11:47:WU00:FS01:Assigned to work server 140.163.4.231
07:11:47:WU00:FS01:Requesting new work unit for slot 01: READY gpu:0:GK106 [GeForce GTX 660] from 140.163.4.231
07:11:47:WU00:FS01:Connecting to 140.163.4.231:8080
07:11:50:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
07:11:50:WU00:FS01:Connecting to 140.163.4.231:80
07:11:50:ERROR:WU00:FS01:Exception: Failed to connect to 140.163.4.231:80: Connection refused
07:13:23:WU00:FS01:Connecting to 171.67.108.201:80
07:13:24:WU00:FS01:Assigned to work server 140.163.4.231
07:13:24:WU00:FS01:Requesting new work unit for slot 01: READY gpu:0:GK106 [GeForce GTX 660] from 140.163.4.231
07:13:24:WU00:FS01:Connecting to 140.163.4.231:8080
07:13:27:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
07:13:27:WU00:FS01:Connecting to 140.163.4.231:80
....
The server status page for that server seems ok:
140.163.4.231 plfah1-1 kyleb GPU full Accepting 0.25 9 0 1 20676 20676 20676 124 33 0 0 0 0 WL_9000_F_8080G; WL_5000_A_8080G; W_9000_F_8080G; W_5000_A_8080G
I can't ping to it though, not using my pc, not from one of my servers on a different network.
If i go to 140.163.4.231:80 I get ERR_CONNECTION_REFUSED (chromium), if I go to it using port 8080 I get ERR_ADDRESS_UNREACHABLE.
This is all on a Lubuntu 12.04 pc. I can get CPU work units just fine.
Re: Can't connect with 140.163.4.231
Posted: Mon Apr 21, 2014 6:30 pm
by PantherX
Welcome to the F@H Forum Foezjie,
Can you please tell us what version of V7 you are using? Do note that for the GPU to fold, you need a 64-bit OS and using Nvidia's Propriety Drivers.
Can you perform a traceroute and see what your results are?
Re: Can't connect with 140.163.4.231
Posted: Mon Apr 21, 2014 6:52 pm
by Foezjie
PantherX wrote:Welcome to the F@H Forum Foezjie,
Can you please tell us what version of V7 you are using? Do note that for the GPU to fold, you need a 64-bit OS and using Nvidia's Propriety Drivers.
Can you perform a traceroute and see what your results are?
I am using version 7.4.4.
Traceroute:
Code: Select all
traceroute to 140.163.4.231 (140.163.4.231), 30 hops max, 60 byte packets
1 172.18.222.1 (172.18.222.1) 1.963 ms 3.019 ms 5.076 ms
2 192.168.12.1 (192.168.12.1) 24.239 ms 25.433 ms 26.628 ms
3 192.168.3.1 (192.168.3.1) 27.942 ms 29.372 ms 30.576 ms
4 94-224-16-1.access.telenet.be (94.224.16.1) 42.908 ms 44.033 ms 45.692 ms
5 dD5E0C601.access.telenet.be (213.224.198.1) 53.502 ms 52.130 ms 54.722 ms
6 dD5E0FD25.access.telenet.be (213.224.253.37) 61.192 ms 12.337 ms 24.693 ms
7 * * *
8 ae-0-11.bar2.Brussels1.Level3.net (4.69.148.178) 26.608 ms * 31.105 ms
9 ae-7-7.ebr1.London1.Level3.net (4.69.148.182) 111.194 ms 114.617 ms 115.977 ms
10 vlan102.ebr2.London1.Level3.net (4.69.143.90) 120.643 ms vlan103.ebr2.London1.Level3.net (4.69.143.94) 122.148 ms 139.821 ms
11 ae-43-43.ebr1.NewYork1.Level3.net (4.69.137.74) 130.459 ms ae-44-44.ebr1.NewYork1.Level3.net (4.69.137.78) 135.202 ms ae-43-43.ebr1.NewYork1.Level3.net (4.69.137.74) 133.612 ms
12 ae-81-81.csw3.NewYork1.Level3.net (4.69.134.74) 116.674 ms 120.869 ms ae-91-91.csw4.NewYork1.Level3.net (4.69.134.78) 114.723 ms
13 ae-72-72.ebr2.NewYork1.Level3.net (4.69.148.37) 85.394 ms 87.720 ms ae-62-62.ebr2.NewYork1.Level3.net (4.69.148.33) 90.025 ms
14 ae-2-2.ebr1.Newark1.Level3.net (4.69.132.98) 90.454 ms 92.085 ms 89.825 ms
15 ae-1-51.edge2.Newark1.Level3.net (4.69.156.9) 89.602 ms 102.846 ms 99.343 ms
16 MEMORIAL-SL.edge2.Newark1.Level3.net (4.30.135.222) 103.249 ms 99.777 ms 95.998 ms
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
I am using a 64 bit version, and using the nvidia drivers. (Linux Harm-PC 3.8.0-35-generic #50-Ubuntu SMP Tue Dec 3 01:24:59 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
)
Re: Can't connect with 140.163.4.231
Posted: Sun Apr 27, 2014 4:19 pm
by Foezjie
No ideas on how to solve this?
Re: Can't connect with 140.163.4.231
Posted: Sun Apr 27, 2014 5:34 pm
by bollix47
I'm not seeing any problems uploading/downloading with that server. Currently I have five WUs running from it and just uploaded to and downloaded from 140.163.4.231:8080 within the last hour. Have you tried rebooting all the hardware involved(computer, modem, router)? You could also try adding client-type advanced to see if you get assigned to a different work server which may work for you. Changing your DNS servers might help as well although you don't seem to be having a problem reaching the AS so I'm not sure that will solve anything but could be worth a try. Is there any security software involved that you can temporarily disable and try again?
My tracert and ping are both unsuccessful:
Code: Select all
tracert 140.163.4.231
Tracing route to plfah1-1.mskcc.org [140.163.4.231]
over a maximum of 30 hops:
1 2 ms <1 ms <1 ms 192.168.2.1
2 15 ms 10 ms 11 ms 7.11.160.69
3 622 ms 727 ms 11 ms 209.148.244.193
4 11 ms 11 ms 12 ms 69.63.248.209
5 13 ms 19 ms 15 ms 69.63.248.201
6 28 ms 40 ms 47 ms 69.63.248.89
7 * * * Request timed out.
8 789 ms 854 ms 886 ms xe-1-0-1.cr1.lga5.us.above.net [
9 931 ms 924 ms 917 ms ae1.cr2.lga5.us.above.net [64.12
10 962 ms 998 ms 953 ms ae3.er4.lga5.us.above.net [64.12
11 775 ms 815 ms 885 ms L3-Zayo.lga5.us.above.net [64.12
12 989 ms 851 ms 727 ms vlan90.csw4.NewYork1.Level3.net
13 28 ms 30 ms 28 ms ae-92-92.ebr2.NewYork1.Level3.ne
14 26 ms 27 ms 27 ms ae-2-2.ebr1.Newark1.Level3.net [
15 31 ms 26 ms 29 ms ae-1-51.edge2.Newark1.Level3.net
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.
Trace complete.
ping 140.163.4.231
Pinging 140.163.4.231 with 32 bytes of data:
Request timed out.
Ping statistics for 140.163.4.231:
Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
Control-C
Trying
http://140.163.4.231:8080/ in my browser results in:
401 HTTP UNAUTHORIZED /
which is a legitimate response.
Even though the above trace and ping tests didn't succeed the client is having no problems uploading or downloading with that server and I suspect if there was a problem we would be receiving lots of reports.