starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 06:05:57 +03:00

[GH-ISSUE #3619] [BUG] sdtd monitor query fails #2413

New issue

Closed

opened 2026-02-27 03:02:47 +03:00 by kerem · 8 comments

kerem commented

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

Owner

Originally created by @PointWolf-Dev on GitHub (Oct 14, 2021).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/3619

I## Basic info

Distro: [Distro: CentOS Linux 8]
Game: [SDTD]
Command: [Monitor]
LinuxGSM version: [ v21.3.2]

Further Information

Unable to run the monitor command as it shows my the query as failed:
[sdtdserver@games ~]$ ./sdtdserver monitor
[ OK ] Monitoring sdtdserver: Checking session: OK
[ .... ] Monitoring sdtdserver: Querying port: gsquery: 95.216.16.217:26900 : 0/[ FAIL ] Monitoring sdtdserver: Querying port: gsquery: 95.216.16.217:26900 : 0/1: FAIL

To Reproduce

I am unsure as this is a fresh install on a dedicated server.

Server Resource

CPU
Model: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz
Cores: 8
Frequency: 3803.346MHz
Avg Load: 0.24, 0.30, 0.33

Memory
Mem: total used free cached available
Physical: 32GB 14GB 18GB 13GB 18GB
Swap: 16GB 0B 16GB

Storage
Filesystem: /dev/md2
Total: 1.8T
Used: 17G
Available: 1.7T

Network
IP: 0.0.0.0
Internet IP: 95.216.16.217

Game Server Resource Usage

CPU Used: 31.6%
Mem Used: 42% 13395MB

Storage
Total: 16G
Serverfiles: 15G

7 Days To Die Server Details

Server name: NuperSatural - WoW - The Great Plague 10k
App ID: 294420
Server IP: 0.0.0.0:26900
Internet IP: 95.216.16.217:26900
Server password: NOT SET
Maxplayers: 25
Game mode: GameModeSurvival
Game world: The.Great.Plague.10k
Master server: not listed
Status: STARTED

Originally created by @PointWolf-Dev on GitHub (Oct 14, 2021). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/3619 I## Basic info * **Distro:** [Distro: CentOS Linux 8] * **Game:** [SDTD] * **Command:** [Monitor] * **LinuxGSM version:** [ v21.3.2] ## Further Information Unable to run the monitor command as it shows my the query as failed: [sdtdserver@games ~]$ ./sdtdserver monitor [ OK ] Monitoring sdtdserver: Checking session: OK [ .... ] Monitoring sdtdserver: Querying port: gsquery: 95.216.16.217:26900 : 0/[ FAIL ] Monitoring sdtdserver: Querying port: gsquery: 95.216.16.217:26900 : 0/1: FAIL ## To Reproduce I am unsure as this is a fresh install on a dedicated server. Server Resource ================================================================================ CPU Model: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz Cores: 8 Frequency: 3803.346MHz Avg Load: 0.24, 0.30, 0.33 Memory Mem: total used free cached available Physical: 32GB 14GB 18GB 13GB 18GB Swap: 16GB 0B 16GB Storage Filesystem: /dev/md2 Total: 1.8T Used: 17G Available: 1.7T Network IP: 0.0.0.0 Internet IP: 95.216.16.217 Game Server Resource Usage ================================================================================ CPU Used: 31.6% Mem Used: 42% 13395MB Storage Total: 16G Serverfiles: 15G 7 Days To Die Server Details ================================================================================ Server name: NuperSatural - WoW - The Great Plague 10k App ID: 294420 Server IP: 0.0.0.0:26900 Internet IP: 95.216.16.217:26900 Server password: NOT SET Maxplayers: 25 Game mode: GameModeSurvival Game world: The.Great.Plague.10k Master server: not listed Status: STARTED

kerem

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

closed this issue
added the
type: bug

command: monitor

distro: CentOS

command: details

game: 7 Days to Die

command: install

command: start

info: query
labels

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Oct 24, 2021):

[  OK  ] Monitoring sdtdserver: Checking session: OK
[  OK  ] Monitoring sdtdserver: Querying port: gsquery: xxx.xxx.242.198:26900 : 0/1: OK

Just checked and I can query OK. Unsure what is causing the issue

