Folding Forum

I just blew 20 minutes writing a detailed report here about installing FAHControl on two Mac Minis and getting nothing but "No WUs available." As I was just about ready to submit it, both instances started processing... after nearly two hours of failing to start! I was positive I had screwed something up in the configuration and needed assistance. I had no idea a working configuration would take that long to begin!

Anyway, I'm happy a a clam that the major issue solved itself. Now I only need to get the two smaller issues addressed.

First, on both machines (Mac Mini 2018 and Mac Mini mid-2011) I attempted to add a GPU folding slot, using the -1 default. Both times, I got: "On client local 127.0.0.1/36330: No available GPUs." Checked the forum for supported GPUs and it looks like the one on the 2018 (0x3e9b) at least is fully supported, so I must have some other problem. There's only one GPU in each device, and it's running the screen, but I'm assuming that must not be a deal-breaker.

Second, on the the 2018 mini, I tried to add the 2011 client to its client list. It added, but is permanently stuck in orange "Connecting" state (image). Same if I try to add the 2018 to the 2011's client list. Netstat shows port 36330 on the 2011 as ESTABLISHED. I'm using the same (default) port on both devices, but I wouldn't think that would be a problem. There's definitely no firewall between LAN devices.

What other info do I need to provide you in order for you to give me a hand getting this up and running? Thanks for your time.

Hi libertyhaven, welcome to Folding and to this forum!

1. The current version of the Folding software does not support GPUs on MacOS. See https://foldingathome.org/support/faq/i ... uirements/

I'm not familiar with FAHControl and adding remote clients. Hopefully, someone else who's familiar with this can answer. In the meantime, have you tried replacing the hostname with the IP? Also, I believe you will need to restart both clients (local and remote) after you make any changes.

Folding@home's userbase has increased about 10x over the past several weeks, which has flooded the servers under the load and exhausted workunits faster than they can be generated. When the queue is empty, the server says "No WUs available for this configuration". The research teams are rapidly setting up new servers and getting more projects into the queue, including for the Wuhan Coronavirus, so hopefully that can keep up with demand soon. In the meantime, keep everything running and the software should pick up workunits when they are available.

Another person posted what looks like a good step by step description of how to set up remote access, I will give a link to that - viewtopic.php?f=16&t=32962&p=316215&hilit=remote+access#p316067. As mentioned a couple posts up, after making the changes you do need to restart each client, most easily done by a reboot.

Due to the press of other tasks, I didn't get around to following up on this until today. I found that all the problems I reported had shaken themselves out with no intervention, possibly due to a couple reboots that occurred as part of the reinitialization of system backups. So, every part of this is running fine now (other than long stretches of "No WU available" which I understand are not problems at my end).

Thank all of you for your help.