[Linux] ASF doesn't run even though the service is running / No errors

[MoShU23]

Hi,

I been running ASF on my Raspberry Pi for the past 3 years, more or less without issues. Today I had a look at my config file via the ASF-ui and noticed that my "UpdatePeriod" was set to 48, so I changed it 24, saved and waited for ASF to restart. Unfortunately it never came back online and I'm a bit baffled as to why. I attached the last lines from the log before it closed down ( https://hastebin.com/iyuwivipab.apache ) no other logs are being created when I try to start it.

I start it with systemctl start ArchiSteamFarm@asf and I get this:

 [email protected] - ArchiSteamFarm Service (on asf)
   Loaded: loaded (/home/asf/ArchiSteamFarm/[email protected]; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2022-11-13 01:34:31 GMT; 1s ago
     Docs: https://github.com/JustArchiNET/ArchiSteamFarm/wiki
 Main PID: 3252 (ArchiSteamFarm)
    Tasks: 4 (limit: 4915)
   CGroup: /system.slice/system-ArchiSteamFarm.slice/[email protected]
           └─3252 [ArchiSteamFarm]

Nov 13 01:34:31 raspberrypi systemd[1]: Started ArchiSteamFarm Service (on asf).

I close it down with systemctl stop ArchiSteamFarm@asf and I get this:

 [email protected] - ArchiSteamFarm Service (on asf)
   Loaded: loaded (/home/asf/ArchiSteamFarm/[email protected]; enabled; vendor preset: enabled)
   Active: failed (Result: signal) since Sun 2022-11-13 01:38:04 GMT; 5s ago
     Docs: https://github.com/JustArchiNET/ArchiSteamFarm/wiki
  Process: 3252 ExecStart=/home/asf/ArchiSteamFarm/ArchiSteamFarm --no-restart --process-required --service --system-required (code=killed, signal=SYS)
 Main PID: 3252 (code=killed, signal=SYS)

Nov 13 01:34:31 raspberrypi systemd[1]: Started ArchiSteamFarm Service (on asf).
Nov 13 01:38:04 raspberrypi systemd[1]: Stopping ArchiSteamFarm Service (on asf)...
Nov 13 01:38:04 raspberrypi systemd[1]: [email protected]: Main process exited, code=killed, status=31/SYS
Nov 13 01:38:04 raspberrypi systemd[1]: [email protected]: Failed with result 'signal'.
Nov 13 01:38:04 raspberrypi systemd[1]: Stopped ArchiSteamFarm Service (on asf).

When I run journalctl -u [email protected] I only get this

Nov 13 01:34:15 raspberrypi systemd[1]: Stopping ArchiSteamFarm Service (on asf)...
Nov 13 01:34:15 raspberrypi systemd[1]: [email protected]: Main process exited, code=killed, status=31/SYS
Nov 13 01:34:15 raspberrypi systemd[1]: [email protected]: Failed with result 'signal'.
Nov 13 01:34:15 raspberrypi systemd[1]: Stopped ArchiSteamFarm Service (on asf).
Nov 13 01:34:31 raspberrypi systemd[1]: Started ArchiSteamFarm Service (on asf).
Nov 13 01:38:04 raspberrypi systemd[1]: Stopping ArchiSteamFarm Service (on asf)...
Nov 13 01:38:04 raspberrypi systemd[1]: [email protected]: Main process exited, code=killed, status=31/SYS
Nov 13 01:38:04 raspberrypi systemd[1]: [email protected]: Failed with result 'signal'.
Nov 13 01:38:04 raspberrypi systemd[1]: Stopped ArchiSteamFarm Service (on asf).
Nov 13 01:40:57 raspberrypi systemd[1]: Started ArchiSteamFarm Service (on asf).

I'm not exactly sure as to what happened, is not the first time I change the config file via asf-ui and I never had any problems. Is there a command that I'm missing to get a bit more details? Enabling debug doesn't do much since ASF doesn't actually starts in the first place. The fact that I don't get any errors it confuses me a bit, the service is running, although is showed as defunct.

UNIT                        LOAD   ACTIVE SUB     DESCRIPTION
[email protected]  loaded active running ArchiSteamFarm Service (on asf)

But nothing happens, what am I missing here? Any help is appreciated, thank you.

[JustArchi]

31/SYS is systemd (actually kernel) killing the app due to security concerns, ASF uses now very strict security rules, which means if it tries to do something undefined, this may happen.

I'll need more details from you, check journalctl -r or dmesg, there should be a note from systemd/kernel about which call ASF tries to do before it's killed. This will help me fix the problem.

[MoShU23]

https://hastebin.com/egosoyekeg.http

By the looks of it, it can't read the values on [email protected] file, beside editing the ExecStart parameters, I have never touched anything else on that file, plus I just unpacked the files again, so everything should be default. I double check and user asf does have access to /home/asf/ArchiSteamFarm , shouldn't have a problem reading / writing there.

[JustArchi]

Thanks, you're using pretty old systemd version (from Debian oldstable), this is probably the root culprit of your issue.

Find [email protected] file in /etc/systemd/system directory, and try to comment out lines 37 and 38, like this:

#SystemCallFilter=@system-service
#SystemCallFilter=~@privileged

Save the file, get to the root shell su or sudo -i, and then execute systemctl daemon-reload and systemctl start ArchiSteamFarm@asf, see if it helps.

[MoShU23]

Yes, commenting those two lines worked, it started normally after reboot as well.

I'm still running on pi OS based on buster since switching to the newer one requires a fresh install and I'm not that comfortable with moving everything back after install, pretty sure I will screw something up but I guess I might have to do it eventually if this becomes a problem again.

Thank you very much for your help, I was really stuck on this one, much appreciated.

[JustArchi]

No problem, I've addressed this issue in ASF 5.4.0.0, so no manual edits are required. I'd recommend you to upgrade your system regardless, as your OS is obsolete and doesn't receive even security updates anymore - ASF will eventually just drop support for it, it's not my intention to do it just yet, but eventually I will (likely with .NET 8+), so it's a good idea to at least try to be on current Debian stable.