Closed PapaMooDoo closed 3 years ago
Can you attach the log in its entirety? From very first start to when the issue shows up in the log.
Yes, for sure!
thanks for your answer while weekend :) Sascha-Valheim.csv
I have been experiencing the same since the image update. I upped the ram & CPU as well, but it keeps disconnecting and I think its mostly when I am not connected to it for a while
https://gist.github.com/nitishdhar/bcf5549e251d054cce7a9d5de51ea136
Hey There, Great work, very easy to setup on docker/compose/swarm. Ran out of the box pretty well. Great image!
I am getting this error as well from some users connecting.
I found something that might be adjusted in the image from this form: https://valheimbugs.featureupvote.com/suggestions/172771/read-here-my-dedicatedhosted-server-broke-after-patch
This is the relevant post text from that forum: _31 Mar Johan Sandström I managed to fix the ZRpc issue on my own, by changing the class m_timeout, from 30 seconds to 300 (in the file assemblyvalheim.dll). Now the game works again.
EDIT: I did find this file, it's located: /opt/valheim/server/valheim_server_Data/Managed I don't know how to edit it. Any thoughts?
See my errors below: May 2 20:34:22 /supervisord: valheim-server 05/02/2021 20:34:22: ZRpc timeout detected May 2 20:34:22 /supervisord: valheim-server 05/02/2021 20:34:22: Closing socket 76561198073504281 May 2 20:34:22 /supervisord: valheim-server 05/02/2021 20:34:22: send queue size:0 May 2 20:34:22 /supervisord: valheim-server 05/02/2021 20:34:22: Got status changed msg k_ESteamNetworkingConnectionState_None May 2 20:34:22 /supervisord: valheim-server 05/02/2021 20:34:22: Destroying abandoned non persistent zdo -570636977:3 owner -570636977 May 2 20:34:22 /supervisord: valheim-server 05/02/2021 20:34:22: Disposing socket May 2 20:34:22 /supervisord: valheim-server 05/02/2021 20:34:22: Disposing socket
Sincerely, Jared
@PapaMooDoo I went over the entire log but other than some nits can't really find anything wrong with your installation. Like
Apr 30 10:52:08 /supervisord: valheim-server Warning: failed to set thread priority: set failed for 8: -1: setpriority() failed
can be solved by providing -cap-add sys_nice
when starting the container. Now I don't think the Synology WebUI allows you to do that, it's likely something that has to be done on the cli. But I doubt that it's the reason for your timeout unless you have a super busy NAS. All this flag does is it gives the Valheim network thread more CPU priority. But the error you're getting means that the server hasn't received any data from the connecting client for more than half a minute. So I doubt your NAS is that busy.
@AlthaTechnology to edit any file of the server you'd have to load the dll into DnSpy on your desktop, update and save it there and then upload to the container. See https://steamcommunity.com/app/892970/discussions/0/3073117690255918314/ for more info. It is not something we can do on the container side of things since the container does not come with the dll (that would be illegal as the dll and all binary code is © Iron Gate) it is downloaded from Steam at runtime. Plus it would be overwritten during the next server update.
Closing for inactivity
I had a Valheimserver on my docker (@DS218+ with 10GB Ram) running the past few weeks. thanks for your work!
Now, my brother wanted a server for himself and his friends. So i deleted my working server (My mates and i didnt play anymore) and the saved world and pulled the latest version from today.
Now nobody can join the server. After 30sec Blackscreen the message came "Disconnected" in the dockerlog stands:
we try with our savegame and the Dockersettings, but got the same result. my brother lives in another town, so he isnt in my network. the ports are open in the DS-Firewall and the router. I dont know, why he coudnt join.
best regards!