Running F@H headless and work unit requests timing out

kelvinhall05 · August 31, 2020

Hi guys. Trying to get F@H running on my desktop and my server after months of not having done any folding, but I'm running to a few problems.

My desktop is folding fine so far, but the WU requests for my GPU slot keep timing out. I've let it retry for half an hour now and it's not working so I'm assuming there is something wrong.

15:16:58:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
15:19:08:ERROR:WU01:FS01:Exception: Failed to connect to 192.0.2.1:80: Connection timed out
15:21:17:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
15:23:27:ERROR:WU01:FS01:Exception: Failed to connect to 192.0.2.1:80: Connection timed out
15:25:37:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
15:27:46:ERROR:WU01:FS01:Exception: Failed to connect to 192.0.2.1:80: Connection timed out
15:29:56:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
15:32:06:ERROR:WU01:FS01:Exception: Failed to connect to 192.0.2.1:80: Connection timed out
15:34:15:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
15:36:25:ERROR:WU01:FS01:Exception: Failed to connect to 192.0.2.1:80: Connection timed out
15:38:35:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
15:40:45:ERROR:WU01:FS01:Exception: Failed to connect to 192.0.2.1:80: Connection timed out
15:45:28:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
15:47:38:ERROR:WU01:FS01:Exception: Failed to connect to 192.0.2.1:80: Connection timed out

The other problem I'm having is with my server running Ubuntu Server. I am trying to get the client running headless and although it appears to be working fine (as evident by looking at temps, util, fan speed, and just hearing the damn thing lol) is that I am unable to connect to the web interface with my desktop. Also, when I try to start the FAHClient service, it appears to start fine but init.d says it failed. No other info, just "failed". Here is my config file:

<config>
  <!-- Folding Slot Configuration -->
  <cause v='COVID_19'/>
  <gpu v='true'/>

  <!-- Slot Control -->
  <power v='full'/>

  <!-- User Information -->
  <passkey v='[censored]'/>
  <team v='223518'/>
  <user v='kelvinhall05'/>

   <!-- Folding Slots -->
  <slot id='0' type='CPU'>
    <cpus v='12'/>
  </slot>
  <slot id='1' type='GPU'>
    <gpu-index v='0'/>
  </slot>
  <slot id='2' type='GPU'>
    <gpu-index v='1'/>
  </slot>

  <!-- Grant remote web access to the following IP -->
  <allow>192.168.0.13</allow>
  <web-allow>192.168.0.13</web-allow>
</config>

My desktop is at 192.168.0.13 yet the connection times out when I try to go to http://192.168.0.10:7396 (the IP of my server).

Any ideas? Thanks!

Parideboy · August 31, 2020

33 minutes ago, kelvinhall05 said:

My desktop is folding fine so far, but the WU requests for my GPU slot keep timing out. I've let it retry for half an hour now and it's not working so I'm assuming there is something wrong.

If it's a Linux system, it's a know bug:

https://github.com/FoldingAtHome/fah-issues/issues/1309

It's a symptom of 2 things:

No WUs available

GPU not supported

Check the GPU.txt file and search if your gpu is present.

You might also want to check that you have the latest beta version of the software, as it should have fixes for this issue.

You can grab it from here: https://foldingathome.org/beta/

As for the remote access, try changing this line as follows:

  <!-- Grant remote web access to the following IP -->
  <allow v='192.168.0.13'/>
  <web-allow>192.168.0.13</web-allow>

kelvinhall05 · August 31, 2020

11 minutes ago, Parideboy said:
If it's a Linux system, it's a know bug:

https://github.com/FoldingAtHome/fah-issues/issues/1309

It's a symptom of 2 things:

No WUs available

GPU not supported

Check the GPU.txt file and search if your gpu is present.

You might also want to check that you have the latest beta version of the software, as it should have fixes for this issue.

You can grab it from here: https://foldingathome.org/beta/

As for the remote access, try changing this line as follows:
  
  <allow v='192.168.0.13'/>
  <web-allow>192.168.0.13</web-allow>

Yes, I use Arch (btw) so I will check gpu.txt. Where do I find it?

I tried editing the config file like that and it still times out. I've also noticed this in the log for the fahclient in init.d:

16:51:02:WU02:FS01:Starting
16:51:02:ERROR:WU02:FS01:Failed to start core: OpenCL device matching slot 1 not found, make sure the OpenCL driver is installed or try setting 'opencl-index' manually
16:51:02:WU03:FS02:Starting
16:51:02:ERROR:WU03:FS02:Failed to start core: OpenCL device matching slot 2 not found, make sure the OpenCL driver is installed or try setting 'opencl-index' manually

