Page 1 of 1

Transfer Error When Sending Results

PostPosted: Tue Mar 17, 2020 1:33 pm
by BPHusker
I seem to be having trouble sending a GPU WU that completed last night. I let it sit for over an hour last night and it never completed and I am seeing the same error this morning. Any ideas as to what the problem is? I have allowed the program on Windows Defender and MalwareBytes. Downloading seems to work just fine.

Here is the error:
Code: Select all
12:30:33:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11758 run:0 clone:3108 gen:0 core:0x22 unit:0x000000019bf7a4d55e6d7718bfc0d1c7
12:30:33:WU01:FS01:Uploading 55.25MiB to 155.247.164.213
12:30:33:WU01:FS01:Connecting to 155.247.164.213:8080
12:30:34:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
12:30:34:WU01:FS01:Trying to send results to collection server
12:30:34:WU01:FS01:Uploading 55.25MiB to 155.247.164.214
12:30:34:WU01:FS01:Connecting to 155.247.164.214:8080
12:30:35:ERROR:WU01:FS01:Exception: Transfer failed
12:30:35:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11758 run:0 clone:3108 gen:0 core:0x22 unit:0x000000019bf7a4d55e6d7718bfc0d1c7
12:30:35:WU01:FS01:Uploading 55.25MiB to 155.247.164.213
12:30:35:WU01:FS01:Connecting to 155.247.164.213:8080
12:30:35:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
12:30:35:WU01:FS01:Trying to send results to collection server
12:30:35:WU01:FS01:Uploading 55.25MiB to 155.247.164.214
12:30:35:WU01:FS01:Connecting to 155.247.164.214:8080
12:30:36:ERROR:WU01:FS01:Exception: Transfer failed

Re: Transfer Error When Sending Results

PostPosted: Tue Mar 17, 2020 6:21 pm
by davidcoton
It looks as though a network connection cannot be made. It may be a temporary problem caused by the unprecedented load on the servers. Are other work units completing and uploading?

Re: Transfer Error When Sending Results

PostPosted: Tue Mar 17, 2020 6:42 pm
by alxbelu
I highly doubt this specific instance is a current overload issue; we have multiple cases of this in this thread: viewtopic.php?f=18&t=32492&start=15

Re: Transfer Error When Sending Results

PostPosted: Tue Mar 17, 2020 6:53 pm
by davidcoton
@alxbelu Looking at the timing this is not the same issue. We need more information as I asked to see what is happening.
Could you keep your issue to the original thread, please? It is hard enough to answer all the issues (and work out which need further investigation) without getting all the issues muddled up.

Re: Transfer Error When Sending Results

PostPosted: Thu Mar 19, 2020 7:23 am
by puuteknikko
Uploading anything bigger seems to be impossible right now. I've been trying to send a >700MB WU back for about two days now, and with the current situation, it's just not happening.

Re: Transfer Error When Sending Results

PostPosted: Thu Mar 19, 2020 2:19 pm
by CrazyRyan
I have the same problem!!
Project: 11758
Work server:155.247.164.213
Collection server:155.247.164.214


Code: Select all
12:38:58:WU02:FS01:Trying to send results to collection server
12:38:58:WU02:FS01:Uploading 55.24MiB to 155.247.164.214
12:38:58:WU02:FS01:Connecting to 155.247.164.214:8080
12:38:58:ERROR:WU02:FS01:Exception: Transfer failed

Re: Transfer Error When Sending Results

PostPosted: Thu Mar 19, 2020 4:59 pm
by davidcoton
The team are aware and are (I hop) working on the issue. It does still seem to be a consequence of server overload -- upload transfers are much bigger than downloads. Most of the refusals are immediate, so resources are not being wasted on partial transfers.
The science cannot proceed until a unit is returned, so the team are as keen as we are to see things flowing properly.

Re: Transfer Error When Sending Results

PostPosted: Thu Mar 19, 2020 7:14 pm
by Joe_H
:lol: Yes, they are working on it, not just "hop"ping.

Re: Transfer Error When Sending Results

PostPosted: Thu Mar 19, 2020 8:51 pm
by davidcoton
Joe_H wrote::lol: Yes, they are working on it, not just "hop"ping.

Sorry, I don't hop, but I think the servers are "hopping" mad at their suddenly increased workload for no extra pay. :lol: