[GH-ISSUE #2109] 7DTD Wrong query port Alpha 17 #1630

Closed
opened 2026-02-27 02:58:13 +03:00 by kerem · 8 comments
Owner

Originally created by @Eekiig on GitHub (Dec 12, 2018).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2109

Environment
OS: Ubuntu server 16.04.5 LTS
Server: 7DaysToDie Alpha 17

Problem
If you update the 7DaysToDie-Server to latest experimental (A17), the monitor tool restarts the server even if it is running.

Reason
In Alpha 17 the query-port has moved to the main gameserver-port but the monitor (gsquery) querys on gameserver-port+1.

Workaround
Change the queryport to the main port in info_config.sh
nano ~/lgsm/functions/info_config.sh
Edit queryport in section:
fn_info_config_sdtd()
from
[row 909] queryport=$((port + 1))
to
[row 909] queryport=$(grep "ServerPort" "${servercfgfullpath}" | tr -cd '[:digit:]')

Now the monitor will use the ServerPort for querys.

Greetings Eekiig

Originally created by @Eekiig on GitHub (Dec 12, 2018). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2109 **Environment** OS: Ubuntu server 16.04.5 LTS Server: 7DaysToDie Alpha 17 **Problem** If you update the 7DaysToDie-Server to latest experimental (A17), the monitor tool restarts the server even if it is running. **Reason** In Alpha 17 the query-port has moved to the main gameserver-port but the monitor (gsquery) querys on gameserver-port+1. **Workaround** Change the queryport to the main port in info_config.sh `nano ~/lgsm/functions/info_config.sh` Edit queryport in section: `fn_info_config_sdtd()` from `[row 909] queryport=$((port + 1))` to `[row 909] queryport=$(grep "ServerPort" "${servercfgfullpath}" | tr -cd '[:digit:]')` Now the monitor will use the ServerPort for querys. Greetings Eekiig
kerem 2026-02-27 02:58:13 +03:00
Author
Owner

@joshhsoj1902 commented on GitHub (Dec 23, 2018):

FYI, A17 was released today so this is now the version installed by default!

<!-- gh-comment-id:449659855 --> @joshhsoj1902 commented on GitHub (Dec 23, 2018): FYI, A17 was released today so this is now the version installed by default!
Author
Owner

@h3o66 commented on GitHub (Jan 16, 2019):

I think this should be solved by the hotfix mentioned.

Can you confirm this after updating lgsm ?

<!-- gh-comment-id:454982831 --> @h3o66 commented on GitHub (Jan 16, 2019): I think this should be solved by the hotfix mentioned. Can you confirm this after updating lgsm ?
Author
Owner

@Eekiig commented on GitHub (Jan 17, 2019):

Nope, doesn't work for me. Update to latest lgsm results in an empty queryport.
Monitor sdtd-server: Querying port: gsquery: 192.168.0.21: : 0/1: QUERYING[ FAIL ] Monitor sdtd-server: Querying port: gsquery: 192.168.0.21: : 0/1: FAIL[ FAIL ]

<!-- gh-comment-id:455142896 --> @Eekiig commented on GitHub (Jan 17, 2019): Nope, doesn't work for me. Update to latest lgsm results in an empty queryport. `Monitor sdtd-server: Querying port: gsquery: 192.168.0.21: : 0/1: QUERYING[ FAIL ] Monitor sdtd-server: Querying port: gsquery: 192.168.0.21: : 0/1: FAIL[ FAIL ]`
Author
Owner

@dgibbs64 commented on GitHub (Jan 17, 2019):

I did quite a bit of work on this to get everything working with A17 so should be working correctly now. How odd

<!-- gh-comment-id:455145923 --> @dgibbs64 commented on GitHub (Jan 17, 2019): I did quite a bit of work on this to get everything working with A17 so should be working correctly now. How odd
Author
Owner

@Eekiig commented on GitHub (Jan 17, 2019):

Seems the workaround on my first post also didn't work anymore with the latest version of lgsm. It leads to the same result of an empty queryport.

<!-- gh-comment-id:455147628 --> @Eekiig commented on GitHub (Jan 17, 2019): Seems the workaround on my first post also didn't work anymore with the latest version of lgsm. It leads to the same result of an empty queryport.
Author
Owner

@dgibbs64 commented on GitHub (Jan 17, 2019):

I have re-tested this and querying is working for me. The query port is now the same port as the gameport which by default is 26900

DESCRIPTION  DIRECTION  PORT   PROTOCOL
> Game/RCON  INBOUND    26900  udp
> Query      INBOUND    26900  udp
> WebAdmin   INBOUND    8080   tcp
> Telnet     INBOUND    8081   tcp

I would check that the details are being pulled correct. The data is pulled from the config sdtdserver.xml

<!-- gh-comment-id:455298172 --> @dgibbs64 commented on GitHub (Jan 17, 2019): I have re-tested this and querying is working for me. The query port is now the same port as the gameport which by default is 26900 ``` DESCRIPTION DIRECTION PORT PROTOCOL > Game/RCON INBOUND 26900 udp > Query INBOUND 26900 udp > WebAdmin INBOUND 8080 tcp > Telnet INBOUND 8081 tcp ``` I would check that the details are being pulled correct. The data is pulled from the config `sdtdserver.xml`
Author
Owner

@Eekiig commented on GitHub (Feb 7, 2019):

After a reinstall of LGSM all works fine.

  • Bug closed - Thanx! ;-)