I don't remember seeing this before I installed ocl-icd-opencl-dev. GPUs still appear to be utilized by F@H, both before and after I installed this package.

Parideboy · August 31, 2020

6 minutes ago, kelvinhall05 said:

Yes, I use Arch (btw) so I will check gpu.txt. Where do I find it?

Depends on the version of the client is installed, take a look in those directories:

/opt/fah/

/etc/foldingathome

/var/lib/foldingathome

12 minutes ago, kelvinhall05 said:

I've also noticed this in the log for the fahclient in init.d:

This is on the server, right? You're right, that error usually refers to wrong/not compatible opencl packages.

You can follow this guide to get the right packages for fah:

27 minutes ago, kelvinhall05 said:

I tried editing the config file like that and it still times out.

Edit this line aswell, and make sure to restart the client afterwards

  <!-- Grant remote web access to the following IP -->
  <allow v='192.168.0.13'/>
  <web-allow v='192.168.0.13'/>

kelvinhall05 · August 31, 2020

7 minutes ago, Parideboy said:

36 minutes ago, kelvinhall05 said:

Depends on the version of the client is installed, take a look in those directories:

/opt/fah/

/etc/foldingathome

/var/lib/foldingathome

My GPU is present there. I have also now noticed that after letting it sit for a while, I now have these errors for the GPU slot:

16:59:32:WU01:FS01:0x22:ERROR:126: Bad platformId size.
16:59:32:WARNING:WU01:FS01:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
16:59:38:WU02:FS01:0x22:ERROR:126: Bad platformId size.
16:59:38:WARNING:WU02:FS01:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
16:59:43:WU01:FS01:0x22:ERROR:126: Bad platformId size.
16:59:43:WARNING:WU01:FS01:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
16:59:48:WU02:FS01:0x22:ERROR:126: Bad platformId size.
16:59:48:WARNING:WU02:FS01:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
16:59:52:WU01:FS01:0x22:ERROR:126: Bad platformId size.
16:59:53:WARNING:WU01:FS01:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
16:59:57:WU02:FS01:0x22:ERROR:126: Bad platformId size.
16:59:57:WARNING:WU02:FS01:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
17:00:00:WARNING:WU01:FS01:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
17:00:04:WU02:FS01:0x22:ERROR:126: Bad platformId size.
17:00:05:WARNING:WU02:FS01:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
17:00:09:WU01:FS01:0x22:ERROR:126: Bad platformId size.
17:00:09:WARNING:WU01:FS01:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
17:00:13:WU02:FS01:0x22:ERROR:126: Bad platformId size.
17:00:13:WARNING:WU02:FS01:FahCore returned: BAD_WORK_UNIT (114 = 0x72)

I will check that guide out and let you know if it works and fixes the above errors (assuming they are related to OpenCL), as well as if editing the server's config file will allow me to connect with the web control. Thanks!

kelvinhall05 · August 31, 2020

@Parideboy So I've managed to get the GPU on my desktop working, thanks! However, I'm still having problems with connecting to my server. Here is the updated config:

<config>
  <!-- Folding Slot Configuration -->
  <gpu v='true'/>

  <!-- Slot Control -->
  <power v='full'/>

  <!-- User Information -->
  <passkey v='[censored]'/>
  <team v='223518'/>
  <user v='kelvinhall05'/>

  <!-- Folding Slots -->
  <slot id='0' type='CPU'>
    <cpus v='8'/>
  </slot>
  <slot id='1' type='GPU'>
    <gpu-index v='0'/>
  </slot>
  <slot id='2' type='GPU'>
    <gpu-index v='1'/>
  </slot>

  <!-- Grant remote web access to the following IP -->
  <allow v='192.168.0.13'/>
  <web-allow v='192.168.0.13'/>
</config>

Any more ideas, or at least a way to confirm that both GPUs and full CPU is folding?

Parideboy · August 31, 2020

23 minutes ago, kelvinhall05 said:

@Parideboy So I've managed to get the GPU on my desktop working, thanks! However, I'm still having problems with connecting to my server. Here is the updated config:

Any more ideas, or at least a way to confirm that both GPUs and full CPU is folding?

I'm glad you were able to find a solution.

If you have FAHControl on your desktop you can control the folding on the server, just add this to the config:

<command-allow-no-pass v='192.168.0.13'/>

From the desktop on the Control program, just press the + button, give a name to the client, put the server IP (192.168.0.10) and leave the port to 36330