@dgibbs64 commented on GitHub (Oct 24, 2021): ```[lgsm@li1527-198 sdtdserver]$ ./sdtdserver m [ OK ] Monitoring sdtdserver: Checking session: OK [ OK ] Monitoring sdtdserver: Querying port: gsquery: xxx.xxx.242.198:26900 : 0/1: OK ``` Just checked and I can query OK. Unsure what is causing the issue

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Oct 28, 2021):

@johnoclockdk query seems to fail if the server has been running for a while. I am unsure what we can do to address this

@dgibbs64 commented on GitHub (Oct 28, 2021): @johnoclockdk query seems to fail if the server has been running for a while. I am unsure what we can do to address this

kerem commented

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

Author

Owner

@johnoclockdk commented on GitHub (Oct 28, 2021):

@johnoclockdk query seems to fail if the server has been running for a while. I am unsure what we can do to address this

maybe a leak with 7 Days To Die is it a old game

@johnoclockdk commented on GitHub (Oct 28, 2021): > @johnoclockdk query seems to fail if the server has been running for a while. I am unsure what we can do to address this maybe a leak with 7 Days To Die is it a old game

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Oct 28, 2021):

It might be that the bug has to be reported to the game developers. The only current workaround maybe to disable querying.

@dgibbs64 commented on GitHub (Oct 28, 2021): It might be that the bug has to be reported to the game developers. The only current workaround maybe to disable querying.

kerem commented

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

Author

Owner

@parasyte commented on GitHub (Jan 26, 2022):

I just setup a monitor because the game crashed, and I want to be notified the next time it happens. But the monitor cannot connect to the query port because the server does not listen on the port at all:

Useful port diagnostic command:
ss -tuplwn | grep 7DaysToDieServe

DESCRIPTION  PORT   PROTOCOL  LISTEN
Game         26900  udp       0
Game+2       26902  udp       2
Query        26900  tcp       0
Web Admin    8080   tcp       0
Telnet       8081   tcp       1

$ ss -tuplwn | grep 7DaysToDieServe
udp    UNCONN  0       0                   0.0.0.0:26902          0.0.0.0:*      users:(("7DaysToDieServe",pid=142064,fd=27))
udp    UNCONN  0       0                      [::]:26902             [::]:*      users:(("7DaysToDieServe",pid=142064,fd=31))
tcp    LISTEN  0       4096              127.0.0.1:8081           0.0.0.0:*      users:(("7DaysToDieServe",pid=142064,fd=23))

This might be a bug introduced by the game developers, but this definitely has nothing to do with how long the server has been running.

@parasyte commented on GitHub (Jan 26, 2022): I just setup a monitor because the game crashed, and I want to be notified the next time it happens. But the monitor cannot connect to the query port because the server does not listen on the port at all: ``` Useful port diagnostic command: ss -tuplwn | grep 7DaysToDieServe DESCRIPTION PORT PROTOCOL LISTEN Game 26900 udp 0 Game+2 26902 udp 2 Query 26900 tcp 0 Web Admin 8080 tcp 0 Telnet 8081 tcp 1 ``` ``` $ ss -tuplwn | grep 7DaysToDieServe udp UNCONN 0 0 0.0.0.0:26902 0.0.0.0:* users:(("7DaysToDieServe",pid=142064,fd=27)) udp UNCONN 0 0 [::]:26902 [::]:* users:(("7DaysToDieServe",pid=142064,fd=31)) tcp LISTEN 0 4096 127.0.0.1:8081 0.0.0.0:* users:(("7DaysToDieServe",pid=142064,fd=23)) ``` This might be a bug introduced by the game developers, but this definitely has nothing to do with how long the server has been running.

kerem commented

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

Author

Owner

@parasyte commented on GitHub (Jan 26, 2022):

I was able to fix the issue with the listening port. In my case, the game could not find steamclient.so. Updating the game files fixed it. Probably because the next server start fixed some hard links for steamcmd.

DESCRIPTION  PORT   PROTOCOL  LISTEN
Game         26900  udp       1
Game+2       26902  udp       2
Query        26900  tcp       1
Web Admin    8080   tcp       0
Telnet       8081   tcp       1

