Jump to content

[41.73]Error when logging in to the server "Malformed packet detected. Type 21."


MONKEY_GAMING

Recommended Posts

7 минут назад, Борода сказал:

В настоящее время это вызвало модами, которые были сломаны обновлением, один из выпусков — «Moar Can Openers»
. Я проверил, включен ли у вас этот мод, и он является его владельцем.

Странно получается, администраторы могут зайти на сервер. We will then sit and watch which mods still break the game

Edited by MONKEY_GAMING
Link to comment
Share on other sites

47 minutes ago, Beard said:

This is currently caused by mods which were broken by the update, one known one is "Moar Can Openers"
I recommend checking if you have that mod enabled and disabling it.

Do you know when this will be fixed? I'm having the same problem, also I'm not sure how to go about finding the broken mod without possibly corrupting my save file or losing my modded items.

Link to comment
Share on other sites

53 minutes ago, Beard said:

This is currently caused by mods which were broken by the update, one known one is "Moar Can Openers"
I recommend checking if you have that mod enabled and disabling it.

We don't run that mod (or any mod for that matter) but we're constantly getting this error, and also frequent crashes server-side. It's you, not mods.

Link to comment
Share on other sites

1 hour ago, robingraves said:

We don't run that mod (or any mod for that matter) but we're constantly getting this error, and also frequent crashes server-side. It's you, not mods.

Well, do you have any mods on the server?

Link to comment
Share on other sites

1 hour ago, slavik_the_slav said:

Do you know when this will be fixed? I'm having the same problem, also I'm not sure how to go about finding the broken mod without possibly corrupting my save file or losing my modded items.

I would assume once the mod author fixes the mod issue it would be fixed. So I don't have an answer for that will be.

Link to comment
Share on other sites

5 minutes ago, Beard said:

Well, do you have any mods on the server?

No, it's a vanilla server, as I said in the initial response.

 

It was kicking players with the "malformed packet" error, and then crashed completely (twice).

 

I'm attaching the console output at the moment of the crash.

crash.txt

Link to comment
Share on other sites

Thats unusual, can you make sure to open the 8766 and 8767 ports in your firewall and router settings?
Since the crash log seems to be related to Steam, and those two ports are the only ones Steam uses
As for the malformed packet error,  which type do you get?

Link to comment
Share on other sites

Quote

WARN : General     , 1660081673773> 16.106.065> GameServer.kick> The player Pig was kicked. The reason was UI_Policy_Kick, UI_ValidationFailed_Type1
LOG  : General     , 1660081673773> 16.106.065> 1660081673773 znet: Java_zombie_core_raknet_RakNetPeerInterface_disconnect
WARN : Network     , 1660081673773> 16.106.065> UdpEngine.decode> GOT PACKET FROM UNKNOWN CONNECTION guid=292734562634220835 packetId=5
WARN : Network     , 1660081673774> 16.106.065> UdpEngine.decode> GOT PACKET FROM UNKNOWN CONNECTION guid=292734562634220835 packetId=5
LOG  : Network     , 1660081673774> 16.106.066> Received packet type=Vehicles connection is null.
LOG  : Network     , 1660081673774> 16.106.066> Received packet type=PlayWorldSound connection is null.
WARN : Network     , 1660081673796> 16.106.088> UdpEngine.decode> GOT PACKET FROM UNKNOWN CONNECTION guid=292734562634220835 packetId=5
WARN : Network     , 1660081673806> 16.106.098> UdpEngine.decode> GOT PACKET FROM UNKNOWN CONNECTION guid=292734562634220835 packetId=5
WARN : Network     , 1660081673806> 16.106.098> UdpEngine.decode> GOT PACKET FROM UNKNOWN CONNECTION guid=292734562634220835 packetId=7