If this doesn't work, try adding 127.0.0.1 to the IP ranges of the config:

  <!-- Grant remote web access to the following IP -->
  <allow v='127.0.0.1 192.168.0.13'/>
  <web-allow v='127.0.0.1 192.168.0.13'/>
  <command-allow-no-pass v='127.0.0.1 192.168.0.13'/>

kelvinhall05 · August 31, 2020

15 minutes ago, Parideboy said:
I'm glad you were able to find a solution.

If you have FAHControl on your desktop you can control the folding on the server, just add this to the config:
<command-allow-no-pass v='192.168.0.13'/>
From the desktop on the Control program, just press the + button, give a name to the client, put the server IP (192.168.0.10) and leave the port to 36330

If this doesn't work, try adding 127.0.0.1 to the IP ranges of the config:
  
  <allow v='127.0.0.1 192.168.0.13'/>
  <web-allow v='127.0.0.1 192.168.0.13'/>
  <command-allow-no-pass v='127.0.0.1 192.168.0.13'/>

The F@H client times out trying to connect, however, I noticed that with 127.0.0.1 added to the IP range, I now get an error 403 access denied when trying to access the web console for my server instead of it just timing out. Progress? lol

Parideboy · August 31, 2020

14 minutes ago, kelvinhall05 said:

The F@H client times out trying to connect, however, I noticed that with 127.0.0.1 added to the IP range, I now get an error 403 access denied when trying to access the web console for my server instead of it just timing out. Progress? lol

For the sake of troubleshooting, let's just YOLO it.

Let's give it the full range of local IPs, we can revert that later

  <!-- Grant remote web access to the following IP -->
  <allow v='127.0.0.1 192.168.0.0/24'/>
  <web-allow v='127.0.0.1 192.168.0.0/24'/>
  <command-allow-no-pass v='127.0.0.1 192.168.0.0/24'/>

PS: make sure to give it one of those:

service --status-all | grep '\[ + \]'
systemctl restart <name>

Search for the service and restart it

kelvinhall05 · August 31, 2020

25 minutes ago, Parideboy said:
For the sake of troubleshooting, let's just YOLO it.

Let's give it the full range of local IPs, we can revert that later
  
  <allow v='127.0.0.1 192.168.0.0/24'/>
  <web-allow v='127.0.0.1 192.168.0.0/24'/>
  <command-allow-no-pass v='127.0.0.1 192.168.0.0/24'/>
PS: make sure to give it one of those:
service --status-all | grep '\[ + \]'
systemctl restart <name>
Search for the service and restart it

Still get denied

I forgot to post systemctl status output in this thread so far, so here it is:

● FAHClient.service - LSB: Folding@home Client
   Loaded: loaded (/etc/init.d/FAHClient; generated)
   Active: failed (Result: exit-code) since Mon 2020-08-31 15:02:27 EDT; 48s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 2829 ExecStop=/etc/init.d/FAHClient stop (code=exited, status=0/SUCCESS)
  Process: 2853 ExecStart=/etc/init.d/FAHClient start (code=exited, status=1/FAILURE)
    Tasks: 23 (limit: 4915)
   CGroup: /system.slice/FAHClient.service
           ├─2871 /usr/bin/FAHClient /etc/fahclient/config.xml --run-as fahclient --pid-file=/var/run/fahclient.pid --daemon
           ├─2874 /usr/bin/FAHClient --child /etc/fahclient/config.xml --run-as fahclient --pid-file=/var/run/fahclient.pid --daemon
           ├─2894 /usr/bin/FAHCoreWrapper /var/lib/fahclient/cores/cores.foldingathome.org/lin/64bit-sse2/a7-0.0.19/Core_a7.fah/FahCore_a7 -dir 00 -suffix 01 -version 706 -lifeline 2874 -checkpoint 15 -np 8
           └─2898 /var/lib/fahclient/cores/cores.foldingathome.org/lin/64bit-sse2/a7-0.0.19/Core_a7.fah/FahCore_a7 -dir 00 -suffix 01 -version 706 -lifeline 2894 -checkpoint 15 -np 8

Aug 31 15:02:27 cheesegrater systemd[1]: Starting LSB: Folding@home Client...
Aug 31 15:02:27 cheesegrater FAHClient[2853]: Starting fahclient ... FAIL
Aug 31 15:02:27 cheesegrater systemd[1]: FAHClient.service: Control process exited, code=exited status=1
Aug 31 15:02:27 cheesegrater systemd[1]: FAHClient.service: Failed with result 'exit-code'.
Aug 31 15:02:27 cheesegrater systemd[1]: Failed to start LSB: Folding@home Client.
kelvin@cheesegrater:~$