$ ss -tuplwn | grep 7DaysToDieServe
udp    UNCONN  768     0                   0.0.0.0:26900          0.0.0.0:*      users:(("7DaysToDieServe",pid=160356,fd=208))
udp    UNCONN  0       0                   0.0.0.0:26902          0.0.0.0:*      users:(("7DaysToDieServe",pid=160356,fd=27))
udp    UNCONN  0       0                      [::]:26902             [::]:*      users:(("7DaysToDieServe",pid=160356,fd=31))
tcp    LISTEN  0       4096              127.0.0.1:8081           0.0.0.0:*      users:(("7DaysToDieServe",pid=160356,fd=23))
tcp    LISTEN  0       4096                0.0.0.0:26900          0.0.0.0:*      users:(("7DaysToDieServe",pid=160356,fd=214))

Even with the query port listening, monitor never gets a response from the server. I confirmed that no packets are sent back with tcpdump. I also tried sending the protocol-valve stuff with netcat and socat, and the server just will not respond at all to the query.

@parasyte commented on GitHub (Jan 26, 2022): I was able to fix the issue with the listening port. In my case, the game could not find `steamclient.so`. Updating the game files fixed it. Probably because the next server start fixed some hard links for steamcmd. ``` DESCRIPTION PORT PROTOCOL LISTEN Game 26900 udp 1 Game+2 26902 udp 2 Query 26900 tcp 1 Web Admin 8080 tcp 0 Telnet 8081 tcp 1 ``` ``` $ ss -tuplwn | grep 7DaysToDieServe udp UNCONN 768 0 0.0.0.0:26900 0.0.0.0:* users:(("7DaysToDieServe",pid=160356,fd=208)) udp UNCONN 0 0 0.0.0.0:26902 0.0.0.0:* users:(("7DaysToDieServe",pid=160356,fd=27)) udp UNCONN 0 0 [::]:26902 [::]:* users:(("7DaysToDieServe",pid=160356,fd=31)) tcp LISTEN 0 4096 127.0.0.1:8081 0.0.0.0:* users:(("7DaysToDieServe",pid=160356,fd=23)) tcp LISTEN 0 4096 0.0.0.0:26900 0.0.0.0:* users:(("7DaysToDieServe",pid=160356,fd=214)) ``` Even with the query port listening, `monitor` never gets a response from the server. I confirmed that no packets are sent back with `tcpdump`. I also tried sending the `protocol-valve` stuff with netcat and socat, and the server just will not respond at all to the query.

kerem commented

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

Author

Owner

@parasyte commented on GitHub (Jan 26, 2022):

Whew! I got it working. It looks like 7 Days to Die no longer supports the UDP protocol-valve for gamedig or gsquery, so you have to switch the monitor mode to TCP to get it working.

E.g. I added this line to my common.cfg:

querymode="5"

And now it's all good:

$ ./sdtdserver monitor                                        
[  OK  ] Monitoring sdtdserver: Checking session: OK                              
[  OK  ] Monitoring sdtdserver: Querying port: tcp: 0.0.0.0:26900 : 0/1: OK

This should really be changed in the default config: github.com/GameServerManagers/LinuxGSM@fdfeae1fcd/lgsm/config-default/config-lgsm/sdtdserver/_default.cfg (L137-L144)

@parasyte commented on GitHub (Jan 26, 2022): Whew! I got it working. It looks like 7 Days to Die no longer supports the UDP `protocol-valve` for gamedig or gsquery, so you have to switch the monitor mode to TCP to get it working. E.g. I added this line to my `common.cfg`: ```ini querymode="5" ``` And now it's all good: ``` $ ./sdtdserver monitor [ OK ] Monitoring sdtdserver: Checking session: OK [ OK ] Monitoring sdtdserver: Querying port: tcp: 0.0.0.0:26900 : 0/1: OK ``` This should really be changed in the default config: https://github.com/GameServerManagers/LinuxGSM/blob/fdfeae1fcdccb89f55e41ca33e964bbcb035d2ce/lgsm/config-default/config-lgsm/sdtdserver/_default.cfg#L137-L144

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Jun 3, 2023):

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

@github-actions[bot] commented on GitHub (Jun 3, 2023): This issue 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:55:15 +03:00

[PR #2413] [MERGED] Hotfix v19.8.2 #3639