LOG  : General     , 1660081674250> 16.106.541> 1660081674250 znet: OnValidateAuthTicketResponse response=6 SteamID=76561198155580552
LOG  : General     , 1660081674250> 16.106.542> 1660081674250 znet: Auth failed response=6 state=2 SteamID=76561198155580552
LOG  : General     , 1660081674250> 16.106.542> 1660081674250 znet: Sending auth fail message
DEBUG: Multiplayer , 1660081674291> 16.106.583> ItemTransactionManager.receiveOnServer> remove processed [ 1948528394 : -1 => -1 ]
LOG  : General     , 1660081674352> 16.106.644> 1660081674352 znet: Finally disconnected client 76561198155580552
DEBUG: Multiplayer , 1660081674782> 16.107.074> ItemTransactionManager.receiveOnServer> set accepted [ 646590075 : -1 => -1 ]
LOG  : General     , 1660081675052> 16.107.344> 1660081675052 znet: OnP2PSessionRequest

 

look this... the server is kicking everyone.. and then crash and close... anyone went through this

Link to comment
Share on other sites

Could you tell me where to find the log file, I want to share to find out what the actual problem is.  I play on someone else's server and when I enter the game, I have the same error. :unsure:

Edited by Brainsy
Link to comment
Share on other sites

13 hours ago, Beard said:

Thats unusual, can you make sure to open the 8766 and 8767 ports in your firewall and router settings?
Since the crash log seems to be related to Steam, and those two ports are the only ones Steam uses
As for the malformed packet error,  which type do you get?

1x type1, 2x type4 and the rest type22

Ports are open.

Link to comment
Share on other sites

8 hours ago, raydough said:

I'm experiencing this same issue, "Malformed packet detected type 21" I am running mods but, I'm ABLE TO CONNECT to the hosted MP server I run with my ADMIN, but none of the standard users can connect.

Because admins are exempt from errors such as these, as mentioned the issue is currently caused by mods

 

8 hours ago, Brainsy said:

Could you tell me where to find the log file, I want to share to find out what the actual problem is.  I play on someone else's server and when I enter the game, I have the same error. :unsure:

Do any other users get the errors too?

 

2 hours ago, robingraves said:

1x type1, 2x type4 and the rest type22

Ports are open.

1 and 4 can be caused by mods which give users weird abilities or increase their power for example.

Type 22 is being investigated, would recommend disabling that one for now

Link to comment
Share on other sites

30 minutes ago, Beard said:

1 and 4 can be caused by mods which give users weird abilities or increase their power for example.


Type 22 is being investigated, would recommend disabling that one for now

 

In our setup only admin level accounts have paranormal abilities/powerups/odd trait combos, regular players do not.

 

I'll try your Type 22 recommendation, although I'd like to remind the kicks aren't the only problem.

 

Server crashes every 20-30 minutes, this time it's a different error, attaching.

 

 

 

crash 2.txt

Link to comment
Share on other sites

2 minutes ago, robingraves said:

 

In our setup only admin level accounts have paranormal abilities/powerups/odd trait combos, regular players do not.

 

I'll try your Type 22 recommendation, although I'd like to remind the kicks aren't the only problem.

 

Server crashes every 20-30 minutes, this time it's a different error, attaching.

 

 

 

crash 2.txt 721 B · 0 downloads

Can I ask what operating system the server is hosted on? And how was it installed exactly?

Link to comment
Share on other sites

23 minutes ago, Beard said:

Can I ask what operating system the server is hosted on? And how was it installed exactly?

Relaying at this point:

 

Supervisor OS is Debian, platform is pterodactyl.io, server was installed through the official egg.

Was running without problems on the day of the update (pre-update).

Link to comment
Share on other sites

21 minutes ago, robingraves said:

Scratch my last message, I got ahold of a fresh crash log - contains more info that might help you. Sorry for not attaching it earlier.

hs_err_pid36.log 251.98 kB · 0 downloads

Thanks for the log, could you also share the core dump as well? It is mentioned in this error log.
"Core dump will be written. Default location: /home/container/core"

We are currently still investigating this issue.

Link to comment
Share on other sites

11 minutes ago, Beard said:

Thanks for the log, could you also share the core dump as well? It is mentioned in this error log.
"Core dump will be written. Default location: /home/container/core"

We are currently still investigating this issue.

The "core" file is 50 gigabytes. I'm trying to somehow facilitate a d/l for it for you.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...