Jump to content

Recommended Posts

HEllo everyone i using vanilla core and i have little problem i dont know why.. can anyone help me please ?
error and screens:
error :
SYSERR: Jan 29 21:26:47 :: socket_connect: HOST localhost:26842, could not connect.
SYSERR: Jan 29 21:26:50 :: socket_connect: HOST localhost:26842, could not connect.
SYSERR: Jan 29 21:26:53 :: socket_connect: HOST localhost:26842, could not connect.
SYSERR: Jan 29 21:26:56 :: socket_connect: HOST localhost:26842, could not connect.
SYSERR: Jan 29 21:26:59 :: socket_connect: HOST localhost:26842, could not connect.
SYSERR: Jan 29 21:27:02 :: socket_connect: HOST localhost:26842, could not connect.
SYSERR: Jan 29 21:27:05 :: socket_connect: HOST localhost:26842, could not connect.


g99 :
SYSERR: Jan 29 21:46:32 :: ChildLoop: AsyncSQL: query failed: Out of range value for column 'time' at row 1 (query: INSERT INTO bootlog (time, hostname, channel) VALUES(NOW(), 'game99', 99) errno: 1264)
SYSERR: Jan 29 21:51:35 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.

DB :
SYSERR: Jan 29 21:17:40 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Jan 29 21:17:40 :: Load: DirectQuery failed(SELECT IP_FROM, IP_TO, COUNTRY_NAME FROM iptocountry)
SYSERR: Jan 29 21:17:47 :: Process: FDWATCH: peer null in event: ident 20
SYSERR: Jan 29 21:17:50 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: Jan 29 21:17:52 :: Process: FDWATCH: peer null in event: ident 22
SYSERR: Jan 29 21:17:54 :: Process: FDWATCH: peer null in event: ident 20
SYSERR: Jan 29 21:17:54 :: Process: FDWATCH: peer null in event: ident 23
SYSERR: Jan 29 21:27:06 :: pid_init:
Start of pid: 1300

SYSERR: Jan 29 21:27:06 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Jan 29 21:27:06 :: Load: DirectQuery failed(SELECT IP_FROM, IP_TO, COUNTRY_NAME FROM iptocountry)
SYSERR: Jan 29 21:30:38 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Jan 29 21:34:34 :: pid_init:
Start of pid: 919

SYSERR: Jan 29 21:34:34 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Jan 29 21:34:35 :: Load: DirectQuery failed(SELECT IP_FROM, IP_TO, COUNTRY_NAME FROM iptocountry)
SYSERR: Jan 29 21:37:51 :: pid_init:
Start of pid: 973

SYSERR: Jan 29 21:37:51 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Jan 29 21:37:51 :: socket_bind: bind: Address already in use
SYSERR: Jan 29 21:40:54 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Jan 29 21:46:22 :: pid_init:
Start of pid: 919

SYSERR: Jan 29 21:46:22 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Jan 29 21:46:22 :: Load: DirectQuery failed(SELECT IP_FROM, IP_TO, COUNTRY_NAME FROM iptocountry)
SYSERR: Jan 29 21:51:35 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Jan 29 22:00:52 :: pid_init:
Start of pid: 930


SYSERR: Jan 30 08:54:29 :: socket_connect: HOST localhost:26842, could not connect.
SYSERR: Jan 30 08:54:29 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Jan 30 08:54:30 :: load: ANI directory = (null)
SYSERR: Jan 30 08:54:30 :: pid_deinit:

In conzole

Assertion failed: (!ms_singleton), function singleton, file ./../../common/singleton.h, line 13.
Abort trap

 

 

 

Link to comment
https://metin2.dev/topic/20515-vanilla-core-cant-connect/
Share on other sites

  • Replies 0
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Don't use any images from : imgur, turkmmop, freakgamers, inforge, hizliresim... Or your content will be deleted without notice...
Use : https://metin2.download/media/add/

Please use https://metin2.download/ when uploading files smaller than 100MB, otherwise the approval will take longer due to manual upload.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • 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.