Hi,
I just came from installing f@h client on a ubuntu server 20.04, but there is an issue with systemctl (see below).
top shows the client is running.
Is there anything I should do to get systemctl handle f@h client as a service?
I too am having problems with v21 and Ubuntu 20. I have installed the 7.6.21 client four times and while the installs are a little different each time, the result is the same. After an install, v21 prompts for the username, password, team, and power setting (I always select "full"). Then about a minute passes and the client begins running. I process normally until I restart my computer. After the restart, I find that the client is not running. Does not matter whether I log in as admin or standard user. I had NO problems with 7.6.13 and Ubuntu 18. Unfortunately, I violated the cardinal rule of changing two things at once - new OS and new client. Below is the error I see. Does anyone have any advice/suggestions? I have not tried to fall back to v13 but that is certainly an option. Thanks for any help.
The Linux installation script should install a script that starts FAHClient as a background daemon when you reboot. The installation also should create a unique user ID (probably "FAHClient") with just the permissions to run the daemon and access FAH's working files. The installation script also starts the Daemon and apparently that is working. The script that restarts the daemon after a reboot should do exactly the same thing and apparently it is not. Please confirm that FAHClient is/is_not running after a reboot.
When a new distro of Linux is distributed, they do sometimes change how the reboot script (/etc/init.d/FAHClient) needs to be installed and/or updated. I'm not enough of a Linux guru to know how 20.04 does it an why it isn't working for you but at least that's something that can be researched. What happens if you run that script manually?
Bruce, I can verify that FAHClient is not running after a reboot. When I run the reboot script I see the following errors. If there is an error in my config.xml I can't see it. This is the same file I used with 7.6.13 with the exception of the <fold-anon> line. Hopefully I have captured enough of the essentials to help someone offer a solution. It certainly has me puzzled ... and no, I have not fallen back to 7.6.13 yet. If someone way smarter than me has no suggestions, I will try to locate and reinstall v13 this weekend. Errors:
Also, I recommend against relying on the automagic translation from init.d to systemd for the init script. There is some good advice on working around this in another post:
viewtopic.php?f=81&t=33353#p318278
Look under the "TL;DR" heading. The best way to create the unit file is to issue:
Whompithian and Bruce, thanks for your help. v21 is back to running after a reboot ... finally. Turns out the startup for the client must perform a check of config.sys that failed when it hit my tag error. Once I fixed that and restarted the computer the config.sys was parsed and folding started right up. I didn't have to use systemctl to fix the init problem although both references contained valuable insights on how to do that. Under Ubuntu 20, systemctl enable relocated the init script due to its not being a part of LSB but I did not use it the second time since fixing config.sys solved the problem. Again, thanks!