Jump to content

FDWatch Problem PLEASE HELP


Recommended Posts

Hello,

Each time i run my game, it shuts down in 2 minutes.

I have checked mob_proto. ban word and everything. I recently added some quests and some items , tried removing items it didnt work

PLEASE i need your help.

Thank you 

This is my Channel1 Sysser : 

 

 

SYSERR: Jun 14 12:18:11 :: ForAttrRegionFreeAngle: SECTREE_MANAGER::ForAttrRegion - Unhandled exception. MapIndex: 21

SYSERR: Jun 14 12:18:11 :: ForAttrRegionFreeAngle: SECTREE_MANAGER::ForAttrRegion - Unhandled exception. MapIndex: 1
SYSERR: Jun 14 12:18:36 :: socket_bind: bind: Address already in use
SYSERR: Jun 14 12:18:54 :: HandshakeProcess: handshake retry limit reached! (limit 32 character !NO CHARACTER!)
SYSERR: Jun 14 12:19:06 :: ItemLoad: cannot create item by vnum 63532 (name Infinity id 13245431)
SYSERR: Jun 14 12:19:06 :: ItemLoad: cannot create item by vnum 49185 (name Infinity id 13245385)
SYSERR: Jun 14 12:19:20 :: ItemLoad: cannot create item by vnum 63548 (name Tiny id 13257971)
SYSERR: Jun 14 12:19:22 :: HandshakeProcess: handshake retry limit reached! (limit 32 character !NO CHARACTER!)

And DB Sysser error : 

 

 

SYSERR: Jun 14 12:18:59 :: Process: FDWATCH: peer null in event: ident 20

SYSERR: Jun 14 12:19:26 :: Process: FDWATCH: peer null in event: ident 21
 

 

Link to comment
Share on other sites

  • Replies 2
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

SYSERR: Jun 14 12:18:11 :: ForAttrRegionFreeAngle: SECTREE_MANAGER::ForAttrRegion - Unhandled exception. MapIndex: 21

SYSERR: Jun 14 12:18:11 :: ForAttrRegionFreeAngle: SECTREE_MANAGER::ForAttrRegion - Unhandled exception. MapIndex: 1

SYSERR: Jun 14 12:18:36 :: socket_bind: bind: Address already in use

The first is probably just telling you that a core (probably the one commonly known as first, the one that has no map_indexes in the CONFIG file) doesn't have the maps inside its CONFIG file. BTW i don't think that's relevant.

The second one is telling you that there's already a core running, so the address is already in use.

Check the running processes by typing: ps x.

EDIT: the first problem seems like something else, check this:

74ce532e31.png

Edited by Metin2 Dev
Core X - External 2 Internal
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

Announcements



×
×
  • Create New...

Important Information

Terms of Use / Privacy Policy / Guidelines / We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.