Mordhau
Mordhau Merch
Check out our merch shop!

Server Stability

56 8

Also, your ports are fine if there is not an error message like "Steam authentification failed". If this message is not in your logs then all is good. Also if the logs say XXX is listening to port XXXX then it's fine aswell.

This freeze state has nothing to do with ports I am pretty sure now after debugging and pinging the servers the whole time while being in the freeze state. It looks like the server network drivers crash and then the servers are stuck in an endless state

6 1
  • 11 May '19
 Jiuqi

https://pastebin.com/MvEEFfeY

This is my error message

Poor english Sorry

4 0
  • 13 May '19
 DGT

The problem still exists, I've already tried everything without success

2 1

I just had a lesson learned with self-hosting these servers. I'm running a windows server 2016 VM with the -log flag and was having what seemed like random crashes... There weren't any system resource constraints or network limitations. So to test, I would connect, have a friend connect, random people would connect to this hoard server. Trying to figure out what was going on. So when I would die or the map was switching I would switch over to the logs through RDP and it just seemed to keep happening. I would watch the logs, see nothing change and have to press enter to keep the server moving and see a huge queue of connection accepted messages attempting to be sent out. (100s of these errors) I would see server tick is taking too long errors as well. Again, no system resource or network constraints...

I would try to Mc-Groogle^TM search without any luck on the connection accepted errors or the abnormally high tick rate messages with both mordhau and other unreal engine 4 dedicated servers. So, I would mess with settings adding more configurations to the launch bat file, spin it up again and all would seem fine... until I went to review the logs. I had a friend over and showed him what's going on.

"The server seems to freeze until I press enter randomly."
"Do you have quick edit enabled? That will freeze the application when you click into and try to highlight text in the window...."

Turned out I quick-edit being enabled by default on windows was causing my log window to freeze the app when clicking into it. I am not sure if there is a similar issue with Linux based servers.

Fix action:
right click log window > properties > uncheck 'quick edit mode' > relaunch server

I was dumb.PNG

I was dumb 2.PNG

I feel dumb. This was causing me a lot of headaches with spinning up my servers. I hope this helps someone out there. There is a possibility the devs can disable this for us noob server admins.

56 8

That is a really good track down report. It could help fixing the issues on Linux too.

56 8

Yes, because of your bug report we were able to fix the servers on our side aswell on Linux.
Can be closed.

2 1

It's silly. I wonder how many people that have been complaining about generic server errors have been encountering this kind of thing.

4 0
  • 1
  • 14 May '19
 DGT

@Infravider.comDominicIllu said:
Yes, because of your bug report we were able to fix the servers on our side aswell on Linux.
Can be closed.

What exactly did you do?

Edit:
Ok, I solved the problem. I am using easy-wi for the administration of my gameservers. Easy-wi is using symlinks to prevent that massive space waste. The problem was, that the default config files from the original installation was not replaced at the slave installations. Due to the outdated DefaultConfig the BeaconDriver was not loaded and accordingly the error message came.

56 8

@DGT

that is some issues too maybe we should make a faq.

Our issue was that we emulated the screen with Node.JS and that somehow blocked the window like on Windows even tho it's Linux. We fixed it by adjusting several parts of the starting process/node js daemon.

22 0
  • 16 May '19
 PBSPowerbits

after some gaming and server runs full, i get

Fatal error!

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x00000180
[2019.05.16-09.50.08:121][982]LogNet: NotifyAcceptingConnection accepted from: 79.211.174.157:58187
[2019.05.16-09.50.08:121][982]LogNet: Invalid ConnectionlessHandler (0) or StatelessConnectComponent (0); can't accept connections.
[2019.05.16-09.50.09:121][ 42]LogNet: NotifyAcceptingConnection accepted from: 79.211.174.157:58187
[2019.05.16-09.50.09:121][ 42]LogNet: Invalid ConnectionlessHandler (0) or StatelessConnectComponent (0); can't accept connections.

22 0
  • 16 May '19
 PBSPowerbits

after some gaming and server runs full, i get

