Community driven support forum for Folding@home
https://foldingforum.org/
Thanks for the reply.
Code: Select all
04:56:26:I1:WU644:Requesting WU assignment for user Malkie team 0
04:56:26:I1:OUT191:> POST https://assign4.foldingathome.org/api/assign HTTP/1.1
04:56:26:I1:OUT191:< HTTP/1.1 503 HTTP_SERVICE_UNAVAILABLE
04:56:26:E :OUT191:HTTP_SERVICE_UNAVAILABLE: {"error":"No appropriate assignment"}
04:56:26:I1:WU644:Retry #5 in 32 secs
Your issue is related to lack of work on the servers. If you check your log which you posted here it says: no appropriate assignment.malkie wrote: ↑Fri Oct 24, 2025 5:10 am I'm finding the same thing on my Windows 11 machine, starting about a week ago. The two Windows 10 machines seem to be just fine.
In detail:
1. WU completes
2. Progress bar is red, and log fills up with a series of messages:3. If I click "Pause All", followed by "Pause", followed by "Fold All", the machine picks up a WU within a second or twoCode: Select all
04:56:26:I1:WU644:Requesting WU assignment for user Malkie team 0 04:56:26:I1:OUT191:> POST https://assign4.foldingathome.org/api/assign HTTP/1.1 04:56:26:I1:OUT191:< HTTP/1.1 503 HTTP_SERVICE_UNAVAILABLE 04:56:26:E :OUT191:HTTP_SERVICE_UNAVAILABLE: {"error":"No appropriate assignment"} 04:56:26:I1:WU644:Retry #5 in 32 secs
Like questionsquestions, I regret the loss of progress between the completion of a WU and my noticing and fixing the problem. Because I keep an eye on the ETA, I can usually minimise the down time.
However, I need full productivity from my Win11 machine. How else will I reach the top of the leader board from my current position at #122,645
Is it just coincidence that every time I go through the "Pause All", followed by "Pause", followed by "Fold All", the machine finds a WU almost immediately, and that the Win10 machines are not having the same issue? On one occasion the Win11 machine was idle for several hours (I have to sleep sometimesmuziqaz wrote: ↑Fri Oct 24, 2025 5:48 amYour issue is related to lack of work on the servers. If you check your log which you posted here it says: no appropriate assignment.malkie wrote: ↑Fri Oct 24, 2025 5:10 am I'm finding the same thing on my Windows 11 machine, starting about a week ago. The two Windows 10 machines seem to be just fine.
In detail:
1. WU completes
2. Progress bar is red, and log fills up with a series of messages:3. If I click "Pause All", followed by "Pause", followed by "Fold All", the machine picks up a WU within a second or twoCode: Select all
04:56:26:I1:WU644:Requesting WU assignment for user Malkie team 0 04:56:26:I1:OUT191:> POST https://assign4.foldingathome.org/api/assign HTTP/1.1 04:56:26:I1:OUT191:< HTTP/1.1 503 HTTP_SERVICE_UNAVAILABLE 04:56:26:E :OUT191:HTTP_SERVICE_UNAVAILABLE: {"error":"No appropriate assignment"} 04:56:26:I1:WU644:Retry #5 in 32 secs
Like questionsquestions, I regret the loss of progress between the completion of a WU and my noticing and fixing the problem. Because I keep an eye on the ETA, I can usually minimise the down time.
However, I need full productivity from my Win11 machine. How else will I reach the top of the leader board from my current position at #122,645
), but found work right away after the procedure I described.I don't know what you mean by "struggling". This machine was doing just fine, picking up WUs just like my lower-powered (in CPU terms) Win 10 machines, until a week or so ago - about the same time that questionsquestions posted the OP in this thread.
Your machine is struggling to get work. When machine cannot find work, it tries and re-tries to get work. When it again fails, it continues doing so. To stop that machine from hammering servers, there is retry timer implemented, which increases with every new attempt. So between 1st and 2nd attempts you will have 1s waiting time. From 2nd to 3rd retry, that period will increase to let's say 5s. Next attempt will be in 10s, etc, etc. So if your machine has been struggling to get work for an hour, retry period might be in 10s of minutes. So even though you might think that client tries non stop to get work, it doesn't it might be in that waiting period. When You pause your client, that waiting period resets to 1s. So when you resume paused client which was struggling to get work before (or most likely was sleeping, waiting for the timer to expire), it will immediately try getting work, and since WU shortages are relatively rare, and no available work is momentary, you will most likely receive work immediately after pause/unpause.malkie wrote: ↑Fri Oct 24, 2025 5:56 pmI don't know what you mean by "struggling". This machine was doing just fine, picking up WUs just like my lower-powered (in CPU terms) Win 10 machines, until a week or so ago - about the same time that questionsquestions posted the OP in this thread.
Anyway, not a tragedy. I'm now at position #122,588, so still slowly catching up
Thanks - yes, it does clarify the issue. I guess the Win10 machines are just lucky that when they finish a WU there is always one "waiting" for them. All three machines are currently set to offer three CPUs - 3 of 8 for the Win11 machine, and 3 of 4 for each of the Win10 machines.muziqaz wrote: ↑Fri Oct 24, 2025 6:47 pmYour machine is struggling to get work. When machine cannot find work, it tries and re-tries to get work. When it again fails, it continues doing so. To stop that machine from hammering servers, there is retry timer implemented, which increases with every new attempt. So between 1st and 2nd attempts you will have 1s waiting time. From 2nd to 3rd retry, that period will increase to let's say 5s. Next attempt will be in 10s, etc, etc. So if your machine has been struggling to get work for an hour, retry period might be in 10s of minutes. So even though you might think that client tries non stop to get work, it doesn't it might be in that waiting period. When You pause your client, that waiting period resets to 1s. So when you resume paused client which was struggling to get work before (or most likely was sleeping, waiting for the timer to expire), it will immediately try getting work, and since WU shortages are relatively rare, and no available work is momentary, you will most likely receive work immediately after pause/unpause.malkie wrote: ↑Fri Oct 24, 2025 5:56 pmI don't know what you mean by "struggling". This machine was doing just fine, picking up WUs just like my lower-powered (in CPU terms) Win 10 machines, until a week or so ago - about the same time that questionsquestions posted the OP in this thread.
Anyway, not a tragedy. I'm now at position #122,588, so still slowly catching up
I hope that clarified the issue
no need to apologisemalkie wrote: ↑Fri Oct 24, 2025 7:20 pmThanks - yes, it does clarify the issue. I guess the Win10 machines are just lucky that when they finish a WU there is always one "waiting" for them. All three machines are currently set to offer three CPUs - 3 of 8 for the Win11 machine, and 3 of 4 for each of the Win10 machines.muziqaz wrote: ↑Fri Oct 24, 2025 6:47 pmYour machine is struggling to get work. When machine cannot find work, it tries and re-tries to get work. When it again fails, it continues doing so. To stop that machine from hammering servers, there is retry timer implemented, which increases with every new attempt. So between 1st and 2nd attempts you will have 1s waiting time. From 2nd to 3rd retry, that period will increase to let's say 5s. Next attempt will be in 10s, etc, etc. So if your machine has been struggling to get work for an hour, retry period might be in 10s of minutes. So even though you might think that client tries non stop to get work, it doesn't it might be in that waiting period. When You pause your client, that waiting period resets to 1s. So when you resume paused client which was struggling to get work before (or most likely was sleeping, waiting for the timer to expire), it will immediately try getting work, and since WU shortages are relatively rare, and no available work is momentary, you will most likely receive work immediately after pause/unpause.malkie wrote: ↑Fri Oct 24, 2025 5:56 pm
I don't know what you mean by "struggling". This machine was doing just fine, picking up WUs just like my lower-powered (in CPU terms) Win 10 machines, until a week or so ago - about the same time that questionsquestions posted the OP in this thread.
Anyway, not a tragedy. I'm now at position #122,588, so still slowly catching up
I hope that clarified the issue
Thanks again - especially for your patience. It can't be easy dealing with users with such a wide range of technical abilities.