search

arkmanager / ark-server-tools

Set of server tools used to manage ARK: Survival Evolved servers on Linux
MIT License
678 stars 143 forks source link

Setting arkAutoUpdateOnStart="true" in /etc/arkmanager.cfg prevents starting multiple instances with arkmanager.service #1210

Open cuphi opened 2 years ago

cuphi commented 2 years ago

After reading the docs and getting things setup, mods installed, cluster and item transfers working, and what not this is the only question I can't seem to find an answer to. My apologies if I missed it somewhere.

I would really love to bring my all of cluster up on system reboots without having to ssh into the server to issue a start @all.

klightspeed commented 2 years ago

Adding arkmanager.service to startup should start all of the configured instances.

cuphi commented 2 years ago

It is only starting the default instance. I think the issue is because I have arkmanager,cfg set to check for updates when starting an instance. The arkmanager.log contains these lines: 2022-01-06 13:31:26: [valguero] Checking for updates before starting 2022-01-06 13:31:26: [valguero] Checking for update; PID: 22336 2022-01-06 13:31:26: [crystal_isles] Start aborted due to running update - pid: 22336 2022-01-06 13:31:26: [extinction] Start aborted due to running update - pid: 22336 2022-01-06 13:31:26: [gen_2] Start aborted due to running update - pid: 22336 2022-01-06 13:31:26: [the_island] Start aborted due to running update - pid: 22336 2022-01-06 13:31:33: [valguero] Your server is already up to date! The most recent version is 7970694. 2022-01-06 13:31:33: [valguero] The server is starting...

So I will remove the automatic check for updates and see if that works.

Yes, commenting out arkAutoUpdateOnStart="true" in arkmanager.cfg allowed me to start all instances. This is odd to me because it's not an issue when manually issuing "arkmanager start @all."

klightspeed commented 2 years ago

This is odd to me because it's not an issue when manually issuing "arkmanager start @ALL."

The arkmanager.service systemd service starts each instance in its own arkmanager@instance.service, so startups / updates are not serialized like when using arkmanager start @all