Cient restart required to get next Work Unit (WU)

[p_meyer]

Hi:

I am aware that due to high demand WU are not always available and the client polls the server in increasing exponential waits.

I did notice however that if I restart the client, I almost immediately receive a new WU and my client proceeds.

I am running on linux and can provide logs showing events leading right up to my manual restart of the client.

Peter

[jonault]

You can achieve the same result by pausing & unpausing the client. The only time you should have to restart the client is if you make a change to the configuration file.

[beerhoff]

Hi:

I am aware that due to high demand WU are not always available and the client polls the server in increasing exponential waits.

I did notice however that if I restart the client, I almost immediately receive a new WU and my client proceeds.

I am running on linux and can provide logs showing events leading right up to my manual restart of the client.

Peter

Same thing, but for Windows 10
Pausing doesn't have same effect in my case

[p_meyer]

Hi:

I didn't want add all of the logs. This one shows a WU completing and then it going into a polling mode. Yes most can't get a WU, but I do occasionally see a service error (log marked in bold). Go to the bottom of the logs.

17:24:06:WU01:FS01:Connecting to 155.247.164.214:8080
17:24:16:WU01:FS01:Upload complete
17:24:16:WU01:FS01:Server responded WORK_ACK (400)
17:24:16:WU01:FS01:Final credit estimate, 3271.00 points
17:24:16:WU01:FS01:Cleaning up
17:24:39:WU00:FS01:Connecting to 65.254.110.245:8080
ESC[93m17:24:39:WARNING:WU00:FS01:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configurat
ionESC[0m
<snip>
18:39:13:WU00:FS01:Connecting to 18.218.241.186:80
ESC[93m18:39:14:WARNING:WU00:FS01:Failed to get assignment from '18.218.241.186:80': No WUs available for this configurationESC[0m
ESC[91m18:39:14:ERROR:WU00:FS01:Exception: Could not get an assignmentESC[0m
18:43:28:WU00:FS01:Connecting to 65.254.110.245:8080
18:43:28:WU00:FS01:Assigned to work server 155.247.166.219
18:43:28:WU00:FS01:Requesting new work unit for slot 01: READY cpu:12 from 155.247.166.219
18:43:28:WU00:FS01:Connecting to 155.247.166.219:8080
ESC[91m18:43:28:ERROR:WU00:FS01:Exception: 10001: Server responded: HTTP_SERVICE_UNAVAILABLEESC[0m
18:50:19:WU00:FS01:Connecting to 65.254.110.245:8080
ESC[93m18:50:19:WARNING:WU00:FS01:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configurationESC[0m
18:50:19:WU00:FS01:Connecting to 18.218.241.186:80
ESC[93m18:50:19:WARNING:WU00:FS01:Failed to get assignment from '18.218.241.186:80': No WUs available for this configurationESC[0m
ESC[91m18:50:19:ERROR:WU00:FS01:Exception: Could not get an assignmentESC[0m
(

[bruce]

The SERVICE_UNAVAIL message is an indication that there is a server somewhere that is down for maintenance of some kind.
(The Assignment Server hasn't yet figured out that it's down and the last status update indicated that it could supply your with a new WU. Inter-server polling isn't always instantaneous.)

[p_meyer]

Also:

19:48:24:WU00:FS01:Connecting to 18.218.241.186:80
19:48:24:WU00:FS01:Assigned to work server 40.114.52.201
19:48:24:WU00:FS01:Requesting new work unit for slot 01: READY cpu:12 from 40.114.52.201
19:48:24:WU00:FS01:Connecting to 40.114.52.201:8080
ESC[91m19:49:12:ERROR:WU00:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0ESC[0m
19:49:28:FS01:Paused
19:49:31:FS01:Unpaused
19:49:31:WU00:FS01:Connecting to 65.254.110.245:8080
ESC[93m19:49:31:WARNING:WU00:FS01:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configurationESC[0m
19:49:31:WU00:FS01:Connecting to 18.218.241.186:80
19:49:31:WU00:FS01:Assigned to work server 40.114.52.201
19:49:31:WU00:FS01:Requesting new work unit for slot 01: READY cpu:12 from 40.114.52.201
19:49:31:WU00:FS01:Connecting to 40.114.52.201:8080

It could also be that the server is overloaded and can't dispatch the WU.