Folding Forum

Yeah, not sure, to me it doesn't look exactly like the previous issue. The previous issues seemed to be related to large results, over 50 MiB or so, not being accepted. And this one is 8.32 MiB. Also they were usually rejected immediately, without any upload progress shown, and this one has some pro...

No issues here. Other than lack of WUs to process.

It might help to paste the relevant section from the logs, to see if it looks like the previous issue or not.

I can confirm this seems fixed. In the last few hours I received, processed, and successfully uploaded a 55.24 MiB result for project 11758. 00:29:27:WU00:FS01:0x22:Folding@home Core Shutdown: FINISHED_UNIT 00:29:28:WU00:FS01:FahCore returned: FINISHED_UNIT (100 = 0x64) 00:29:28:WU00:FS01:Sending un...

As to why the issue is apparently so hard to fix, I'm guessing the logging on the servers might be inadequate. Which wouldn't surprise me at all after seeing the poor logging on the clients. Not even logging the error information that the servers are sending them. So probably, just like the clients,...

@davidcoton has the potential configuration issue that might limit the uploaded results based on upload size been investigated? From previous replies I understand only one person is responsible for those servers, and that they are very busy and don't have enough time to investigate this. In these ti...

I have GPU unit from a 0x22 project, that currently doesn't even seem to have a description: https://apps.foldingathome.org/project?p=11776 Trying to see the description there gives me "Project unspecified". There is also no description displayed in the local web control, instead of descri...

Now we know that, unless the servers lie "to prevent cheating", the problem is most likely the result size, since they return HTTP_REQUEST_ENTITY_TOO_LARGE when attempting to upload the result. I looked through my logs from this week to try to get more insight about the problem. This is wh...

Found just the same as Whittle . Transmission ends with HTTP/1.0 413 HTTP_REQUEST_ENTITY_TOO_LARGE analyzing with wireshark. One possibility seems to be that the collector isn't able to receive a chunk of 55 Mbyte . Not very uncommon in a web server setup. Could it be that a reconfiguration to allo...

OK. As long as it's not a systemic issue, 2 stuck units here and there probably won't make much difference in the grand scheme of things.

So maybe it's not worth the effort to investigate this further.

Still can't upload my 2 GOOD WUs from 11758, getting close to 72 hours since I finished the first one. Before the last attempt I even disabled Windows Defender, the problem persisted: 15:45:41:WU02:FS01:Sending unit results: id:02 state:SEND error:NO_ERROR project:11758 run:0 clone:3900 gen:0 core:0...

The servers are struggling to accept all the work units that are being sent in. I would just leave it to continue to try and upload, you do get partial credit for a failed WU so its still worth it going back. That doesn't be to seem the case for project 11758, it looks more like some kind of config...

Yes, I'm aware of the exponential backoff feature, but it didn't seem to be the case here, since it stopped trying to get units completely, 0 attempts after finishing the previous unit, without me pausing anything (I was sleeping at the time).

As your client is actually trying to fetch new WUs, on separate streams (i.e. WU01 and WU03), I don't see any indication that the completed WUs (WU00 & WU02, both project 11758) are blocking anything - this part of the problem is that the servers/researchers are overloaded (can't dish out enoug...

I have the same problem, two results not uploading to .213 / .214 for over 24 hours. And the credit going down as the delay increases is extremely annoying. Not sure why that "feature" was implemented, but I believe it should be disabled, or at the very least made less aggressive. 11:02:13...

What exactly is the purpose of this project? I wanted to contribute to the COVID projects, and after an initial COVID work unit I got a unit from 11737 instead of COVID.