Work Units not starting automatically?

[questionsquestions]

When a work unit has been completed, it doesn't automatically start a new one. So, I have to pause and click "Fold All" to get it to work. Why is this? I want to be running this 24/7 but this issue prevents that from happening.

Should I downgrade back to v7?

[muziqaz]

It should automatically continue folding. Are you sure you are completing your work units successfully and not just dumping work after failing multiple times? Jn this particular case client will pause the work if device keeps failing

[questionsquestions]

It should automatically continue folding. Are you sure you are completing your work units successfully and not just dumping work after failing multiple times? Jn this particular case client will pause the work if device keeps failing

Thanks for the reply.

I'm pretty sure they're completing correctly. I've got:
410,827 points by contributing 11 work units

On stats page.

When completing they update with a star within the web interface. It does it on two different machines that I have. When I installed 8.4 I think I recall having "auto start" ticked on the installation but I think thats referencing whether the program auto starts on the machine being booted rather than auto starting new work units.

I've read that v7 had an advanced section where you could tinker a few things but 8.4 seems to have nothing of the sort. There's a padlock within the settings which I clicked but that doesn't yield any relevant settings it seems.

[muziqaz]

V8 has advanced section too.
Check the logs for any anomalies. V8 has log section in the web UI with searchable and filtering features

[toTOW]

Which version of the client did you install ?

Could you post some logs ?

[malkie]

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:

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

3. If I click "Pause All", followed by "Pause", followed by "Fold All", the machine picks up a WU within a second or two

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

[muziqaz]

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:

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

3. If I click "Pause All", followed by "Pause", followed by "Fold All", the machine picks up a WU within a second or two

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

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]

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:

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

3. If I click "Pause All", followed by "Pause", followed by "Fold All", the machine picks up a WU within a second or two

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

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.

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 sometimes ), but found work right away after the procedure I described.

[muziqaz]

When you pause struggling device, it resets the delay counter. So that's why it picks up WU straight away

[malkie]

When you pause struggling device, it resets the delay counter. So that's why it picks up WU straight away

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

[muziqaz]

When you pause struggling device, it resets the delay counter. So that's why it picks up WU straight away

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

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.
I hope that clarified the issue

[malkie]

When you pause struggling device, it resets the delay counter. So that's why it picks up WU straight away

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

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.
I hope that clarified the issue

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.

Thanks again - especially for your patience. It can't be easy dealing with users with such a wide range of technical abilities.

[muziqaz]

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

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.
I hope that clarified the issue

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.

Thanks again - especially for your patience. It can't be easy dealing with users with such a wide range of technical abilities.

no need to apologise