Jump to content

Core1 crash after trying to log in :/


Recommended Posts

Hey There!

 

I installed the Kori Serverfiles + Client a few houres ago. I have the problem:

 

When I try to login with not existing login credentials, the game says: "Accountname or Password wrong" (GER: Accountname oder Passwort falsch). By trying to login with existing credentials, it always says all the time "Connecting to server..." (GER: Verbindung zum Server wird hergestellt...).

 

I looked in PuTTy and did "ps", so i found out that every time when I try to login with existing credentials, core 1 crashes. Core1 CH1 always crashs...

 

The syserr of core1 doesnt tell me anything:

 

 

Spoiler


SYSERR: Mar  7 19:02:52 :: BuildStateIndexToName: QUEST wrong quest state file for quest Eisland_W?chter
SYSERR: Mar  7 19:02:54 :: GetQuestStateIndex: QUEST wrong quest state file Eisland_W?chter.start
SYSERR: Mar  7 19:02:54 :: GetQuestStateIndex: QUEST wrong quest state file Eisland_W?chter.start
SYSERR: Mar  7 19:02:54 :: GetQuestStateIndex: QUEST wrong quest state file Eisland_W?chter.start

 

 

 

Here is the Syserr of auth:

 

 

Spoiler

 

SYSERR: Mar  7 19:02:52 :: pid_init:
Start of pid: 779

SYSERR: Mar  7 19:02:52 :: ChildLoop: AsyncSQL: query failed: Unknown column 'name' in 'field list' (query: SELECT name, text FROM string errno: 1054)
SYSERR: Mar  7 19:03:37 :: ChildLoop: AsyncSQL: query failed: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2) (query: SELECT PASSWORD('passwort'),password,securitycode,social_id,id,status,availDt - NOW() > 0,UNIX_TIMESTAMP(silver_expire),UNIX_TIMESTAMP(gold_expire),UNIX_TIMESTAMP(safebox_expire),UNIX_TIMESTAMP(autoloot_expire),UNIX_TIMESTAMP(fish_mind_expire),UNIX_TIMESTAMP(marriage_fast_expire),UNIX_TIMESTAMP(money_drop_rate_expire),UNIX_TIMESTAMP(create_time) FROM account WHERE login='kori' errno: 2002)
SYSERR: Mar  7 19:03:37 :: ChildLoop: AsyncSQL: retrying

 

 

 

 

 

 

and syserr of Database:

 

Spoiler

 

SYSERR: Mar  7 19:02:47 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Mar  7 19:03:36 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (61)
query: SELECT MAX(id) FROM item WHERE id >= 90000001 and id <= 100000000
SYSERR: Mar  7 19:03:36 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (61)
query: SELECT COUNT(*) FROM item WHERE id >= 90000001 AND id <= 100000000
SYSERR: Mar  7 19:03:36 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (61)
query: SELECT MAX(id) FROM item WHERE id >= 30000001 and id <= 40000000
SYSERR: Mar  7 19:03:36 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (61)
query: SELECT COUNT(*) FROM item WHERE id >= 30000001 AND id <= 40000000
SYSERR: Mar  7 19:03:36 :: Process: FDWATCH: peer null in event: ident 25
SYSERR: Mar  7 19:03:36 :: Process: FDWATCH: peer null in event: ident 24
SYSERR: Mar  7 19:03:37 :: ChildLoop: AsyncSQL: query failed: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2) (query: SELECT id,login,vnum,count,socket0,socket1,socket2,mall,why FROM item_award WHERE taken_time IS NULL and id > 0 errno: 2002)
SYSERR: Mar  7 19:03:37 :: ChildLoop: AsyncSQL: retrying
SYSERR: Mar  7 19:03:42 :: ChildLoop: MySQL connection was reconnected. querying locale set

 

 

 

 

 

User: kori, Pass: passwort are existing in database.

 

I thank everyone who can help me

:)

 

 

TY <3

Link to comment
Share on other sites

  • Replies 3
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

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.