starred/LinuxGSM

Fork 0

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

[GH-ISSUE #3337] [BUG] vhserver monitor kills functioning server that has peers connected #2295

New issue

Closed

opened 2026-02-27 03:02:04 +03:00 by kerem · 11 comments

kerem commented

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

Owner

Originally created by @yuzupup on GitHub (Mar 5, 2021).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/3337

User Story

As a server administrator, I would like ./vhserver monitor to not kill my server when the server is in good health.

Basic info

Distro: Ubuntu 18.04.1 LTS
Game: Valheim (build 6315977)
Command: ./vhserver monitor
LinuxGSM version: Valheim v21.1.3

Further Information

I regularly run ./vhserver monitor (every 10 minutes).

As of SteamCMD build 6315977, it seems to be killing my server while peers are connected. The query on port 2457 fails after the normal retry period with the following message:

[  OK  ] Monitoring vhserver: Checking session: OK
[ FAIL ] Monitoring vhserver: Querying port: gsquery: 192.168.86.50:2457 : 60/5: FAIL
[  OK  ] Stopping vhserver: Graceful: CTRL+c: 8: OK
[  OK  ] Starting vhserver: Valheim Server

To Reproduce

Steps to reproduce the behaviour:

Start a server.
Have at least one peer connect.
Run ./vhserver monitor until the query is no longer delayed.
Observe that it terminates the server.

Expected behaviour

monitor does not kill a server with peers connected.

Originally created by @yuzupup on GitHub (Mar 5, 2021). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/3337 ## User Story As a server administrator, I would like ./vhserver monitor to not kill my server when the server is in good health. ## Basic info * **Distro:** Ubuntu 18.04.1 LTS * **Game:** Valheim (build `6315977`) * **Command:** `./vhserver monitor` * **LinuxGSM version:** Valheim v21.1.3 ## Further Information I regularly run ./vhserver monitor (every 10 minutes). As of SteamCMD build `6315977`, it seems to be killing my server while peers are connected. The query on port 2457 fails after the normal retry period with the following message: ``` [ OK ] Monitoring vhserver: Checking session: OK [ FAIL ] Monitoring vhserver: Querying port: gsquery: 192.168.86.50:2457 : 60/5: FAIL [ OK ] Stopping vhserver: Graceful: CTRL+c: 8: OK [ OK ] Starting vhserver: Valheim Server ``` ## To Reproduce Steps to reproduce the behaviour: 1) Start a server. 2) Have at least one peer connect. 3) Run ./vhserver monitor until the query is no longer delayed. 4) Observe that it terminates the server. ## Expected behaviour monitor does not kill a server with peers connected.

kerem

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

closed this issue
added the
type: bug

command: monitor

distro: Ubuntu

game: Valheim
labels

kerem commented

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

Author

Owner

@yuzupup commented on GitHub (Mar 5, 2021):

I am curious if 2457 is the port that should be checked after the update. I had peers connecting via port 2456, and they were unable to connect. Not specifying the port let them connect.

@yuzupup commented on GitHub (Mar 5, 2021): I am curious if 2457 is the port that should be checked after the update. I had peers connecting via port 2456, and they were unable to connect. Not specifying the port let them connect.

kerem commented

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

Author

Owner

@sebastianus78 commented on GitHub (Mar 5, 2021):

Same issue
Ubuntu 18.04
LinuxGSM version: v21.1.3
Local build: 6315977

udp 1536 0 0.0.0.0:2457 0.0.0.0:* 26190/./valheim_ser

after delay monitoring on 0.0.0.0:2457 fails, server restarts.
removing the monitoring from crontab seems to be the easiest workarround

@sebastianus78 commented on GitHub (Mar 5, 2021): Same issue Ubuntu 18.04 LinuxGSM version: v21.1.3 Local build: 6315977 udp 1536 0 0.0.0.0:2457 0.0.0.0:* 26190/./valheim_ser after delay monitoring on 0.0.0.0:2457 fails, server restarts. removing the monitoring from crontab seems to be the easiest workarround

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Mar 6, 2021):

Recent Valheim update has broken query monitor. You can disable query in the LinuxGSM settings.

@dgibbs64 commented on GitHub (Mar 6, 2021): Recent Valheim update has broken query monitor. You can disable query in the LinuxGSM settings.

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Mar 6, 2021):

Previous release

tcp        0      0 178.79.168.193:35253    155.133.248.38:27039    ESTABLISHED 671/./valheim_serve
udp        0      0 0.0.0.0:2457            0.0.0.0:*                           671/./valheim_serve

=================================

./query_gsquery.py -a "178.79.168.193" -p "2457" -e "protocol-valve"

OK: b'\xff\xff\xff\xffI\x11LinuxGSM - Debian 10 Test Server\x00LinuxGSM - Debian 10 Test Serve\x00valheim\x00\x00\x00\x00\x00@\x00dl\x01\x001.0.0.0\x00\xb1\x98\t\x0b\xa04\x18\xd0@@\x010.145.6\x00*\xa0\r\x00\x00\x00\x00\x00'

new release

tcp        0      0 139.162.210.57:51007    162.254.196.67:27035    ESTABLISHED 407404/./valheim_se
udp        0      0 0.0.0.0:2457            0.0.0.0:*                           407404/./valheim_se
udp6       0      0 :::2456                 :::*                                407404/./valheim_se

