Folding Forum

*********************** Log Started 2022-11-01T05:52:53Z ***********************
05:52:53:WARNING:FS01:Disabling beta GPU slot 01: gpu:5:0. Beta GPUs can be tested for no points by setting ``gpu-beta=true`` in the configuration.
05:52:53:WU01:FS01:Sending unit results: id:01 state:SEND error:DUMPED project:18500 run:1 clone:12 gen:349 core:0x22 unit:0x0000000c0000015d0000484400000001
05:52:53:WU01:FS01:Connecting to 140.163.4.200:8080
05:52:53:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
05:52:53:WU01:FS01:Connecting to 140.163.4.200:80
05:52:54:WARNING:WU01:FS01:Exception: Failed to send results to work server: Failed to connect to 140.163.4.200:80: Network is unreachable
05:52:54:WU01:FS01:Trying to send results to collection server
05:52:54:WU01:FS01:Connecting to 54.157.202.86:8080
05:52:54:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
05:52:54:WU01:FS01:Connecting to 54.157.202.86:80
05:52:55:ERROR:WU01:FS01:Exception: Failed to connect to 54.157.202.86:80: Network is unreachable
05:52:55:WU01:FS01:Sending unit results: id:01 state:SEND error:DUMPED project:18500 run:1 clone:12 gen:349 core:0x22 unit:0x0000000c0000015d0000484400000001
05:52:55:WU01:FS01:Connecting to 140.163.4.200:8080
05:52:55:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
05:52:55:WU01:FS01:Connecting to 140.163.4.200:80
05:52:56:WARNING:WU01:FS01:Exception: Failed to send results to work server: Failed to connect to 140.163.4.200:80: Network is unreachable
05:52:56:WU01:FS01:Trying to send results to collection server
05:52:56:WU01:FS01:Connecting to 54.157.202.86:8080
05:52:56:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
05:52:56:WU01:FS01:Connecting to 54.157.202.86:80
05:52:56:ERROR:WU01:FS01:Exception: Failed to connect to 54.157.202.86:80: Network is unreachable
05:53:55:WU01:FS01:Sending unit results: id:01 state:SEND error:DUMPED project:18500 run:1 clone:12 gen:349 core:0x22 unit:0x0000000c0000015d0000484400000001
05:53:55:WU01:FS01:Connecting to 140.163.4.200:8080
05:53:56:WU01:FS01:Server responded WORK_ACK (400)
05:53:56:WU01:FS01:Cleaning up

EDIT1: A reboot did not fix it. I am not getting any new GPU work units.
But the machine is Folding OK on the CPU, though it hasn't asked for new work recently.

EDIT 2: I can get to both work servers with my web browser.

This looks like a client startup at boot after an update of GPU drivers or something like this ...

First, the client failed to check GPU compatibility (or to download an update to GPUs.txt file) and disabled the GPU slot. Then it tried to report the dumped WU and failed because the network wasn't enabled/connected. It finally reported the dumped WU probably because the network was connected after a while.

Make sure your network is connected and available before starting FAHClient.

I was wondering if it were something local. It looks like a strange way for the server to fail.
But the network is OK, and the card (GTX 1070) is OK for display purposes. I have done all the updates, and nothing fixed it.
Maybe a re-installation of the OS or just the Folding Control will fix it, or else something hidden is wrong with the card.

Thanks for your input.

Check to see if you have a full copy of GPUs.txt. On my system it is about 105 KB in size, interrupted downloads of an update to that have been reported leaving behind a truncated or empty file.

I uninstalled FAH and tried to re-install it (I use the Python 3 version). It would not allow configuration after install.
Then I tried the SNAP version on Ubuntu Software Center. That would not work either even for the CPU, so I could not get to GPU.txt.

I think the OS has something wrong with it. If that does not work, I have a spare card to try.
Thanks.

This is interesting. I finally got it to Fold on both the CPU and GPU after a re-install of Ubuntu 20.04.5.
But even then, it would fold only on the CPU, and I could not get the GUI visible at all.

Finally, I added the OpenCl drivers: sudo apt install ocl-icd-opencl-dev
That fixed it. It is not normally necessary, but I am using the latest Nvidia drivers (520) and maybe they left it out.
However, it worked fine on those drivers for a couple of weeks before it decided to quit.