Upload Issues to 3.133.76.19:80

Moderators: Site Moderators, FAHC Science Team

Re: 3.133.76.19

Postby PantherX » Sun May 24, 2020 12:47 am

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
ETA:
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time

Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
User avatar
PantherX
Site Moderator
 
Posts: 6591
Joined: Wed Dec 23, 2009 10:33 am
Location: Land Of The Long White Cloud

Re: Upload Issues to 3.133.76.19:80

Postby Juggy » Sun May 24, 2020 4:57 am

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.
Image
Image
Juggy
 
Posts: 102
Joined: Fri Mar 20, 2020 1:07 pm
Location: Qatar

Re: 3.133.76.19

Postby G3WGV » Sun May 24, 2020 9:22 am

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!
Radio Amateur, light aircraft owner/pilot, computer nerd, mountaineer, organist (sort of) and, now, folder.
User avatar
G3WGV
 
Posts: 61
Joined: Sun Mar 22, 2020 11:52 pm
Location: Near Penrith, Cumbria, UK

Re: 3.133.76.19

Postby bumbel123 » Sun May 24, 2020 10:23 am

@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 ...
  • Ryzen 3 3100 (Zen2), Nv GTX 1660 Ti, Win10 Ent
  • Ryzen 5 3600 (Zen2), Nv RTX 2060, Win10 Ent
  • Ryzen 7 2700 (Zen+), Nv RTX 2060, Nv GTX 1660, Ubuntu LTS 20.04
  • Ryzen 5 3600 (Zen2), Nv RTX 2060, Nv GTX 1650, Ubuntu LTS 20.04
bumbel123
 
Posts: 30
Joined: Fri Mar 20, 2020 1:17 pm

Re: Upload Issues to 3.133.76.19:80

Postby Juggy » Sun May 24, 2020 2:10 pm

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
Juggy
 
Posts: 102
Joined: Fri Mar 20, 2020 1:07 pm
Location: Qatar

Re: 3.133.76.19

Postby Joe_H » Sun May 24, 2020 3:46 pm

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.
Image

iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
Joe_H
Site Admin
 
Posts: 6540
Joined: Tue Apr 21, 2009 5:41 pm
Location: W. MA

Re: 3.133.76.19

Postby uyaem » Sun May 24, 2020 4:12 pm

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.
Image
CPU: Ryzen 9 3900X (1x21 CPUs) ~ GPU: nVidia GeForce GTX 1660 Super (Asus)
uyaem
 
Posts: 222
Joined: Sat Mar 21, 2020 8:35 pm
Location: Esslingen, Germany

Re: 3.133.76.19

Postby G3WGV » Sun May 24, 2020 4:52 pm

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?
User avatar
G3WGV
 
Posts: 61
Joined: Sun Mar 22, 2020 11:52 pm
Location: Near Penrith, Cumbria, UK

Re: 3.133.76.19

Postby TPL » Sun May 24, 2020 6:06 pm

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.
TPL
 
Posts: 99
Joined: Sun Apr 19, 2020 12:37 pm

Re: Upload Issues to 3.133.76.19:80

Postby SirTj » Mon May 25, 2020 4:53 am

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
SirTj
 
Posts: 5
Joined: Mon May 25, 2020 4:46 am

Re: 3.133.76.19

Postby SirTj » Mon May 25, 2020 5:32 am

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.
SirTj
 
Posts: 5
Joined: Mon May 25, 2020 4:46 am

Re: 3.133.76.19

Postby bruce » Mon May 25, 2020 5:39 am

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.
bruce
 
Posts: 19844
Joined: Thu Nov 29, 2007 11:13 pm
Location: So. Cal.

Re: 3.133.76.19

Postby bruce » Mon May 25, 2020 5:46 am

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.
bruce
 
Posts: 19844
Joined: Thu Nov 29, 2007 11:13 pm
Location: So. Cal.

Re: 3.133.76.19

Postby SirTj » Mon May 25, 2020 5:50 am

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
SirTj
 
Posts: 5
Joined: Mon May 25, 2020 4:46 am

Re: 3.133.76.19

Postby bruce » Mon May 25, 2020 6:03 am

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. :mrgreen:
bruce
 
Posts: 19844
Joined: Thu Nov 29, 2007 11:13 pm
Location: So. Cal.

PreviousNext

Return to Issues with a specific server

Who is online

Users browsing this forum: No registered users and 0 guests

cron