Fatal error!

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x00000180
[2019.05.16-09.50.08:121][982]LogNet: NotifyAcceptingConnection accepted from: 79.211.174.157:58187
[2019.05.16-09.50.08:121][982]LogNet: Invalid ConnectionlessHandler (0) or StatelessConnectComponent (0); can't accept connections.
[2019.05.16-09.50.09:121][ 42]LogNet: NotifyAcceptingConnection accepted from: 79.211.174.157:58187
[2019.05.16-09.50.09:121][ 42]LogNet: Invalid ConnectionlessHandler (0) or StatelessConnectComponent (0); can't accept connections.

29 3

[2019.05.17-14.54.33:541][514]LogNet: Warning: UNetConnection::Tick: Connection TIMED OUT. Closing connection.. Elapsed: 10.00, Real: 10.00, Good: 10.00, DriverTime: 296.28, Threshold: 10.00, [UNetConnection] RemoteAddr: 180.65.161.83:55372, Name: IpConnection_53, Driver: GameNetDriver IpNetDriver_6, IsServer: YES, PC: BP_SkirmishPlayerController_C_9, Owner: BP_SkirmishPlayerController_C_9, UniqueId: MordhauOnlineSubsystem:76561198285182544
[2019.05.17-14.54.33:541][514]LogNet: NetworkFailure: ConnectionTimeout, Error: 'UNetConnection::Tick: Connection TIMED OUT. Closing connection.. Elapsed: 10.00, Real: 10.00, Good: 10.00, DriverTime: 296.28, Threshold: 10.00, [UNetConnection] RemoteAddr: 180.65.161.83:55372, Name: IpConnection_53, Driver: GameNetDriver IpNetDriver_6, IsServer: YES, PC: BP_SkirmishPlayerController_C_9, Owner: BP_SkirmishPlayerController_C_9, UniqueId: MordhauOnlineSubsystem:76561198285182544'
[2019.05.17-14.54.33:542][514]LogNet: UNetConnection::Close: [UNetConnection] RemoteAddr: 180.65.161.83:55372, Name: IpConnection_53, Driver: GameNetDriver IpNetDriver_6, IsServer: YES, PC: BP_SkirmishPlayerController_C_9, Owner: BP_SkirmishPlayerController_C_9, UniqueId: MordhauOnlineSubsystem:76561198285182544, Channels: 196, Time: 2019.05.17-14.54.33
[2019.05.17-14.54.33:542][514]LogNet: UChannel::Close: Sending CloseBunch. ChIndex == 0. Name: [UChannel] ChIndex: 0, Closing: 0 [UNetConnection] RemoteAddr: 180.65.161.83:55372, Name: IpConnection_53, Driver: GameNetDriver IpNetDriver_6, IsServer: YES, PC: BP_SkirmishPlayerController_C_9, Owner: BP_SkirmishPlayerController_C_9, UniqueId: MordhauOnlineSubsystem:76561198285182544
[2019.05.17-14.54.33:557][515]LogMordhauGameSession: Verbose: Freed slot occupied by 76561198285182544
[2019.05.17-14.54.33:557][515]LogMordhauGameSession: Verbose: Updating server session
[2019.05.17-14.54.35:207][606]LogWindows: Error: === Critical error: ===
[2019.05.17-14.54.35:207][606]LogWindows: Error:
[2019.05.17-14.54.35:207][606]LogWindows: Error: Fatal error!
[2019.05.17-14.54.35:208][606]LogWindows: Error:
[2019.05.17-14.54.35:208][606]LogWindows: Error: Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x000019a0
[2019.05.17-14.54.35:208][606]LogWindows: Error:
[2019.05.17-14.54.35:208][606]LogWindows: Error: [Callstack] 0x00007ff79b4c98fd MordhauServer-Win64-Shipping.exe!UnknownFunction []
[2019.05.17-14.54.35:208][606]LogWindows: Error: [Callstack] 0x00007ff79b4054a9 MordhauServer-Win64-Shipping.exe!UnknownFunction []
[2019.05.17-14.54.35:209][606]LogWindows: Error: [Callstack] 0x00007ff79b3ec701 MordhauServer-Win64-Shipping.exe!UnknownFunction []
[2019.05.17-14.54.35:209][606]LogWindows: Error: [Callstack] 0x00007ff79b3ed63f MordhauServer-Win64-Shipping.exe!UnknownFunction []
[2019.05.17-14.54.35:209][606]LogWindows: Error: [Callstack] 0x00007ff79b405ef6 MordhauServer-Win64-Shipping.exe!UnknownFunction []
[2019.05.17-14.54.35:209][606]LogWindows: Error: [Callstack] 0x00007ff79b405f2e MordhauServer-Win64-Shipping.exe!UnknownFunction []
[2019.05.17-14.54.35:210][606]LogWindows: Error: [Callstack] 0x00007ff79bfffb2c MordhauServer-Win64-Shipping.exe!UnknownFunction []
[2019.05.17-14.54.35:210][606]LogWindows: Error: [Callstack] 0x00007ff79bfe82bf MordhauServer-Win64-Shipping.exe!UnknownFunction []
[2019.05.17-14.54.35:210][606]LogWindows: Error: [Callstack] 0x00007ff79c4f752c MordhauServer-Win64-Shipping.exe!UnknownFunction []
[2019.05.17-14.54.35:211][606]LogWindows: Error: [Callstack] 0x00007ff79b5a42c3 MordhauServer-Win64-Shipping.exe!UnknownFunction []
[2019.05.17-14.54.35:211][606]LogWindows: Error: [Callstack] 0x00007ff79b5ab0e1 MordhauServer-Win64-Shipping.exe!UnknownFunction []
[2019.05.17-14.54.35:211][606]LogWindows: Error: [Callstack] 0x00007ff79c4fda81 MordhauServer-Win64-Shipping.exe!UnknownFunction []
[2019.05.17-14.54.35:211][606]LogWindows: Error: [Callstack] 0x00007ff79c4fedf7 MordhauServer-Win64-Shipping.exe!UnknownFunction []
[2019.05.17-14.54.35:211][606]LogWindows: Error: [Callstack] 0x00007ff79c2b9039 MordhauServer-Win64-Shipping.exe!UnknownFunction []
[2019.05.17-14.54.35:212][606]LogWindows: Error: [Callstack] 0x00007ff79c1eeaa5 MordhauServer-Win64-Shipping.exe!UnknownFunction []
[2019.05.17-14.54.35:212][606]LogWindows: Error: [Callstack] 0x00007ff79b20868e MordhauServer-Win64-Shipping.exe!UnknownFunction []
[2019.05.17-14.54.35:212][606]LogWindows: Error: [Callstack] 0x00007ff79b20db3e MordhauServer-Win64-Shipping.exe!UnknownFunction []
[2019.05.17-14.54.35:213][606]LogWindows: Error: [Callstack] 0x00007ff79b20dbba MordhauServer-Win64-Shipping.exe!UnknownFunction []
[2019.05.17-14.54.35:213][606]LogWindows: Error: [Callstack] 0x00007ff79b215079 MordhauServer-Win64-Shipping.exe!UnknownFunction []
[2019.05.17-14.54.35:213][606]LogWindows: Error: [Callstack] 0x00007ff79cc259a6 MordhauServer-Win64-Shipping.exe!UnknownFunction []
[2019.05.17-14.54.35:213][606]LogWindows: Error: [Callstack] 0x00007ffb121d7974 KERNEL32.DLL!UnknownFunction []
[2019.05.17-14.54.35:214][606]LogWindows: Error: [Callstack] 0x00007ffb12e4a271 ntdll.dll!UnknownFunction []
[2019.05.17-14.54.35:214][606]LogWindows: Error:
[2019.05.17-14.54.35:221][606]LogExit: Executing StaticShutdownAfterError
[2019.05.17-14.54.35:239][606]LogWindows: FPlatformMisc::RequestExit(1)
[2019.05.17-14.54.35:241][606]Log file closed, 05/17/19 22:54:35
不知道這個錯誤是不是來自隊友傷害改成-100所產生的伺服器崩潰問題
但這個改法 能讓隊友回血 很好玩大眾 也覺得 這玩法很創新
因這設定讓我伺服器具有獨特創新玩法 獲得好評 希望官方不要改 但能修復伺服器崩潰 問題I don't know if this error is caused by a server crash caused by teammate damage changed to -100.
But this change can make teammates return blood. It’s fun to play with the public. I think this game is very innovative.
Because of this setting, my server has a unique and innovative gameplay. I’m hoping that I don’t want to change the official but I can fix the server crash.