FAH-Client 8 not working on Ubuntu Server

[calxalot]

Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket

This is expected, since you have no client running on localhost.
I'm not seeing anything unusual.

Do you know how to create an ssh tunnel to your server?
If so, you could let web control think there is a local client.

On macOS, the terminal command would be something like this, run on your local machine:

Code: Select all

ssh -f -L 7396:localhost:7396 serveruser@yourserver.local sleep 60 && open https://v8-3.foldingathome.org/

Could be different on linux.

[DoctorBob]

SSH from local Windows 10 PC:


My Machine:


My Account:


It's working!!!

Wow, that is fantastic!

I image if I kill the ssh tunnel session the laptop will stop folding.
How would I get fah-client working independently on the laptop?

[calxalot]

Yay!

It should stay running until you stop it or shutdown the server.
Getting web control to make a direct connection to the client was sufficient to make it link to your account.
Setting account-token in config.xml was supposed to be sufficient.
I've never tested it myself.

The tunnel is only needed for the direct connect.

You should now be able to access it via web control on your smartphone.

[calxalot]

There is often a shortage of work for single cpu configs.
Recently, you needed cpu 4 to get work because a server was down.

Keep an eye on ETA vs WU Deadline.
If you can't make deadlines on a machine, there is no point folding on it.

The ETA is rarely accurate until a few percent done.

[DoctorBob]

Yes, I was able to log into my Machine from my iPhone via Safari.

I did kill off the ssh tunnel session and the laptop continues to fold.
So I need to run the tunnel from my local PC (or any other PC on our LAN) after rebooting the folding laptop?

The ETA of the current WU (Project 19228) is 14 hours and the laptop is at 1% Progress. I will check the the progress and deadline in the morning (its 8:30pm here).

[calxalot]

You won't need the tunnel again except maybe if the client loses its node connection.

I have had clients occasionally disconnect (but keep folding).
If that happens, you can also just restart the client service.

Code: Select all

sudo systemctl restart fah-client

You can also make it restart its account connection with my tool lufah.
If you install it, you can use

Code: Select all

lufah . restart-account

[DoctorBob]

Keep an eye on ETA vs WU Deadline.

Yes, that is right. I had to dump the first two WU as the deadline was half the time of the ETA. The third WU gave a deadline of four days, my ETA settled down to 2 days. That WU completed successfully. I have since had to dump another WU due to a deadline being too short .

Is there a way to ensure sufficient WU deadlines using our current hardware specs?


Not sure if the following is useful...


Our folding laptop runs 24/7.

When we were running fahclient 7.6.21. I added the following in file config.xml:
<!-- Folding Slots -->
<slot id='0' type='CPU'>
<cpu-usage v='50'/>
</slot>

This allowed both CPUs to run at 50%.
I might be wrong here but two CPUs running at 50% seems a better load balance then one CPU running at 100%

Since there are no slot/cpu-usage options available in version 8 and the new web client interface settings only allow you change the number of CPUs, I was able to limit CPU usage via cgroups. In the end it was simple, just add "CPUQuota=100%" to file fah-client.service, right after line:
ExecStart=/usr/bin/fah-client...

I set the web client interface to two CPUs, added CPUQuota=100% to file: /usr/lib/systemd/system/fah-client.service, reloaded and restart the service.
~$ sudo systemctl daemon-reload
~$ sudo service fah-client restart




Two CPUs running at 50%

My thoughts on limiting the CPUs is that it will keep the laptop from being driven too hard plus keep the temperature at a reasonable level:
Core 0: +66.0°C (crit = +105.0°C)
Core 1: +57.0°C (crit = +105.0°C)

and perhaps more efficient number crunching.