gsquery Raw Output
=================================

./query_gsquery.py -a "139.162.210.57" -p "2457" -e "protocol-valve"

ERROR: Unable to receive

@dgibbs64 commented on GitHub (Mar 6, 2021): Previous release ``` tcp 0 0 178.79.168.193:35253 155.133.248.38:27039 ESTABLISHED 671/./valheim_serve udp 0 0 0.0.0.0:2457 0.0.0.0:* 671/./valheim_serve ``` ```gsquery Raw Output ================================= ./query_gsquery.py -a "178.79.168.193" -p "2457" -e "protocol-valve" OK: b'\xff\xff\xff\xffI\x11LinuxGSM - Debian 10 Test Server\x00LinuxGSM - Debian 10 Test Serve\x00valheim\x00\x00\x00\x00\x00@\x00dl\x01\x001.0.0.0\x00\xb1\x98\t\x0b\xa04\x18\xd0@@\x010.145.6\x00*\xa0\r\x00\x00\x00\x00\x00' ``` new release ``` tcp 0 0 139.162.210.57:51007 162.254.196.67:27035 ESTABLISHED 407404/./valheim_se udp 0 0 0.0.0.0:2457 0.0.0.0:* 407404/./valheim_se udp6 0 0 :::2456 :::* 407404/./valheim_se ``` ``` gsquery Raw Output ================================= ./query_gsquery.py -a "139.162.210.57" -p "2457" -e "protocol-valve" ERROR: Unable to receive ```

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Mar 6, 2021):

Tested further it appears to work. But maybe its taking a longer time to get started on boot. I will extend the query delay

edit: OK so a query delay is 5 mins already. I will have to connect to a server and query to see what is happening. This makes no sense currently

edit2: I have joined my server and the query is still working. At this time I am unable to replicate this issue. The only things I can think if is that because its early access there are bugs or a mod is being used that interfere with the query

@dgibbs64 commented on GitHub (Mar 6, 2021): Tested further it appears to work. But maybe its taking a longer time to get started on boot. I will extend the query delay edit: OK so a query delay is 5 mins already. I will have to connect to a server and query to see what is happening. This makes no sense currently edit2: I have joined my server and the query is still working. At this time I am unable to replicate this issue. The only things I can think if is that because its early access there are bugs or a mod is being used that interfere with the query

kerem commented

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

Author

Owner

@jmechnich commented on GitHub (Mar 6, 2021):

I am experiencing the same issue on Debian Testing since a reboot a few days ago. I have just noticed that I am using gsquery in contrast to gamedig, so this might be the underlying cause. Can anyone confirm this ?

Edit: gamedig appears to be the default query mode set in the config file, falling back to gsquery as gamedig is not installed.

@jmechnich commented on GitHub (Mar 6, 2021): I am experiencing the same issue on Debian Testing since a reboot a few days ago. I have just noticed that I am using `gsquery` in contrast to `gamedig`, so this might be the underlying cause. Can anyone confirm this ? Edit: `gamedig` appears to be the default query mode set in the config file, falling back to `gsquery` as `gamedig` is not installed.

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Mar 6, 2021):

@jmechnich its worth trying with just gsquery and just gamedig to see if that is the issue. They are both querying in the same manner so unsure why this would be an issue

@dgibbs64 commented on GitHub (Mar 6, 2021): @jmechnich its worth trying with just gsquery and just gamedig to see if that is the issue. They are both querying in the same manner so unsure why this would be an issue

kerem commented

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

Author

Owner

@Gibbo3771 commented on GitHub (Mar 9, 2021):

Recent Valheim update has broken query monitor. You can disable query in the LinuxGSM settings.

@dgibbs64 How? I have no line to disable and docs don't specify any line to add.

My server is dying whenever gamedig fails to query.

EDIT:

I see it :)

## Query mode
# 1: session only
# 2: gamedig (gsquery fallback)
# 3: gamedig
# 4: gsquery
# 5: tcp
querymode="1"  # Set to 1
querytype="protocol-valve"

@Gibbo3771 commented on GitHub (Mar 9, 2021): > Recent Valheim update has broken query monitor. You can disable query in the LinuxGSM settings. @dgibbs64 How? I have no line to disable and docs don't specify any line to add. My server is dying whenever gamedig fails to query. EDIT: I see it :) ``` ## Query mode # 1: session only # 2: gamedig (gsquery fallback) # 3: gamedig # 4: gsquery # 5: tcp querymode="1" # Set to 1 querytype="protocol-valve" ```

kerem commented

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

Author

Owner

@sebastianus78 commented on GitHub (Mar 10, 2021):

public="0" causes monitoring gsquery to fail.
public="1" works with qsquery

@sebastianus78 commented on GitHub (Mar 10, 2021): public="0" causes monitoring gsquery to fail. public="1" works with qsquery

kerem commented

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

Author

Owner

@h3o66 commented on GitHub (Mar 15, 2021):

this should be fixed with the connected PR, feel free to test it.

@h3o66 commented on GitHub (Mar 15, 2021): this should be fixed with the connected PR, feel free to test it.

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Mar 17, 2022):

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 (Mar 17, 2022): 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.