starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 14:15:59 +03:00

[GH-ISSUE #844] Ark Server Details #680

New issue

Closed

opened 2026-02-27 02:03:06 +03:00 by kerem · 20 comments

kerem commented

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

Owner

Originally created by @reesey275 on GitHub (May 29, 2016).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/844

When running ./arkserver details script it is no longer pulling the IP/Port information from the GameUserSettings.ini file. This is also creating an issue when stopping the server
Stopping ark-server: no queryport found using info_config.sh/home/ark/lgsm/functions/command_stop.sh: line 177: ((: pidcheck < : syntax error: operand expected (error token is "< ")

Originally created by @reesey275 on GitHub (May 29, 2016). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/844 When running ./arkserver details script it is no longer pulling the IP/Port information from the GameUserSettings.ini file. This is also creating an issue when stopping the server Stopping ark-server: no queryport found using info_config.sh/home/ark/lgsm/functions/command_stop.sh: line 177: ((: pidcheck < : syntax error: operand expected (error token is "< ")

kerem closed this issue

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

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (May 29, 2016):

Did you update your functions ?
./arkserver uf

@UltimateByte commented on GitHub (May 29, 2016): Did you update your functions ? `./arkserver uf`

kerem commented

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

Author

Owner

@reesey275 commented on GitHub (May 29, 2016):

Clean installation with new arkserver script.

@reesey275 commented on GitHub (May 29, 2016): Clean installation with new arkserver script.

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (May 29, 2016):

I messaged CedarLug about this as he reworked that function recently.

@UltimateByte commented on GitHub (May 29, 2016): I messaged CedarLug about this as he reworked that function recently.

kerem commented

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

Author

Owner

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

Will check - but I know the current version of the arkserver script lacks an assigned parmslocation, so ./arkserver details won't pull the IP/Port from either location (selfname or GameUserSettings.ini). See tail comments of #770

@cedarlug commented on GitHub (May 29, 2016): Will check - but I know the current version of the arkserver script lacks an assigned parmslocation, so ./arkserver details won't pull the IP/Port from either location (selfname or GameUserSettings.ini). See tail comments of #770

kerem commented

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

Author

Owner

@reesey275 commented on GitHub (May 29, 2016):

I had the ports showing correctly in a previous build pulling the info from the GameUserSettings.ini. HDD failed on that VM so lost quite a bit of the coding that was done to get things to work.

@reesey275 commented on GitHub (May 29, 2016): I had the ports showing correctly in a previous build pulling the info from the GameUserSettings.ini. HDD failed on that VM so lost quite a bit of the coding that was done to get things to work.

kerem commented

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

Author

Owner

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

Update:
The original line 177 error in command_stop.sh was a typo that was fixed in the last pull request in the development branch. The type-o is "MADPIDITER" on line 177 should be "MAXPIDITER", in reference to the maximum number of times the loop checks for an active pid.

@cedarlug commented on GitHub (May 29, 2016): Update: The original line 177 error in command_stop.sh was a typo that was fixed in the last pull request in the development branch. The type-o is "MADPIDITER" on line 177 should be "MAXPIDITER", in reference to the maximum number of times the loop checks for an active pid.

kerem commented

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

Author

Owner

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

@reesey275 Settings in GameUserSettings.ini don't affect the actual runtime assignments. For example, if you set QueryPort=20735 in GameUserSettings.ini and start the game using ./arkserver start, your service will still be running on port 27015.

I'd recommend leveraging the the startup parameters in the script (selfname) as the default location, and using GameUserSettings.ini as a backup location for pulling details in the event they are not specified in selfname (arkserver script).

I can make that happen and work up a pull request if this approach makes sense to everyone.

@cedarlug commented on GitHub (May 29, 2016): @reesey275 Settings in GameUserSettings.ini don't affect the actual runtime assignments. For example, if you set QueryPort=20735 in GameUserSettings.ini and start the game using ./arkserver start, your service will still be running on port 27015. I'd recommend leveraging the the startup parameters in the script (selfname) as the default location, and using GameUserSettings.ini as a backup location for pulling details in the event they are not specified in selfname (arkserver script). I can make that happen and work up a pull request if this approach makes sense to everyone.

kerem commented

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

Author

Owner

@reesey275 commented on GitHub (May 29, 2016):

I've been using the port setting in GameUserSettings.ini and it works
correctly when launching the server.
On May 29, 2016 3:19 PM, "CedarLUG" notifications@github.com wrote:

@reesey275 https://github.com/reesey275 Setting in GameUserSettings.ini
don't affect the actual runtime assignments. For example, if you set
QueryPort=20735 in GameUserSettings.ini and start the game using
./arkserver start, your service will still be running on port 27015.

I'd recommend leveraging the the startup parameters in the script
(selfname) as the default location, and using GameUserSettings.ini as a
backup location for pulling details in the event they are not specified in
selfname (arkserver script).

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dgibbs64/linuxgsm/issues/844#issuecomment-222377690,
or mute the thread
https://github.com/notifications/unsubscribe/AEd5Lh9Uo1Y9gjXshF6cSpwFOqjsHdOnks5qGebVgaJpZM4IpL_A
.

@reesey275 commented on GitHub (May 29, 2016): I've been using the port setting in GameUserSettings.ini and it works correctly when launching the server. On May 29, 2016 3:19 PM, "CedarLUG" notifications@github.com wrote: > @reesey275 https://github.com/reesey275 Setting in GameUserSettings.ini > don't affect the actual runtime assignments. For example, if you set > QueryPort=20735 in GameUserSettings.ini and start the game using > ./arkserver start, your service will still be running on port 27015. > > I'd recommend leveraging the the startup parameters in the script > (selfname) as the default location, and using GameUserSettings.ini as a > backup location for pulling details in the event they are not specified in > selfname (arkserver script). > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > https://github.com/dgibbs64/linuxgsm/issues/844#issuecomment-222377690, > or mute the thread > https://github.com/notifications/unsubscribe/AEd5Lh9Uo1Y9gjXshF6cSpwFOqjsHdOnks5qGebVgaJpZM4IpL_A > .

kerem commented

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

Author

Owner

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

Easy enough to verify:
root@gamerig:# su - arkserver
arkserver@gamerig:$ grep QueryPort serverfiles/ShooterGame/Saved/Config/LinuxServer/GameUserSettings.ini
QueryPort=27025
arkserver@gamerig:$ grep QueryPort arkserver
arkserver@gamerig:$ ./arkserver start
[ OK ] Starting ark-server:
arkserver@gamerig:$ netstat -nap | grep Shoot
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
udp 768 0 0.0.0.0:27015 0.0.0.0:* 1638/./ShooterGameS
arkserver@gamerig:$

Even though it's set to 27025 in GameUserSettings.ini, it's listening on 27015.

@cedarlug commented on GitHub (May 29, 2016): Easy enough to verify: root@gamerig:~# su - arkserver arkserver@gamerig:~$ grep QueryPort serverfiles/ShooterGame/Saved/Config/LinuxServer/GameUserSettings.ini QueryPort=27025 arkserver@gamerig:~$ grep QueryPort arkserver arkserver@gamerig:~$ ./arkserver start [ OK ] Starting ark-server: arkserver@gamerig:~$ netstat -nap | grep Shoot (Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.) udp 768 0 0.0.0.0:27015 0.0.0.0:\* 1638/./ShooterGameS arkserver@gamerig:~$ Even though it's set to 27025 in GameUserSettings.ini, it's listening on 27015.

kerem commented

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

Author

Owner

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

I'd greatly appreciate someone else's confirmation of the above finding, too: Namely that setting ports in the GameUserSettings.ini are ignored.

I'd equally appreciate someone else's counter example as well.

@cedarlug commented on GitHub (May 29, 2016): I'd greatly appreciate someone else's confirmation of the above finding, too: Namely that setting ports in the GameUserSettings.ini are ignored. I'd equally appreciate someone else's counter example as well.

kerem commented

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

Author

Owner

@reesey275 commented on GitHub (May 29, 2016):

You are correct. Just double checked to make sure.

@reesey275 commented on GitHub (May 29, 2016): You are correct. Just double checked to make sure.

kerem commented

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

Author

Owner

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

Thanks for the confirmation. I'm glad that the type-o is still active, because it led to a better conversation about the correct way to parse parameters.

@cedarlug commented on GitHub (May 29, 2016): Thanks for the confirmation. I'm glad that the type-o is still active, because it led to a better conversation about the correct way to parse parameters.

kerem commented

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

Author

Owner

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

can you post (to pastebin) the output of:
awk 'NR>=162&&NR<=199' ~/lgsm/functions/command_stop.sh

@cedarlug commented on GitHub (May 29, 2016): can you post (to pastebin) the output of: `awk 'NR>=162&&NR<=199' ~/lgsm/functions/command_stop.sh`

kerem commented

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

Author

Owner

@reesey275 commented on GitHub (May 29, 2016):

Sure thing.

http://pastebin.com/SkhBDLAE

@reesey275 commented on GitHub (May 29, 2016): Sure thing. [http://pastebin.com/SkhBDLAE](http://pastebin.com/SkhBDLAE)

kerem commented

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

Author

Owner

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

Thanks,

I see what the issue is: Your port in GameUserSettings.ini isn't the port that the server is actually listening on any more :) [Because of my request for you to verify that GameUserSettings.ini isn't setting things correctly.]

So, to fix this, make sure that the QueryPort in GameUserSettings.ini matches what you see when you type:
'netstat -nap | grep Shoot'

You'll likely see 3 sockets in-use. The QueryPort is usually in the 27000+ range and UDP.

@cedarlug commented on GitHub (May 29, 2016): Thanks, I see what the issue is: Your port in GameUserSettings.ini isn't the port that the server is actually listening on any more :) [Because of my request for you to verify that GameUserSettings.ini isn't setting things correctly.] So, to fix this, make sure that the QueryPort in GameUserSettings.ini matches what you see when you type: 'netstat -nap | grep Shoot' You'll likely see 3 sockets in-use. The QueryPort is usually in the 27000+ range and UDP.

kerem commented

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

Author

Owner

@reesey275 commented on GitHub (May 29, 2016):

Looks like it's good to go.

netstat -nap | grep Shoot
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 0.0.0.0:32330 0.0.0.0:* LISTEN 3594/ShooterGameSer
udp 0 0 0.0.0.0:7778 0.0.0.0:* 3594/ShooterGameSer
udp 0 0 0.0.0.0:27015 0.0.0.0:* 3594/ShooterGameSer

Thanks for the help.

@reesey275 commented on GitHub (May 29, 2016): Looks like it's good to go. netstat -nap | grep Shoot (Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.) tcp 0 0 0.0.0.0:32330 0.0.0.0:\* LISTEN 3594/ShooterGameSer udp 0 0 0.0.0.0:7778 0.0.0.0:\* 3594/ShooterGameSer udp 0 0 0.0.0.0:27015 0.0.0.0:\* 3594/ShooterGameSer Thanks for the help.

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (May 30, 2016):

@cedarlug @reesey275 So no code issue ? Can we close this ?

@UltimateByte commented on GitHub (May 30, 2016): @cedarlug @reesey275 So no code issue ? Can we close this ?

kerem commented

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

Author

Owner

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

This can be closed when #834 is worked into the master branch. But yes - I believe this can be closed.

@cedarlug commented on GitHub (May 30, 2016): This can be closed when #834 is worked into the master branch. But yes - I believe this can be closed.

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (May 30, 2016):

Let's wait for the merge then. ^^

@UltimateByte commented on GitHub (May 30, 2016): Let's wait for the merge then. ^^

kerem commented

2026-02-27 02:03:07 +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.