<!-- gh-comment-id:461398695 --> @Eekiig commented on GitHub (Feb 7, 2019): After a reinstall of LGSM all works fine. - Bug closed - Thanx! ;-)
Author
Owner

@lock[bot] commented on GitHub (Feb 17, 2020):

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.

<!-- gh-comment-id:587206329 --> @lock[bot] commented on GitHub (Feb 17, 2020): 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.
Sign in to join this conversation.
No labels
Atomic
Epic
cannot reproduce
command: backup
command: console
command: debug
command: details
command: fast-dl
command: install
command: mods
command: monitor
command: post-details
command: restart
command: send
command: start
command: stop
command: update
command: update-lgsm
command: validate
command: wipe
distro: AlmaLinux
distro: Arch Linux
distro: CentOS
distro: Debian
distro: Fedora
distro: RedHat
distro: Rocky Linux
distro: Ubuntu
distro: openSUSE
engine: goldsrc
engine: source
game: 7 Days to Die
game: ARMA 3
game: Ark: Survival Evolved
game: Assetto Corsa
game: Avorion
game: BATTALION: Legacy
game: Barotrauma
game: Battalion 1944
game: Battlefield 1942
game: Black Mesa: Deathmatch
game: Blade Symphony
game: Call of Duty 2
game: Call of Duty 4
game: Call of Duty: United Offensive
game: Counter-Strike 1.6
game: Counter-Strike 2
game: Counter-Strike: Global Offensive
game: Counter-Strike: Source
game: Day of Infamy
game: Dayz
game: Death Match Classic
game: Don't Starve Together
game: ET: Legacy
game: Eco
game: Factorio
game: Factorio
game: Garry's Mod
game: Half-Life
game: Hurtword
game: Insurgecy
game: Insurgecy
game: Insurgency: Sandstorm
game: Just Cause 3
game: Killing Floor
game: Killing Floor 2
game: Left 4 Dead 2
game: Minecraft
game: Minecraft Bedrock
game: Mordhau
game: Multi Theft Auto
game: Mumble
game: Natural Selection 2
game: No More Room in Hell
game: Pavlov VR
game: Post Scriptum
game: Project Zomboid
game: Quake 3
game: QuakeWorld
game: Red Orchestra: Ostfront 41-45
game: Return to Castle Wolfenstein
game: Rising World
game: Rust
game: San Andreas Multiplayer
game: Satisfactory
game: Soldat
game: Soldier of Fortune 2
game: Squad
game: Squad 44
game: Starbound
game: Stationeers
game: Sven Co-op
game: Team Fortress 2
game: Teamspeak 3
game: Teeworlds
game: Terraria
game: The Front
game: Unreal Tournament 2004
game: Unreal Tournament 3
game: Unreal Tournament 99
game: Unturned
game: Valheim
game: Wurm Unlimited
game: Zombie Master Reborn
game: label missing
good first issue
help wanted
info: alerts
info: dependency
info: docker
info: docs
info: email
info: query
info: steamcmd
info: systemd
info: tmux
info: website
info: website
needs more info
outcome: duplicate
outcome: issue resolved
outcome: issue resolved
outcome: issue unresolved
outcome: pr accepted
outcome: pr rejected
outcome: unconfirmed
outcome: wontfix
outcome: wrong forum
potential-duplicate
priority
pull-request
type: bug
type: feature
type: feature
type: feature request
type: game server request
type: refactor
waiting response
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/LinuxGSM#1630
No description provided.