171.64.65.101 - 171.67.108.49:80
Moderators: Site Moderators, FAHC Science Team
171.64.65.101 - 171.67.108.49:80
19:28:16:WARNING:WU03:FS01:Exception: Failed to send results to work server: Failed to connect to 171.64.65.101:80: No connection could be made because the target machine actively refused it.
19:28:17:WARNING:WU03:FS01:WorkServer connection failed on port 8080 trying 80
19:28:19:ERROR:WU03:FS01:Exception: Failed to connect to 171.67.108.49:80: No connection could be made because the target machine actively refused it.
anybody else having this issue today?
19:28:17:WARNING:WU03:FS01:WorkServer connection failed on port 8080 trying 80
19:28:19:ERROR:WU03:FS01:Exception: Failed to connect to 171.67.108.49:80: No connection could be made because the target machine actively refused it.
anybody else having this issue today?
Re: 171.67.108.49.80 WU7646
Checked my Windows 7 64-bit machine yesterday running version FAHClient 3.1 and found 5 WUs waiting to send using servers 171.67.108.49, 171.64.65.99, and 171.64.65.101. Tried installing version 3.6.1.
Today found one more WU waiting with additional transfer failures with 128.143.199.97, and 128.143.231.202. Log suggests 1 to 5% uploads before transfer fails. Pinged all satisfactorily, some servers currently accessible by browser, some not .. .
Hope this log sheds some light:
Today found one more WU waiting with additional transfer failures with 128.143.199.97, and 128.143.231.202. Log suggests 1 to 5% uploads before transfer fails. Pinged all satisfactorily, some servers currently accessible by browser, some not .. .
Hope this log sheds some light:
Code: Select all
******************************* Date: 2013-11-24 *******************************
09:18:28:WU07:FS00:0xa4:Completed 825000 out of 2500000 steps (33%)
09:52:50:WU07:FS00:0xa4:Completed 850000 out of 2500000 steps (34%)
10:27:19:WU07:FS00:0xa4:Completed 875000 out of 2500000 steps (35%)
10:38:17:WU03:FS00:Sending unit results: id:03 state:SEND error:NO_ERROR project:7809 run:4 clone:106 gen:54 core:0xa4 unit:0x0000004e0a3b1e874e310da387b75cc6
10:38:17:WU03:FS00:Uploading 4.13MiB to 171.64.65.99
10:38:17:WU03:FS00:Connecting to 171.64.65.99:8080
10:38:30:WU04:FS00:Sending unit results: id:04 state:SEND error:NO_ERROR project:7808 run:5 clone:80 gen:163 core:0xa4 unit:0x000000e10a3b1e874e30fa1ab34dba3b
10:38:30:WU04:FS00:Uploading 4.05MiB to 171.64.65.99
10:38:30:WU04:FS00:Connecting to 171.64.65.99:8080
10:38:38:WARNING:WU03:FS00:WorkServer connection failed on port 8080 trying 80
10:38:38:WU03:FS00:Connecting to 171.64.65.99:80
10:38:38:WU03:FS00:Upload 1.51%
10:38:51:WARNING:WU04:FS00:WorkServer connection failed on port 8080 trying 80
10:38:51:WU04:FS00:Connecting to 171.64.65.99:80
10:38:52:WU04:FS00:Upload 1.54%
10:38:59:WU03:FS00:Upload 4.54%
10:38:59:WARNING:WU03:FS00:Exception: Failed to send results to work server: Transfer failed
10:39:00:WU05:FS00:Sending unit results: id:05 state:SEND error:NO_ERROR project:7646 run:48 clone:2 gen:167 core:0xa4 unit:0x00000334664f2dcd4fa7fdec3acd14af
10:39:00:WU05:FS00:Uploading 14.01MiB to 171.64.65.101
10:39:00:WU05:FS00:Connecting to 171.64.65.101:8080
10:39:01:WU02:FS00:Sending unit results: id:02 state:SEND error:NO_ERROR project:7808 run:7 clone:222 gen:66 core:0xa4 unit:0x000000550a3b1e874e30fefb59367ccc
10:39:01:WU02:FS00:Uploading 4.05MiB to 171.64.65.99
10:39:01:WU02:FS00:Connecting to 171.64.65.99:8080
10:39:12:WU04:FS00:Upload 4.63%
10:39:12:WARNING:WU04:FS00:Exception: Failed to send results to work server: Transfer failed
10:39:17:WU01:FS00:Sending unit results: id:01 state:SEND error:NO_ERROR project:7808 run:6 clone:42 gen:63 core:0xa4 unit:0x000000570a3b1e874e30fc12d0a5579a
10:39:17:WU01:FS00:Uploading 4.05MiB to 171.64.65.99
10:39:17:WU01:FS00:Connecting to 171.64.65.99:8080
10:39:21:WARNING:WU05:FS00:WorkServer connection failed on port 8080 trying 80
10:39:21:WU05:FS00:Connecting to 171.64.65.101:80
10:39:21:WU05:FS00:Upload 0.45%
10:39:23:WARNING:WU02:FS00:WorkServer connection failed on port 8080 trying 80
10:39:23:WU02:FS00:Connecting to 171.64.65.99:80
10:39:26:WU02:FS00:Upload 1.54%
10:39:30:WU00:FS00:Sending unit results: id:00 state:SEND error:NO_ERROR project:7646 run:48 clone:0 gen:171 core:0xa4 unit:0x000001de664f2dcd4fa7fdeb58d14985
10:39:30:WU00:FS00:Uploading 14.01MiB to 171.64.65.101
10:39:30:WU00:FS00:Connecting to 171.64.65.101:8080
10:39:38:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
10:39:38:WU01:FS00:Connecting to 171.64.65.99:80
10:39:38:WU01:FS00:Upload 1.54%
10:39:42:WU05:FS00:Upload 1.34%
10:39:42:WARNING:WU05:FS00:Exception: Failed to send results to work server: Transfer failed
10:39:42:WU05:FS00:Trying to send results to collection server
10:39:42:WU05:FS00:Uploading 14.01MiB to 171.67.108.49
10:39:42:WU05:FS00:Connecting to 171.67.108.49:8080
10:39:46:WU02:FS00:Upload 4.63%
10:39:47:WARNING:WU02:FS00:Exception: Failed to send results to work server: Transfer failed
10:39:51:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80
10:39:51:WU00:FS00:Connecting to 171.64.65.101:80
10:39:52:WU00:FS00:Upload 0.45%
10:39:59:WU01:FS00:Upload 4.63%
10:39:59:WARNING:WU01:FS00:Exception: Failed to send results to work server: Transfer failed
10:40:03:WARNING:WU05:FS00:WorkServer connection failed on port 8080 trying 80
10:40:03:WU05:FS00:Connecting to 171.67.108.49:80
10:40:05:ERROR:WU05:FS00:Exception: Failed to connect to 171.67.108.49:80: No connection could be made because the target machine actively refused it.
10:40:08:WU06:FS00:Sending unit results: id:06 state:SEND error:NO_ERROR project:8570 run:0 clone:2 gen:300 core:0xa3 unit:0x00000cfc0a3b1e595122561b9c4dc5f6
10:40:08:WU06:FS00:Uploading 7.19MiB to 128.143.231.202
10:40:08:WU06:FS00:Connecting to 128.143.231.202:8080
10:40:12:WU00:FS00:Upload 1.34%
10:40:12:WARNING:WU00:FS00:Exception: Failed to send results to work server: Transfer failed
10:40:12:WU00:FS00:Trying to send results to collection server
10:40:12:WU00:FS00:Uploading 14.01MiB to 171.67.108.49
10:40:12:WU00:FS00:Connecting to 171.67.108.49:8080
10:40:29:WARNING:WU06:FS00:WorkServer connection failed on port 8080 trying 80
10:40:29:WU06:FS00:Connecting to 128.143.231.202:80
10:40:29:WU06:FS00:Upload 0.87%
10:40:33:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80
10:40:33:WU00:FS00:Connecting to 171.67.108.49:80
10:40:35:ERROR:WU00:FS00:Exception: Failed to connect to 171.67.108.49:80: No connection could be made because the target machine actively refused it.
10:40:49:WU06:FS00:Upload 1.74%
10:40:49:WARNING:WU06:FS00:Exception: Failed to send results to work server: Transfer failed
10:40:49:WU06:FS00:Trying to send results to collection server
10:40:49:WU06:FS00:Uploading 7.19MiB to 128.143.199.97
10:40:49:WU06:FS00:Connecting to 128.143.199.97:8080
10:41:10:WARNING:WU06:FS00:WorkServer connection failed on port 8080 trying 80
10:41:10:WU06:FS00:Connecting to 128.143.199.97:80
10:41:10:WU06:FS00:Upload 0.87%
10:41:30:WU06:FS00:Upload 1.74%
10:41:30:ERROR:WU06:FS00:Exception: Transfer failed
11:01:41:WU07:FS00:0xa4:Completed 900000 out of 2500000 steps (36%)
11:36:02:WU07:FS00:0xa4:Completed 925000 out of 2500000 steps (37%)
Re: 171.67.108.49.80 WU7646
Thank you for your reports.
The server status link shows 171.64.65.101 is in REJECT. PG notified.
The server status link shows 171.64.65.101 is in REJECT. PG notified.
-
- Posts: 1003
- Joined: Thu May 02, 2013 8:46 pm
- Hardware configuration: Full Time:
2x NVidia GTX 980
1x NVidia GTX 780 Ti
2x 3GHz Core i5 PC (Linux)
Retired:
3.2GHz Core i5 PC (Linux)
3.2GHz Core i5 iMac
2.8GHz Core i5 iMac
2.16GHz Core 2 Duo iMac
2GHz Core 2 Duo MacBook
1.6GHz Core 2 Duo Acer laptop - Location: Near Oxford, United Kingdom
- Contact:
Re: 171.67.108.49.80 WU7646
With these repoerted connection failures I thought I'd better check my on logs- only found one from the last few days, on 22nd :iokeith wrote:Checked my Windows 7 64-bit machine yesterday …
Code: Select all
04:18:10:WU00:FS00:Connecting to 171.64.65.124:8080.
.
.
.
04:20:17:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80
04:20:17:WU00:FS00:Connecting to 171.64.65.124:80
04:22:24:WARNING:WU00:FS00:Exception: Failed to send results to work server: Failed to connect to 171.64.65.124:80: Connection timed out
04:22:24:WU00:FS00:Trying to send results to collection server
04:22:24:WU00:FS00:Uploading 1.58MiB to 171.65.103.160
04:22:24:WU00:FS00:Connecting to 171.65.103.160:8080
04:22:30:WU00:FS00:Upload complete
04:22:30:WU00:FS00:Server responded WORK_ACK (400)
171.64.65.101 vspg14a tjlane SMP full Reject
According to the server log it has been down since 09:10 pst this morning.
-
- Posts: 117
- Joined: Mon Mar 16, 2009 3:06 am
Re: 171.67.108.49.80 WU7646
My system has been trying to transmit WUs to 171.67.108.49 over port HTTP all afternoon. I can't find it on the server status report. I can however confirm it is pingable, but rejecting connections on over port 80 when I test it via a TCP port tester I have.
Windows 8.1 64-bit, running SMP and Nvidia CUDA folding over client version 7.3.6
Windows 8.1 64-bit, running SMP and Nvidia CUDA folding over client version 7.3.6
[img 468x60]https://folding.extremeoverclocking.com ... p?u=679048[/img]
-
- Posts: 110
- Joined: Thu Apr 30, 2009 7:31 pm
- Hardware configuration: [email protected]
[email protected]
[email protected]
GTX460@800MHz - Location: Essen, Germany
Re: 171.64.65.101 - 171.67.108.49:80
Also having the same issue attempting to return 7645 (16, 0,174).
Windows 7 64-bit, Client version 7.3.6.
Windows 7 64-bit, Client version 7.3.6.
Re: 171.64.65.101 - 171.67.108.49:80
UPDATE: Now successfully uploaded to 171.64.65.101:8080STFC9F22 wrote:Also having the same issue attempting to return 7645 (16, 0,174).
Windows 7 64-bit, Client version 7.3.6.