Reading up on a previous issue 899, the solution to start the ARK server on startup is to run the instance via systemctl, I have a problem though, there is no arkmanager.service.
I've tried adding my own .service:
`[Unit]
Description=ARK Server 29/08/2023
After=network.target
StartLimitIntervalSec=0
No luck. Service starts, fails after 10 seconds, and reboots. arkmanager and steamcmd CPU usage fluctuates from 40% each (1 core) down to 0% at each failure.
Any idea why, for one, I don't have an arkmanager.service, and two, my custom service doesn't work?
Reading up on a previous issue 899, the solution to start the ARK server on startup is to run the instance via systemctl, I have a problem though, there is no arkmanager.service.
I've tried adding my own .service: `[Unit] Description=ARK Server 29/08/2023 After=network.target StartLimitIntervalSec=0
[Service] Type=simple Restart=always RestartSec=1 User=steam ExecStart=/usr/local/bin/arkmanager start --alwaysrestart
[Install] WantedBy=multi-user.target`
No luck. Service starts, fails after 10 seconds, and reboots. arkmanager and steamcmd CPU usage fluctuates from 40% each (1 core) down to 0% at each failure.
Any idea why, for one, I don't have an arkmanager.service, and two, my custom service doesn't work?