Upate: Service still fails to start but I just ran FAHClient manually again and it connected and is now processing a job apparently, so must have been a tempor

Upate: Service still fails to start but I just ran FAHClient manually again and it connected and is now processing a job apparently, so must have been a temporary glitch. Cores and GPUs at full throttle according to htop. Don't see anything indicating whether what it's doing is related to COVID-19, so blindly hoping it's helping with something, but I'll leave it on. (Says: "project 14307"??) ---- original post ------ I was just trying to get it running on Ubuntu 18.04 in response to this post but I'm just getting a lot of errors with not very useful error messages. Any ideas? When I run FAHClient manually I get, 21:04:10:WARNING:WU01:FS01:Failed to get assignment from 'X.X.X.X:8080': No WUs available for this configuration (I replaced the IP address with Xs) When I try starting the service I get an error and journalctl -xe gives me, e.g., (unedited, it actually says "result is RESULT") -- Unit FAHClient.service has begun starting up. Mar 14 22:02:27 poole FAHClient[17956]: Starting fahclient ... FAIL Mar 14 22:02:27 poole systemd[1]: FAHClient.service: Control process exited, code=exited st Mar 14 22:02:27 poole systemd[1]: FAHClient.service: Failed with result 'exit-code'. Mar 14 22:02:27 poole systemd[1]: Failed to start LSB: Folding@home Client. -- Subject: Unit FAHClient.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support http://www.ubuntu.com/support -- -- Unit FAHClient.service has failed. -- -- The result is RESULT.