Huge problem with "??????????????"

[Aioria 11]

Hi!
I get this error and crash client after that:

syserr empty in client and just these errors in server.

CH1

Spoiler

SYSERR: May 17 12:15:05.873789 :: pid_init: 
Start of pid: 2920

SYSERR: May 17 12:15:10.217262 :: GetMotionFileName: Motion: dog_god have not motlist.txt vnum(20202) folder(dog_god)
SYSERR: May 17 12:15:10.217262 :: GetMotionFileName: Motion: dog_god have not motlist.txt vnum(20202) folder(dog_god)
SYSERR: May 17 12:15:10.217273 :: GetMotionFileName: Motion: dog_god have not motlist.txt vnum(20202) folder(dog_god)
SYSERR: May 17 12:15:10.218041 :: GetMotionFileName: Motion: dog_god have not motlist.txt vnum(20206) folder(dog_god)
SYSERR: May 17 12:15:10.218054 :: GetMotionFileName: Motion: dog_god have not motlist.txt vnum(20206) folder(dog_god)
SYSERR: May 17 12:15:10.218065 :: GetMotionFileName: Motion: dog_god have not motlist.txt vnum(20206) folder(dog_god)
SYSERR: May 17 12:15:10.218367 :: GetMotionFileName: Motion: dog_god have not motlist.txt vnum(20210) folder(dog_god)
SYSERR: May 17 12:15:10.218379 :: GetMotionFileName: Motion: dog_god have not motlist.txt vnum(20210) folder(dog_god)
SYSERR: May 17 12:15:10.218390 :: GetMotionFileName: Motion: dog_god have not motlist.txt vnum(20210) folder(dog_god)
SYSERR: May 17 12:15:10.223947 :: GetMotionFileName: Motion: pig_young2 have not motlist.txt vnum(34017) folder(pig_young2)
SYSERR: May 17 12:15:10.223960 :: GetMotionFileName: Motion: pig_young2 have not motlist.txt vnum(34017) folder(pig_young2)
SYSERR: May 17 12:15:10.223971 :: GetMotionFileName: Motion: pig_young2 have not motlist.txt vnum(34017) folder(pig_young2)
SYSERR: May 17 12:15:10.224047 :: GetMotionFileName: Motion: dog_young2 have not motlist.txt vnum(34018) folder(dog_young2)
SYSERR: May 17 12:15:10.224072 :: GetMotionFileName: Motion: dog_young2 have not motlist.txt vnum(34018) folder(dog_young2)
SYSERR: May 17 12:15:10.224084 :: GetMotionFileName: Motion: dog_young2 have not motlist.txt vnum(34018) folder(dog_young2)
SYSERR: May 17 12:15:10.224220 :: GetMotionFileName: Motion: lion_young2 have not motlist.txt vnum(34020) folder(lion_young2)
SYSERR: May 17 12:15:10.224232 :: GetMotionFileName: Motion: lion_young2 have not motlist.txt vnum(34020) folder(lion_young2)
SYSERR: May 17 12:15:10.224243 :: GetMotionFileName: Motion: lion_young2 have not motlist.txt vnum(34020) folder(lion_young2)
SYSERR: May 17 12:20:13.856332 :: Process: SEQUENCE 3bd81000 mismatch 0xaf != 0x64 header 254
SYSERR: May 17 12:20:13.856342 :: Process: SEQUENCE_LOG [UNKNOWN]-------------
	[254 : 0xaf]

SYSERR: May 17 12:25:49.126062 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: May 17 12:25:49.649240 :: pid_deinit: 
End of pid

 

DB

Spoiler

SYSERR: May 17 12:15:00.803742 :: pid_init: 
Start of pid: 2910

SYSERR: May 17 12:25:46.548407 :: Process: FDWATCH: peer null in event: ident 20
SYSERR: May 17 12:25:49.739306 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: May 17 12:25:52.48440 :: Process: FDWATCH: peer null in event: ident 22
SYSERR: May 17 12:25:53.639347 :: Process: FDWATCH: peer null in event: ident 23
SYSERR: May 17 12:25:56.638516 :: Process: FDWATCH: peer null in event: ident 24
SYSERR: May 17 12:25:59.210870 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: May 17 12:25:59.243664 :: pid_deinit: 
End of pid

 

the others are clean.

I know about the "FDWATCH" warning, but i don't think it can cause this error.

Can you guys help me to resolve?

Edited August 25, 2022 by Metin2 Dev
Core X - External 2 Internal

[OtherChoice 81]

There is some inconsistecies in packet definition of game and client binary. This error usually occurs when one binary expects the size of a packet to be actually larger or smaller than it is:
game source

typedef unsigned char       BYTE;
struct test_packet
{
  BYTE header;
  BYTE value1;
  int value2;
  unsigned long value3;
} TTestPacket;

client source

typedef unsigned char       BYTE;
struct test_packet
{
  BYTE header;
  BYTE value1;
  long value2;
  unsigned long value3;
} TTestPacket;

As you can see both packet looks almost the same but sizeof(int) is 4 and sizeof(long) is 8. So when one binary copys values pointed by const void* using sizeof(TTestPacket) it will either be missing 4 bytes or have 4 more. Long story short check all your packets declarations

[Aioria 11]

Oh! Glad to know! Thank you! But how can i know which one i should check? they're a lot, and no don't know where to start

[OtherChoice 81]

This error started showing after some changes i suppose, check changes you did like new systems and so on. If you instead got a new clean server and client source maybe you should start considering they're either different releases or not so clean.

[Aioria 11]

I'll try! Thank you a lot!