"Don't know system call group"

[GraceCourt]

I've just installed the most up-to-date client/FAHcontrol on a server running OpenSUSE Leap 15.2, and the client doesn't start. System call filters have only just been introduced in Leap v15.2 so the issue probably hasn't arisen widely yet. A quick grep in /var/log/messages reveals that the service tries to start, but fails with the error "Don't know system call group, ignoring: @system-service"... this is being generated by the line

SystemCallFilter=@system-service

I understand what system call filters are, and what they do, but I don't know why this group isn't pre-defined... and removing this line doesn't fix the issue (although it does reveal that the directory /etc/fahclient has been created but is empty... config.xml is missing).

Any advice? I have tried to find guidance on here but there's no obvious fix.

[promeneur]

Sorry i do not get this problem with opensuse Leap 15.2 and i don't know anything about "system call filters"

I use the rpms 7.6.21 from opensuse not folding@home.

Before, I uninstalled all rpms from folding@home.

[promeneur]

Hello i found a solution. There is a true bug.

see my tuto first comment. I wrote it again.

viewtopic.php?f=89&t=36442

[GraceCourt]

Thanks for this, I used the "Curiosity" RPMs as well.

Unfortunately, even after commenting out the SystemCallFilter line, it doesn't look as though it's an easy task to run this version as a service - when the FAHClient is run, it doesn't create config.xml in /etc/fahclient, it goes into /var/lib/ instead, or into /var/lib/configs/ (where a succession of copies are kept with a date/time stamp appended to the file name), and similarly the log goes into /var/lib/ or into /var/lib/logs/ (similarly with a date/time stamp in the file name).

Running FAHClient in the background from the command line works without any hiccups at all, so given that (for unconnected reasons) this server isn't up 24/7, I think I'll take the easy route and just set it going manually when appropriate.

Just in case this thread is found by anyone else thinking of running FAHClient on Leap 15.2, the Web Control, FAH Control, and FAH Viewer (visualiser) run perfectly if you have a graphics display, even if you only want to use FAH Control to tweak the settings that the FAH Client chooses for itself automatically. Well worth it, so many thanks to "Curiosity" for doing all the hard work to port it.

Edit: Quick and dirty way to make it run as a service... copy a valid config.xml file to /etc/fahconfig/ before starting the service as normal... NB: The Web Control, FAH Control, and FAH Viewer will not work and the live logfile goes to /var/lib/fahclient/work/logs/00/ but the client will keep running, picking up work units and returning the results.

Any changes to the config.xml file must be made manually (and very carefully!) to the version in /etc/fahclient.

[promeneur]

There is no more problem with today 19/12/2020 version 7.6.21-lp152.4.1 of faclient
after update

sudo systemctl daemon-reload
sudo systemctl start fahclient.service

if you get some problem then fill a report here https://bugzilla.opensuse.org/show_bug.cgi?id=1180005

Set my bug report to state “reopened” then add your problem. The author is very reactive.