FDWATCH problem

[Creo 27]

SYSERR: May 21 03:38:84 :: Process: FDWATCH: peer null in event: ident 22
SYSERR: May 21 03:38:84 :: Process: FDWATCH: peer null in event: ident 23
SYSERR: May 21 03:38:84 :: Process: FDWATCH: peer null in event: ident 23
SYSERR: May 21 03:38:84 :: Process: FDWATCH: peer null in event: ident 23
SYSERR: May 21 03:38:84 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: May 21 03:38:84 :: Process: FDWATCH: peer null in event: ident 24

[Creo 27]

up

[Creo 27]

anyone...

[Aerrow 42]

I have too.

[wezt 99]

Hi.

Try to backtrace core files with gdb (in case if you are using freebsd). Bactrace results probably will help you, or will help someone to help you.

[skill178 19]

up

[TheMt2 12]

Other sysser please.

(Auth, channel1, db, game99)

[flygun 356]

you get this error before or after turning off the channels ?

[TheMt2 12]

you get this error before or after turning off the channels ?

That's a silly question ...The channel can only communicate error if it is closed ...

 

Just send us all sysser please (Auth, channel1 (core1,2,3,4,5), db, game99)

exemple : /usr/metin2/auth/sysser.txt

Edited July 24, 2015 by TheMt2

[flygun 356]

lol this error appears when a core or channel turns off ... he got 6 errors that means 6 cores closed at the same time

[TheMt2 12]

The error causes the closure.
You have said that the error appears after closing, these not the same: o

[JIntors 8]

Did you create characters and guilds from db? Or what did you copy paste in new line ?