FAHClient on headless Ubuntu Server

Moderators: Site Moderators, FAHC Science Team

FAHClient on headless Ubuntu Server

Postby playforvoices » Mon Mar 23, 2020 2:03 pm

Hi folks,

I'm new to Folding@home. Currently, I use the FAHClient with the recent version on a headless Ubuntu 18.04 server machine.

On firewall, I've open the ports 7396 tcp and 36330 tcp for web client access and client communication. The client start to work properly but if he finished the job, he runs in idle mode and didn't load any new package from the folding server.

I have to stop and start the client. Then he starts to process a new package.

What's wrong here? Need the client an additional open port at the firewall? Or what is the correct way to configure the command line based client? I didn't found a good walkthrough for it. :shock:
playforvoices
 
Posts: 2
Joined: Mon Mar 23, 2020 1:43 pm
Location: Germany

Re: FAHClient on headless Ubuntu Server

Postby Joe_H » Mon Mar 23, 2020 8:36 pm

Few use the client directly from the command line. It can be used that way, but as I recall from testing that mode a few years ago there are issues. Most of the support is a few pages on the folding site, and the help within the FAHClient software - FAHClient --help.

Perhaps better, and more supported, is to install FAHClient using the installer. It can then be configured to allow remote access. FAHControl can be running any any system running Linux, Windows or OS X with a display and be set up to control the install on the headless server.
Image

iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
Joe_H
Site Admin
 
Posts: 6608
Joined: Tue Apr 21, 2009 5:41 pm
Location: W. MA

Re: FAHClient on headless Ubuntu Server

Postby playforvoices » Tue Mar 24, 2020 8:05 am

Hi Joe,

thanks for your answer. I've installed the FAHClient on Windows and add the Ubuntu server to the configuration. He is displayed as online and waiting for WU's.

Code: Select all
05:47:15:WU01:FS00:Uploading 2.46MiB to 155.247.164.214
05:47:15:WU01:FS00:Connecting to 155.247.164.214:8080
05:47:19:WU01:FS00:Upload complete
05:47:19:WU01:FS00:Server responded WORK_ACK (400)
05:47:19:WU01:FS00:Final credit estimate, 1000.00 points
05:47:19:WU01:FS00:Cleaning up
05:49:39:WU00:FS00:Connecting to 65.254.110.245:8080
05:49:39:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
05:49:39:WU00:FS00:Connecting to 18.218.241.186:80
05:49:40:WARNING:WU00:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
05:49:40:ERROR:WU00:FS00:Exception: Could not get an assignment
05:56:31:WU00:FS00:Connecting to 65.254.110.245:8080
05:56:32:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
05:56:32:WU00:FS00:Connecting to 18.218.241.186:80
05:56:32:WARNING:WU00:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
05:56:32:ERROR:WU00:FS00:Exception: Could not get an assignment
05:59:09:WARNING:Denied 30:192.168.1.11 access to URI: /api/updates/set?_=1585029549186&sid=29db129b1b98dd925a8fff61abe0e89e&update_id=0&update_path=/api/basic&update_rate=1
05:59:09:WARNING:Denied 31:192.168.1.11 access to URI: /api/updates/set?_=1585029549187&sid=29db129b1b98dd925a8fff61abe0e89e&update_id=1&update_path=/api/slots&update_rate=1
05:59:09:WARNING:Denied 32:192.168.1.11 access to URI: /api/configured?_=1585029549188&sid=29db129b1b98dd925a8fff61abe0e89e
05:59:10:WARNING:Denied 33:192.168.1.11 access to URI: /api/updates?_=1585029549189&sid=29db129b1b98dd925a8fff61abe0e89e
05:59:11:WARNING:Denied 34:192.168.1.11 access to URI: /api/updates?_=1585029549190&sid=29db129b1b98dd925a8fff61abe0e89e
06:07:35:WU00:FS00:Connecting to 65.254.110.245:8080
06:07:36:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
06:07:36:WU00:FS00:Connecting to 18.218.241.186:80
06:07:36:WARNING:WU00:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
06:07:36:ERROR:WU00:FS00:Exception: Could not get an assignment
06:25:32:WU00:FS00:Connecting to 65.254.110.245:8080
06:25:33:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
06:25:33:WU00:FS00:Connecting to 18.218.241.186:80
06:25:33:WARNING:WU00:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
06:25:33:ERROR:WU00:FS00:Exception: Could not get an assignment
06:47:17:40:192.168.1.109:New Web connection
06:47:18:54:192.168.1.109:New Web connection
06:54:34:WU00:FS00:Connecting to 65.254.110.245:8080
06:54:35:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
06:54:35:WU00:FS00:Connecting to 18.218.241.186:80
06:54:35:WARNING:WU00:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
06:54:35:ERROR:WU00:FS00:Exception: Could not get an assignment
playforvoices
 
Posts: 2
Joined: Mon Mar 23, 2020 1:43 pm
Location: Germany


Return to V7.5.1 Public Release Windows/Linux/MacOS X

Who is online

Users browsing this forum: No registered users and 2 guests

cron