I'm not sure why it's always failed to start/be active because it's very obviously running.

Parideboy · August 31, 2020

Can you by any chance reboot the system? At the very least the control through the client should work

kelvinhall05 · August 31, 2020

1 hour ago, Parideboy said:

Can you by any chance reboot the system? At the very least the control through the client should work

I have rebooted several times and always get this result.

Parideboy · August 31, 2020

42 minutes ago, kelvinhall05 said:

I have rebooted several times and always get this result.

I have a very similar config (minus the web-allow part) and I can see it in my client.

Can you post the unit file?

HaRdLy007 · September 4, 2020

 <allow v='127.0.0.1 192.168.0.0/24'/>  <command-allow-no-pass v='127.0.0.1 192.168.0.0/24'/>

Try replacing your remote access lines with the above.

The only way I can think of checking CPU/GPU usage is using top

On 8/31/2020 at 1:47 PM, kelvinhall05 said:
@Parideboy So I've managed to get the GPU on my desktop working, thanks! However, I'm still having problems with connecting to my server. Here is the updated config:
<config>
  
  <gpu v='true'/>

  
  <power v='full'/>

  
  <passkey v='[censored]'/>
  <team v='223518'/>
  <user v='kelvinhall05'/>

  
  <slot id='0' type='CPU'>
    <cpus v='8'/>
  </slot>
  <slot id='1' type='GPU'>
    <gpu-index v='0'/>
  </slot>
  <slot id='2' type='GPU'>
    <gpu-index v='1'/>
  </slot>

  
  <allow v='192.168.0.13'/>
  <web-allow v='192.168.0.13'/>
</config>
Any more ideas, or at least a way to confirm that both GPUs and full CPU is folding?

kelvinhall05 · September 7, 2020

Gonna bump this thread, have some new info.

I've now installed Arch and so far everything appears to be working better (I prefer Arch over Ubuntu so much...but anyway), however, when I try to connect with a browser to the server's IP it denies me permission. Here is my config file:

config>
  <!-- Folding Slot Configuration -->
  <cause v='COVID_19'/>
  <gpu v='false'/>

  <!-- Slot Control -->
  <power v='full'/>

  <!-- User Information -->
  <passkey v='[censored]'/>
  <team v='223518'/>
  <user v='kelvinhall05'/>

  <!-- Folding Slots -->
  <slot id='0' type='CPU'/>
    <cpus v='8'/>
  </slot>
  <slot id='1' type='GPU'/>
    <gpu-index v='0'/>
  </slot>

  <!-- Grant remote web access to the following IP -->
  <allow v='127.0.0.1 192.168.0.13'/>
  <web-allow v='127.0.0.1 192.168.0.13'/>
  <command-allow-no-pass v='127.0.0.1 192.168.0.13'/>
</config>

Any ideas?

Gorgon · September 7, 2020

1 hour ago, kelvinhall05 said:
Gonna bump this thread, have some new info.

I've now installed Arch and so far everything appears to be working better (I prefer Arch over Ubuntu so much...but anyway), however, when I try to connect with a browser to the server's IP it denies me permission. Here is my config file:
config>
  
  <cause v='COVID_19'/>
  <gpu v='false'/>

  
  <power v='full'/>

  
  <passkey v='[censored]'/>
  <team v='223518'/>
  <user v='kelvinhall05'/>

  
  <slot id='0' type='CPU'/>
    <cpus v='8'/>
  </slot>
  <slot id='1' type='GPU'/>
    <gpu-index v='0'/>
  </slot>

  
  <allow v='127.0.0.1 192.168.0.13'/>
  <web-allow v='127.0.0.1 192.168.0.13'/>
  <command-allow-no-pass v='127.0.0.1 192.168.0.13'/>
</config>
Any ideas?

<!-- HTTP Server -->
<allow v='127.0.0.1 192.168.1.0/24'/>
<!-- Remote Command Server -->
<command-allow-no-pass v='127.0.0.1 192.168.1.0/24'/>

I’ve noticed on newer flavours of Linux that you have to replace the init file (It’s broken) and make the fahclient user a member of the video group.

see:

Sign In

Running F@H headless and work unit requests timing out

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Link to comment

Share on other sites

Link to post

Share on other sites

Create an account or sign in to comment

Create an account

Sign in

Announcements

Featured Topics

Topics

Latest From Linus Tech Tips:

I shouldn’t have kept the $1,000,000 computer

Latest From Tech Quickie:

This Guy BUILT His Own Graphics Card!

Latest From TechLinked:

Microsoft, Give Up Already.

Latest From GameLinked:

Roblox and Walmart... Are One