Page 2 of 3
Re: 3.133.76.19
Posted: Sat May 23, 2020 11:47 pm
by PantherX
G3WGV wrote:...my firewall was seeing something coming at it from 3.133.76.19 at the end of the upload sequence that it did not like the look of...
Pretty sure that it would be this message:
02:44:06:WU00:FS01:Upload 98.23%
02:44:08:WU00:FS01:Upload complete
02:44:08:WU00:FS01:
Server responded WORK_ACK (400)
02:44:08:WU00:FS01:Final credit estimate, 85469.00 points
Re: Upload Issues to 3.133.76.19:80
Posted: Sun May 24, 2020 3:57 am
by Juggy
Thank you PantheraX, 37 minutes after I posted this the WU uploaded for a final score of 157K
Glad the result got returned, at least now i know what to do if I see this behaviour again.
Re: 3.133.76.19
Posted: Sun May 24, 2020 8:22 am
by G3WGV
I think it would have to be something else, PantherX, probably at a TCP/IP level rather than payload content, since the firewall was clearly throwing a hissy fit at it. Of course the server almost certainly is not sending plain text. Maybe I should wireshark it to find out. I don't suppose the protocol is published.
I will try removing the exception today and see what happens!
Re: 3.133.76.19
Posted: Sun May 24, 2020 9:23 am
by bumbel123
@G3WGV
Your firewall setting or not, that specific server 3.133.76.19 just sucks. I have no harsh firewall restrictions and am connected with a very fast and reliable connection. My bunch of folding servers have absolutely no issues with down- or uploads, any final FAH result file is uploaded with ease in seconds, no matter what size.
The only exception is that specific AWS server, 3.133.76.19, that piece of ... does only respond after many tries and upload speed is always slow as on my first times in internet, back in the 1990s. And these are not single issues anymore, rather daily business as soon as 3.133.76.19 steps into the game.
And unfortunately it's always good habit here to blame the donor having anything wrong on its side ...
Re: Upload Issues to 3.133.76.19:80
Posted: Sun May 24, 2020 1:10 pm
by Juggy
I'm experiencing the same behaviour on this server again
13:08:11:WU00:FS01:Sending unit results: id:00 state:SEND error:FAILED project:16434 run:169 clone:2 gen:40 core:0x22 unit:0x0000003f03854c135e9cbacc28dd9a63
13:08:11:WU00:FS01:Connecting to 3.133.76.19:8080
13:08:47:WU01:FS01:0x22:Completed 10000 out of 1000000 steps (1%)
13:09:24:WARNING:WU00:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
And then I got this
13:18:24:WARNING:WU00:FS01:Too many failed attempts to report WORK_FAILED, dumping
13:18:24:WARNING:WU00:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
13:18:24:WU00:FS01:Cleaning up
Re: 3.133.76.19
Posted: Sun May 24, 2020 2:46 pm
by Joe_H
G3WGV wrote:I think it would have to be something else, PantherX, probably at a TCP/IP level rather than payload content, since the firewall was clearly throwing a hissy fit at it. Of course the server almost certainly is not sending plain text. Maybe I should wireshark it to find out. I don't suppose the protocol is published.
The protocol is published, all transfers between clients and serves are done over HTTP on either port 8080 or port 80.
Re: 3.133.76.19
Posted: Sun May 24, 2020 3:12 pm
by uyaem
bumbel123 wrote:And unfortunately it's always good habit here to blame the donor having anything wrong on its side ...
It's more experience than habit, and there's also a lot of "internet" in between you and the server, which can be the cause of failures (that are hard to analyze and remedy).
That said, 3.133.76.19 really is a repeat offender and should be looked at.
It used to not have a collection server iirc, now it has one but it's "not connected" according to
https://apps.foldingathome.org/serverstats.
Re: 3.133.76.19
Posted: Sun May 24, 2020 3:52 pm
by G3WGV
I turned off the firewall exception but then enjoyed something of a charmed existence for most of today, getting allocated to other WSs. Eventually my luck ran out and I got a big job (94MB upload) from our errant WS. After 25 minutes of failed attempts it sluggishly uploaded and... success! Server responded WORK_ACK (400).
The problems with this WS are well known and have existed for a considerable time. It seems a bit pointless (creditless?) expending GPU work and electricity on WUs that cannot be uploaded in a timely fashion. Can't something be done about it?
Re: 3.133.76.19
Posted: Sun May 24, 2020 5:06 pm
by TPL
I've had many WUs from 3.133.76.19 and never had any problems.
Edit: checked log and in one case 3 unsuccessful cases to upload on port 8080, then successful upload on port 80.
Re: Upload Issues to 3.133.76.19:80
Posted: Mon May 25, 2020 3:53 am
by SirTj
I'm having issues as well for the past few days. Any update on this? Below are the logs.
Code: Select all
02:26:30:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:14448 run:0 clone:20 gen:19 core:0x22 unit:0x0000001e03854c135ea7b88f47788401
02:26:30:WU01:FS01:Uploading 95.13MiB to 3.133.76.19
02:26:30:WU01:FS01:Connecting to 3.133.76.19:8080
02:26:44:WU01:FS01:Upload 2.43%
02:26:44:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
Re: 3.133.76.19
Posted: Mon May 25, 2020 4:32 am
by SirTj
TPL wrote:I've had many WUs from 3.133.76.19 and never had any problems.
Edit: checked log and in one case 3 unsuccessful cases to upload on port 8080, then successful upload on port 80.
How did you specify which port to use? Mine keeps erroring out on port 8080. I'm also pretty confident my firewall rules are perfectly fine and I only have issues with this server.
Re: 3.133.76.19
Posted: Mon May 25, 2020 4:39 am
by bruce
You don't specify which port to use. FAHClient is totally responsible for the upload IP and Port. 8080 is tried first and if it fails, it reverts to 80.
This might matter if you've configured FAH to use a proxy server but that's an unusual situation for home computers.
Re: 3.133.76.19
Posted: Mon May 25, 2020 4:46 am
by bruce
Based on the frequency of reports on this forum, this is FAH's most troublesome server. I regularly file a report with the folks who manage these servers. They generally fix something and it works for a while and then before long, the troubles start again.
I don't have enough information about the specific problems to make any useful comments about how to fix it permanently.
Re: 3.133.76.19
Posted: Mon May 25, 2020 4:50 am
by SirTj
Yea, I don't have a proxy server running at home. Apparently, it keeps trying on 8080 and never switches to 80.
From the logs, it does seems like the server is dropping my connection after receiving the initial upload. I also notices that the server was recently restarted with the uptime being only 3 hours. It's still having errors receiving my upload.
Any idea what I should do next?
BTW, my local PC time is 04:49.
Code: Select all
*********************** Log Started 2020-05-25T04:21:51Z ***********************
04:21:51:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:14448 run:0 clone:20 gen:19 core:0x22 unit:0x0000001e03854c135ea7b88f47788401
04:21:51:WU01:FS01:Uploading 95.13MiB to 3.133.76.19
04:21:51:WU01:FS01:Connecting to 3.133.76.19:8080
04:22:25:WU01:FS01:Upload 2.37%
04:22:25:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
04:22:25:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:14448 run:0 clone:20 gen:19 core:0x22 unit:0x0000001e03854c135ea7b88f47788401
04:22:25:WU01:FS01:Uploading 95.13MiB to 3.133.76.19
04:22:25:WU01:FS01:Connecting to 3.133.76.19:8080
04:24:33:WU01:FS01:Upload 2.23%
04:24:33:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
04:24:33:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:14448 run:0 clone:20 gen:19 core:0x22 unit:0x0000001e03854c135ea7b88f47788401
04:24:33:WU01:FS01:Uploading 95.13MiB to 3.133.76.19
04:24:33:WU01:FS01:Connecting to 3.133.76.19:8080
04:25:06:WU01:FS01:Upload 2.23%
04:25:06:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
04:26:10:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:14448 run:0 clone:20 gen:19 core:0x22 unit:0x0000001e03854c135ea7b88f47788401
04:26:10:WU01:FS01:Uploading 95.13MiB to 3.133.76.19
04:26:10:WU01:FS01:Connecting to 3.133.76.19:8080
04:26:14:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
04:28:47:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:14448 run:0 clone:20 gen:19 core:0x22 unit:0x0000001e03854c135ea7b88f47788401
04:28:47:WU01:FS01:Uploading 95.13MiB to 3.133.76.19
04:28:47:WU01:FS01:Connecting to 3.133.76.19:8080
04:29:23:WU01:FS01:Upload 2.43%
04:29:23:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
04:33:02:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:14448 run:0 clone:20 gen:19 core:0x22 unit:0x0000001e03854c135ea7b88f47788401
04:33:02:WU01:FS01:Uploading 95.13MiB to 3.133.76.19
04:33:02:WU01:FS01:Connecting to 3.133.76.19:8080
04:33:38:WU01:FS01:Upload 2.30%
04:33:38:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
04:39:53:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:14448 run:0 clone:20 gen:19 core:0x22 unit:0x0000001e03854c135ea7b88f47788401
04:39:53:WU01:FS01:Uploading 95.13MiB to 3.133.76.19
04:39:53:WU01:FS01:Connecting to 3.133.76.19:8080
04:40:00:WU01:FS01:Upload 2.30%
04:40:00:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
Re: 3.133.76.19
Posted: Mon May 25, 2020 5:03 am
by bruce
SirTj wrote:Any idea what I should do next?
BTW, my local PC time is 04:49.
Get some sleep and don't worry about it until later.
