-
|
This only started after today's update. Looks like monitor script is failing on port 2457 query, which reboots server. You can see from the log file timestamps the frequency of it. I started playing today after 21:00UTC and experienced the disconnects from the reboots. Included below is output of one of the log files. At this time I disabled the monitor script in crontab, and no issues seen while playing. Any suggestions for a fix would be appreciated. -rw-rw-r-- 1 vhserver vhserver 4811 Feb 26 09:30 vhserver-script-2021-02-26-09:30:01.log
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
this sounds like the same issue I'm seeing (#3327), just with more specific info than I provided :-) I'm disabling my monitor cronjob for now. There was a patch today that changed how dedicated servers work, namely "disconnecting" them from a Steam system, which I bet is related to the port. I'm also seeing that in the Steam client Servers list, where I added my server, it's not showing up during list refreshes now. Guessing if you set public to 0 it doesn't open the query port, which would otherwise be used to communicate to Steam that the server exists/is running, so the monitor check fails because it thinks it's needed? |
Beta Was this translation helpful? Give feedback.
-
|
My server starts with the public 0 option, so that doesn't seem to make a difference. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, I was not clear on that. When I said, "Guessing if you set public to 0..." I meant the generic you, not you specifically. To be more clear: With this most recent update to the Valheim server, if a server is run with public 0, I expect that it is not running anything on what used to be the query port. I ran 'netstat -atunp | grep valheim' and got this: So it looks like it is opening the query port, but maybe it's not reporting the same data that it used to if public is 0. To my understanding, the query port is what the server would use so Steam can see it, know it exists, put it in the community servers lists in game, etc. Given that this new patch (patch notes here: https://store.steampowered.com/news/app/892970?emclan=103582791463217109&emgid=3058478454632856786) made changes to dedicated private servers (so like yours, riseteon1, and mine, both with public set to 0), and specifically that they no longer use Steam Datagram Relay, I expect that if the LGSM monitor script is looking for that in some degree it's getting a false negative, thus restarting the server. I could definitely be way off the mark, of course. I just think it's interesting that with an app update that made what appears to be some fundamental changes to the way it does or doesn't use a particular third-party service, and then monitor breaking right after the update was applied on my system at least. |
Beta Was this translation helpful? Give feedback.
-
|
Cool, I see what you mean. Yea, that makes sense. For now I'm running ok without monitor, so hopefully lgsm will figure out a fix so I can use it again. |
Beta Was this translation helpful? Give feedback.
this sounds like the same issue I'm seeing (#3327), just with more specific info than I provided :-)
I'm disabling my monitor cronjob for now. There was a patch today that changed how dedicated servers work, namely "disconnecting" them from a Steam system, which I bet is related to the port. I'm also seeing that in the Steam client Servers list, where I added my server, it's not showing up during list refreshes now. Guessing if you set public to 0 it doesn't open the query port, which would otherwise be used to communicate to Steam that the server exists/is running, so the monitor check fails because it thinks it's needed?