Dedicated not closing connections, not disconnecting properly, ghost players

https://pastebin.com/5xbH3dQB without mods, last player still online, still can't kick/disconnect, line 1227. Compared to the previous one(disabled "SteamNetworking"), this one had "LiteNetLib" disabled in serverconfig.

Hey @HaruRose, this should help you out 

 

This doesn't help that this bug wasn't in A20.7, where the last player stays online to the server and time is still going. The common support FAQ misses the point where the dedicated doesn't close connections. It's about the "Ping requested for unknown client". The common FAQ doesn't have a solution for the newly introduced error with any of these:
zombies chasing a disconnected invulnerable player, crashing which may lead to region corruption(linux only), falling through the map in long sessions(linux only), server hangs and long tick rates(linux only

17 hours ago, Jugginator said:

Hey @HaruRose, this should help you out 

 

 

You have an error that's directly fixed by the link I posted.

16 minutes ago, HaruRose said:

This doesn't help that this bug wasn't in A20.7, where the last player stays online to the server and time is still going. The common support FAQ misses the point where the dedicated doesn't close connections. It's about the "Ping requested for unknown client". The common FAQ doesn't have a solution for the newly introduced error with any of these:
zombies chasing a disconnected invulnerable player, crashing which may lead to region corruption(linux only), falling through the map in long sessions(linux only), server hangs and long tick rates(linux only

 

 

Do see if it helps, because many thousands of hours of testing was done on dedicated servers including linux and this hasn't been seen, so more troubleshooting and debugging (if needed) is needed. As it stands, this doesn't reproduce:

1) Run dedicated server

2) Have people join, disconnect

3) Players will still appear in the server list as connected, a yellow error will be spammed through the console.

 

Edited June 28, 2023 by Jugginator (see edit history)

Yes, your FAQ does fix the IOEXCEPTION: Too many files open.

I'm reporting a different bug in this thread - it just so happens that the last one wasn't fixed and is occuring as well. Please mark it as such.
The different bug I am reporting here is about ghost players, unclosed connections, zombies chasing disconnected players and "ping unknown client".

This is not a fix for windows dedicated servers. The logs are from windows servers. The effects of this A21 bug where ghost players are online, time still passes when no one is online still happens. A fix for this isn't listed in the FAQ as it is not present in A20.7, but in A21.

I went back and tried to reproduce the issue. I wasn't able to. Made a new world, new character and the issue did not occur. The issue only still happens on my RWG map, so it's quite a rare bug. No idea why this happens.

I have the same problem on a 317 RWG map updated to 324. The key exception in the logs is:

2023-06-29T20:08:43 1126.235 EXC Object reference not set to an instance of an object
  at QuestEventManager.QuestUnlockPOI (System.Int32 entityID, UnityEngine.Vector3 prefabPos) [0x0001e] in <faea3a5b1cd24d60977fa28c6573de8f>:0
  at Quest.HandleUnlockPOI (EntityPlayer player) [0x00038] in <faea3a5b1cd24d60977fa28c6573de8f>:0
  at QuestEventManager.HandlePlayerDisconnect (EntityPlayer player) [0x0001f] in <faea3a5b1cd24d60977fa28c6573de8f>:0
  at ConnectionManager.DisconnectClient (ClientInfo _cInfo, System.Boolean _bShutdown, System.Boolean _clientDisconnect) [0x0010e] in <faea3a5b1cd24d60977fa28c6573de8f>:0
  at ConnectionManager.Net_PlayerDisconnected (ClientInfo _cInfo) [0x00013] in <faea3a5b1cd24d60977fa28c6573de8f>:0
  at NetworkServerLiteNetLib.OnPlayerDisconnected (System.Int64 _peerConnectId) [0x00014] in <faea3a5b1cd24d60977fa28c6573de8f>:0
  at NetworkServerLiteNetLib+<>c__DisplayClass14_0.<StartServer>b__3 (System.Object _taskInfo) [0x00036] in <faea3a5b1cd24d60977fa28c6573de8f>:0
  at ThreadManager.UpdateMainThreadTasks () [0x0006c] in <faea3a5b1cd24d60977fa28c6573de8f>:0

 

My hunch was the latest patch POI updates broke this call back. Maybe ID changes? Removing all existing quests will throw this exception again, but then the DisconnectClient method completes successfully on log out. I reset the trader's daily quests to be safe and was able to accept a new quest and log out without issue.

 

Catch your exceptions in network resource code TFP!

@HaruRose
@BloodyGir
Is this still happening in A21 B324?

To me, this stopped happening the moment I used a new map. The one I had the problem on was made using RWG.

Same exact problem for me on b15. Players disconnect, their session hangs. Console is getting spammed with pings.

Theres one reproduction I've done on this, related to what @BourbonBeefcake mentioned, but not of what others are talking about. That one is a ticket currently to be looked into further.