Page 1 of 1

Several Issues including Wrong GPU detected

Posted: Mon Mar 16, 2020 12:32 pm
by Evilvonbek
Before anyone suggests "Default Installation" that won't be happening for various reasons including 2SA including a hardkey handshake on boot and also certain data being held on specific drives.

Full Install done.

Programme is installed to D: ( SSD), but not the OS Partition as that's been sectioned off to allow the machine to work better
Data is being written at 15min intervals to G: ( HDD, Full Ownership and Edit capacity for all User installed programmes, Scratch Partition with @300GB spare so plenty of space )
Programme is set to "Start Manually" due to necessity for several things on my machine to be on delayed start or manual start for the 2SA/Hardkey boot sequence to work without throwing false positives
Firewall is set to allow access when on Trusted Networks, but ask for permission when on unlisted/public networks ( this is a GREP style setting, not a FAH setting so shouldn't be stopping anything )

All Options apart from those above have been left as standard, including letting the Client decide core usage etc.

Three Problems so far, and hoping that the first is just a sign that due to folk like me finding out and signing up we've actually busted a weekend of iteration runs faster than expected.
  • 1. Showing zero WU available in over an hour of queuing/seeing lots of "Connection terminated by host server. This is pretty much my log file any time I start the Client.

    Code: Select all

    12:07:56:Trying to access database...
    12:07:56:Successfully acquired database lock
    12:07:56:Enabled folding slot 00: READY cpu:7
    12:07:56:Enabled folding slot 01: READY gpu:0:Baffin XT [Radeon RX 460]
    12:07:56:WU00:FS00:Connecting to 65.254.110.245:8080
    12:07:56:WU01:FS01:Connecting to 65.254.110.245:8080
    12:07:56:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
    12:07:56:WU00:FS00:Connecting to 18.218.241.186:80
    12:07:56:WARNING:WU01:FS01:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
    12:07:57:WU01:FS01:Connecting to 18.218.241.186:80
    12:07:57:WARNING:WU01:FS01:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
    12:07:57:ERROR:WU01:FS01:Exception: Could not get an assignment
    12:07:57:WU00:FS00:Assigned to work server 128.252.203.9
    12:07:57:WU00:FS00:Requesting new work unit for slot 00: READY cpu:7 from 128.252.203.9
    12:07:57:WU00:FS00:Connecting to 128.252.203.9:8080
    12:07:57:WU01:FS01:Connecting to 65.254.110.245:8080
    12:07:57:WU01:FS01:Assigned to work server 140.163.4.231
    12:07:57:WU01:FS01:Requesting new work unit for slot 01: READY gpu:0:Baffin XT [Radeon RX 460] from 140.163.4.231
    12:07:57:WU01:FS01:Connecting to 140.163.4.231:8080
    12:08:02:ERROR:WU00:FS00:Exception: Server did not assign work unit
    12:08:02:WU00:FS00:Connecting to 65.254.110.245:8080
    12:08:02:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
    12:08:02:WU00:FS00:Connecting to 18.218.241.186:80
    12:08:02:WARNING:WU00:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
    12:08:02:ERROR:WU00:FS00:Exception: Could not get an assignment
    12:08:18:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
    12:08:18:WU01:FS01:Connecting to 140.163.4.231:80
    12:08:39:ERROR:WU01:FS01:Exception: Failed to connect to 140.163.4.231:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
    12:08:57:WU01:FS01:Connecting to 65.254.110.245:8080
    12:08:58:WU01:FS01:Assigned to work server 140.163.4.231
    12:08:58:WU01:FS01:Requesting new work unit for slot 01: READY gpu:0:Baffin XT [Radeon RX 460] from 140.163.4.231
    12:08:58:WU01:FS01:Connecting to 140.163.4.231:8080
    12:09:02:WU00:FS00:Connecting to 65.254.110.245:8080
    12:09:02:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
    12:09:02:WU00:FS00:Connecting to 18.218.241.186:80
    12:09:03:WARNING:WU00:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
    12:09:03:ERROR:WU00:FS00:Exception: Could not get an assignment
    12:09:19:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
    12:10:34:WU01:FS01:Connecting to 65.254.110.245:8080
    12:10:35:WARNING:WU01:FS01:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
    12:10:35:WU01:FS01:Connecting to 18.218.241.186:80
    12:10:35:WARNING:WU01:FS01:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
    12:10:35:ERROR:WU01:FS01:Exception: Could not get an assignment
    2. Client is wrongly showing GPU as a RX460, GPU is a RX560X. Much more powerful and has additional cores, threads and onboard RAM than the one the client thinks is there.

    3. Whether Client is active or not the page for client(dot)foldingathome(dot)org/ will not load stable,and constantly crashes and reloads itself with zero ability to actually do anything via it. Thankfully I can actually use a Console. :lol:
Hopefully I'm right on the first one, and someone can help with the other two as I might as well get the machine doing something while I'm on downtime from work and playing the PS4.

Re: Several Issues including Wrong GPU detected

Posted: Thu Mar 19, 2020 1:43 am
by Paragon
The first problem is just the overloaded F@H servers and lack of work units due to the tons of new donors. I've got a bunch of machines that dried up. The second one is likely not an issue...the names in the GPU list correspond to the hardware IDs, which are sometimes reused by AMD and NVIDIA. For example, the RX 460 and RX 560 are both based on the Baffin XT chip

https://www.techpowerup.com/gpu-specs/amd-baffin.g796

Likely what happened is when they wrote the list for the Baffin XT, the 460 was the only GPU out using that at the time. When the 560 came out (a modest improvement but based on the same architecture), no one updated the list names. They didn't have to, since the hardware ID covers both GPUs so it will fold. On my linux client with RX 580s, it says "Ellesmere XT Rx 470 / 480 / 570/ 580". I used to have RX 480s, and it said the exact same thing (although the folding performance of the 580s was in fact much faster than the 480s). I expect you'll see the same thing happen once they get work units flowing.

Not sure what is going on with the third issue. Perhaps also due to server overload from all the new donors.

Re: Several Issues including Wrong GPU detected

Posted: Thu Mar 19, 2020 4:54 am
by Joe_H
3 - is a known issue with Google Chrome since an update a few months ago. It also affects some recent versions of browsers based on Chromium.

Workarounds have been posted, in no particular order:

Use Incognito mode

clear the cache

Use the dev tools accessed by pressing F12 and turn off caching

Or you can use another browser, for example MS Edge and Firefox have been reported to work.