[GH-ISSUE #806] [ARK] Restart script issue. #646

New issue

Closed

opened 2026-02-27 02:02:52 +03:00 by kerem · 5 comments

kerem commented

2026-02-27 02:02:52 +03:00

Owner

Originally created by @TOXid on GitHub (May 5, 2016).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/806

Restart script does not pause between Stop and Start function, so server does not have time to release ports and result of execute Restart function is CreateBoundSocket: ::bind couldn't find an open port between 27015 and 27015.

Originally created by @TOXid on GitHub (May 5, 2016). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/806 Restart script does not pause between Stop and Start function, so server does not have time to release ports and result of execute Restart function is `CreateBoundSocket: ::bind couldn't find an open port between 27015 and 27015`.

kerem closed this issue

2026-02-27 02:02:52 +03:00

kerem commented

2026-02-27 02:02:52 +03:00

Author

Owner

@cedarlug commented on GitHub (May 19, 2016):

I have a working fix for this ready for a pull but would like a second/third set of eyes on the actual crux of the issue (rather than just a fix for it).

Can someone confirm:

Changing "QueryPort=" in serverfiles/ShooterGame/Saved/Config/LinuxServer/GameUserSettings.ini has no effect on the actual port used in the game. None. Changing this to anything other than 27015 and starting the server has no effect. This is problematic because ./arkserver details - info_config.sh specifically - pulls this (incorrect) information to report the ports used.
When issuing "./arkserver stop", a rogue ShooterGame process is left bound on both "Port+1" and "QueryPort".
This process does not exit gracefully within a reasonable amount of time.

ADVthanksANCE

@cedarlug commented on GitHub (May 19, 2016): I have a working fix for this ready for a pull but would like a second/third set of eyes on the actual crux of the issue (rather than just a fix for it). Can someone confirm: - Changing "<tt>QueryPort=</tt>" in <tt>serverfiles/ShooterGame/Saved/Config/LinuxServer/GameUserSettings.ini</tt> has no effect on the actual port used in the game. None. Changing this to anything other than 27015 and starting the server has no effect. This is problematic because <tt>./arkserver details</tt> - <tt>info_config.sh</tt> specifically - pulls this (incorrect) information to report the ports used. - When issuing "<tt>./arkserver stop</tt>", a rogue <tt>ShooterGame</tt> process is left bound on both "<tt>Port</tt>+1" and "<tt>QueryPort</tt>". - This process does not exit gracefully within a reasonable amount of time. ADV<b>thanks</b>ANCE

kerem commented

2026-02-27 02:02:52 +03:00

Author

Owner

@dgibbs64 commented on GitHub (May 19, 2016):

Please put the request in to the development branch when you are ready 👍

@dgibbs64 commented on GitHub (May 19, 2016): Please put the request in to the development branch when you are ready :+1:

kerem commented

2026-02-27 02:02:52 +03:00

Author

Owner

@dgibbs64 commented on GitHub (May 24, 2016):

Has this been fully resolved with https://github.com/dgibbs64/linuxgsm/pull/828 ? If so this can be closed. I have merged the ARK fix in to master now

@dgibbs64 commented on GitHub (May 24, 2016): Has this been fully resolved with https://github.com/dgibbs64/linuxgsm/pull/828 ? If so this can be closed. I have merged the ARK fix in to master now

kerem commented

2026-02-27 02:02:52 +03:00

Author

Owner

@cedarlug commented on GitHub (May 24, 2016):

Yes - merged with master #828 closes this

@cedarlug commented on GitHub (May 24, 2016): Yes - merged with master #828 closes this

kerem commented

2026-02-27 02:02:52 +03:00

Author

Owner

@lock[bot] commented on GitHub (Jul 19, 2018):

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock[bot] commented on GitHub (Jul 19, 2018): This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

kerem referenced this issue

2026-02-27 03:53:30 +03:00

[PR #705] [MERGED] Updating branch #3161