arkmanager / ark-server-tools

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

Multi Instance Multi IP #1127

Open 46guldogan opened 4 years ago

46guldogan commented 4 years ago

I'll try multi ip adresses for multi server (clusters) but i get error.

ark@gibirnetark:$ arkmanager status Running command 'status' for instance 'main' Server running: No Server listening: No Server build ID: 5320732 Server version: 312.57 ark@gibirnetark:$ tail -f /var/log/arktools/arkserver.log 2020-07-23 13:43:05: [thecenter] /usr/local/bin/arkmanager: line 1224: 3650 Abo rted (core dumped) "$arkserverroot/$arkserverexec" "$arkserverop ts" "${arkextraopts[@]}" 2020-07-23 13:43:05: [thecenter] 2020-07-23 13:43:05: Bad PID ''; expected '3650 ' 2020-07-23 13:43:05: [thecenter] 2020-07-23 13:43:05: exited with status 0 2020-07-23 13:43:11: [theisland] 2020-07-23 13:43:11: start 2020-07-23 13:43:11: [theisland] 2020-07-23 13:43:11: Running /home/ark/ARK/Shoo terGame/Binaries/Linux/ShooterGameServer TheIsland?RCONEnabled=True?RCONPort=3 2330?SessionName=[TR]StayGamer.COM\ [5xPvE/MODS/3\ CLUSTER]\ GibirNET?Port =7778?QueryPort=27015?MaxPlayers=70?GameModIds=872898241,718872221,14285965 66,895711211,1609138312,1999447172,1404697612,849985437,889745138,9246191 15?AltSaveDirectoryName=Saved-StayIsland?MultiHome=45.12.55.100?listen -NoTra nsferFromFiltering -NoBattleEye -server 2020-07-23 13:43:11: [theisland] 2020-07-23 13:43:11: Server PID: 3924 2020-07-23 13:43:12: [theisland] [S_API FAIL] SteamAPI_Init() failed; SteamAPI_I sSteamRunning() failed. 2020-07-23 13:43:16: [theisland] /usr/local/bin/arkmanager: line 1224: 3924 Abo rted (core dumped) "$arkserverroot/$arkserverexec" "$arkserverop ts" "${arkextraopts[@]}" 2020-07-23 13:43:16: [theisland] 2020-07-23 13:43:16: Bad PID ''; expected '3924 ' 2020-07-23 13:43:16: [theisland] 2020-07-23 13:43:16: exited with status 0

klightspeed commented 4 years ago

The server is dying after 5 seconds

Does it work with the mods you have selected if you don't specify an IP address to bind to?

Is the IP address bound directly to an interface on the machine? MultiHome cannot be used to bind to an address that is not bound to an interface on the machine.

2020-07-23 13:43:11: [theisland] 2020-07-23 13:43:11: start

Script is starting

2020-07-23 13:43:11: [theisland] 2020-07-23 13:43:11: Running /home/ark/ARK/ShooterGame/Binaries/Linux/ShooterGameServer TheIsland?RCONEnabled=True?RCONPort=32330?SessionName=[TR]StayGamer.COM\ [5xPvE/MODS/3\ CLUSTER]\ GibirNET?Port=7778?QueryPort=27015?MaxPlayers=70?GameModIds=872898241,718872221,1428596566,895711211,1609138312,1999447172,1404697612,849985437,889745138,924619115?AltSaveDirectoryName=Saved-StayIsland?MultiHome=45.12.55.100?listen -NoTransferFromFiltering -NoBattleEye -server

This is the command the script is using to run the server

2020-07-23 13:43:11: [theisland] 2020-07-23 13:43:11: Server PID: 3924

Server is backgrounded so the script can monitor when it starts listening

2020-07-23 13:43:12: [theisland] [S_API FAIL] SteamAPI_Init() failed; SteamAPI_I sSteamRunning() failed.

The game server always gives this - it is harmless.

2020-07-23 13:43:16: [theisland] /usr/local/bin/arkmanager: line 1224: 3924 Aborted (core dumped) "$arkserverroot/$arkserverexec" "$arkserveropts" "${arkextraopts[@]}"

The game server aborted after running for 5 seconds. It doesn't seem to have output why it aborted. Note that a normal shutdown will also have the server exit by aborting.

2020-07-23 13:43:16: [theisland] 2020-07-23 13:43:16: Bad PID ''; expected '3924 '

The server is no longer alive, so checking on the server results in no running PID.

Alphakilo commented 4 years ago

I've seen this happen on my setup. The old process was still running (PID file got lost on the way :smile:) and listening on its configured port, preventing the new process to bind on that port. Manually killing the old process (kill -SIGINT $pid) and running arkmanager start worked for me.

Not sure if it's the same root cause, but perhaps we could do some environment / sanity checks for some common issues that'd cause the dreaded "Abo rted (core dumped)" on startup. Or at least have the output contain some pointers on where to go from there (e.g. "Check $logdir/$arkserverLog for more details").