Could not get an assignment

[beer]

hi
I thing that there is a problem with getting CPU WU:
04:26:55:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
04:26:55:WU00:FS00:Connecting to 171.64.65.35:80
04:26:56:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
04:26:56:ERROR:WU00:FS00:Exception: Could not get an assignment
04:26:56:WU00:FS00:Connecting to 171.67.108.45:8080
04:26:57:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
04:26:57:WU00:FS00:Connecting to 171.64.65.35:80
04:26:58:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
04:26:58:ERROR:WU00:FS00:Exception: Could not get an assignment

The funny part is that I can still receive GPU WU without any problem.

Any suggestions?

[foldy]

I guess you have a 4 core/8 threads cpu and one thread is reserved to support GPU so you are left with 7 threads for CPU which is an evil number. You need to configure your CPU slot to use 6 threads.

[JimboPalmer]

To generalize, multiples of 2,3,and/or 5 work. Prime numbers greater than 5 do not work as factors.

[beer]

Hi
The setting was -1 (autodetected) and the system then selected 7. It used to work in the past and I have not payed attention to this so I dont know if I was normally getting cores to CPU=7 or the autodetection has changed it to 7. But after manual set it to 6 then I am back with my CPU as well. Thanks for the input. I would never have tought about that as the problem

[JimboPalmer]

The Work Units are getting pickier, so fewer and fewer WUs allow large prime number factors.

At the same time newer clients better set the defaults so an assignment can be found. 7.4.15 is available, but now that you set it to 6, not needed.