Login Problem

[iRETEMAG 137]

Syserr db:

SYSERR: Feb  8 01:40:28 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Feb  8 01:40:28 :: pid_deinit: 
End of pid

SYSERR: Feb  8 01:42:48 :: pid_init: 
Start of pid: 866

SYSERR: Feb  8 01:42:48 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Feb  8 01:42:49 :: Load:  DirectQuery failed(SELECT login FROM block_exception)
SYSERR: Feb  8 01:42:53 :: ProcessPackets: Unknown header (header: 139 handle: 0 length: 3)
SYSERR: Feb  8 01:42:54 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: Feb  8 01:42:55 :: ProcessPackets: Unknown header (header: 139 handle: 0 length: 3)
SYSERR: Feb  8 01:42:56 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: Feb  8 01:42:57 :: ProcessPackets: Unknown header (header: 139 handle: 0 length: 3)
SYSERR: Feb  8 01:42:58 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: Feb  8 01:42:59 :: ProcessPackets: Unknown header (header: 139 handle: 0 length: 3)
SYSERR: Feb  8 01:43:00 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: Feb  8 01:43:01 :: ProcessPackets: Unknown header (header: 139 handle: 0 length: 3)
SYSERR: Feb  8 01:43:02 :: Process: FDWATCH: peer null in event: ident 21

[Syron 294]

SYSERR: Feb  8 01:40:28 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.

SYSERR: Feb  8 01:40:28 :: pid_deinit: 

 

Explication: You closed the specified core/game. [ can't close the server. ]

 

SYSERR: Feb  8 01:42:48 :: pid_init: 

Start of pid: 866

 

Explication: core/game started. [ can't close the server. ]

 

SYSERR: Feb  8 01:42:48 :: Start: TABLE_POSTFIX not configured use default

 

Explication: TABLE_POSTFIX is not configured under each CONFIG file , not a bad thing. "false-error" [ can't close the server. ]

 

SYSERR: Feb  8 01:42:49 :: Load:  DirectQuery failed(SELECT login FROM block_exception)

 

Explication: The MySQL server can't read these informations ( no privileges / internet problems a bit ) [ can't close the server. ]

 

SYSERR: Feb  8 01:42:53 :: ProcessPackets: Unknown header (header: 139 handle: 0 length: 3) [ can't close the server. ]

 

Explication: The packets between client -> server are not the same. [ can't close the server. ] [  read this for further information ]

 

SYSERR: Feb  8 01:43:02 :: Process: FDWATCH: peer null in event: ident 21 [ will close the server! ]

 

Explication: You implemented wrong things under /data/monster folder or MySQL mob_proto.

How to test if this is the problem?: Remove values from 'folder' column in MySQL of the latest mobs/monsters/npcs you added by yourself and the latest folders in data/monster and test if it works.

[pbuzz 31]

 

Explication: You implemented wrong things under /data/monster folder or MySQL mob_proto.

How to test if this is the problem?: Remove values from 'folder' column in MySQL of the latest mobs/monsters/npcs you added by yourself and the latest folders in data/monster and test if it works.

 

not every error with fdwatch can be fixed by adding/removing things from mob_proto table

 

@Asta: post ch1 (core1) syserr + syslog & do a core debugg with gdb and post result here

[Traceur3RUN 73]

 

 

Explication: You implemented wrong things under /data/monster folder or MySQL mob_proto.

How to test if this is the problem?: Remove values from 'folder' column in MySQL of the latest mobs/monsters/npcs you added by yourself and the latest folders in data/monster and test if it works.

 

not every error with fdwatch can be fixed by adding/removing things from mob_proto table

 

@Asta: post ch1 (core1) syserr + syslog & do a core debugg with gdb and post result here

 

from db conf.txt

TABLE_POSTFIX= "" 

change to 

TABLE_POSTFIX = " "

 

SYSERR: Feb  8 01:42:49 :: Load:  DirectQuery failed(SELECT login FROM block_exception)

add id to mysql tables block_exception sometjing 1 or what you want