Jump to content
×
×
  • Create New...
  • 0

problème db au lancement


MeeX

Question

Version des files  : team fr, game et db mainline 2014

 

 

 

Bonjour quand je start le serveur j'ai des :

 

AsyncSQK : connected to localhost (reconnect 1)

 

et le syslog de mon dossier db se remplit de la sorte :

 

SYSERR: Jul  8 20:12:42.643642 :: pid_init: 
Start of pid: 874

Jul  8 20:12:42.643700 :: connecting to MySQL server (player)
Jul  8 20:12:42.643706 :: CREATING DIRECT_SQL
Jul  8 20:12:42.643716 :: AsyncSQL: locale euckr
Jul  8 20:12:42.646152 :: CREATING MAIN_SQL
Jul  8 20:12:42.646164 :: AsyncSQL: locale euckr
Jul  8 20:12:42.646202 :: CREATING ASYNC_SQL
Jul  8 20:12:42.646233 :: AsyncSQL: locale euckr
Jul  8 20:12:42.646246 ::    OK
Jul  8 20:12:42.646262 :: connecting to MySQL server (account)
Jul  8 20:12:42.646266 :: CREATING DIRECT_SQL
Jul  8 20:12:42.646270 :: AsyncSQL: locale euckr
Jul  8 20:12:42.652456 :: CREATING MAIN_SQL
Jul  8 20:12:42.652479 :: AsyncSQL: locale euckr
Jul  8 20:12:42.652504 :: CREATING ASYNC_SQL
Jul  8 20:12:42.652512 :: AsyncSQL: locale euckr
Jul  8 20:12:42.652521 ::    OK
Jul  8 20:12:42.652534 :: connecting to MySQL server (common)
Jul  8 20:12:42.652537 :: CREATING DIRECT_SQL
Jul  8 20:12:42.652542 :: AsyncSQL: locale euckr
Jul  8 20:12:42.652873 :: CREATING MAIN_SQL
Jul  8 20:12:42.652882 :: AsyncSQL: locale euckr
Jul  8 20:12:42.652895 :: CREATING ASYNC_SQL
Jul  8 20:12:42.652902 :: AsyncSQL: locale euckr
Jul  8 20:12:42.652911 ::    OK
Jul  8 20:12:42.652921 :: connecting to MySQL server (hotbackup)
Jul  8 20:12:42.652924 :: CREATING DIRECT_SQL
Jul  8 20:12:42.652928 :: AsyncSQL: locale euckr
Jul  8 20:12:42.653307 :: CREATING MAIN_SQL
Jul  8 20:12:42.653317 :: AsyncSQL: locale euckr
Jul  8 20:12:42.653339 :: CREATING ASYNC_SQL
Jul  8 20:12:42.653347 :: AsyncSQL: locale euckr
Jul  8 20:12:42.653358 ::    OK
Jul  8 20:12:42.654864 :: ClientManager initialization.. 
Jul  8 20:12:42.655096 :: InitializeLocalization() - LoadLocaleTable(count:13)
Jul  8 20:12:42.655107 :: locale[uNKNOWN_KEY(SKILL_POWER_BY_LEVEL_TYPE0)] = 0 5 6 8 10 12 14 16 18 20 22 24
Jul  8 20:12:42.655111 :: locale[uNKNOWN_KEY(SKILL_POWER_BY_LEVEL_TYPE1)] = 0 5 6 8 10 12 14 16 18 20 22 24
Jul  8 20:12:42.655118 :: locale[uNKNOWN_KEY(SKILL_POWER_BY_LEVEL_TYPE2)] = 0 5 6 8 10 12 14 16 18 20 22 24
Jul  8 20:12:42.655127 :: locale[uNKNOWN_KEY(SKILL_POWER_BY_LEVEL_TYPE3)] = 0 5 6 8 10 12 14 16 18 20 22 24
Jul  8 20:12:42.655131 :: locale[uNKNOWN_KEY(SKILL_POWER_BY_LEVEL_TYPE4)] = 0 5 6 8 10 12 14 16 18 20 22 24
Jul  8 20:12:42.655134 :: locale[uNKNOWN_KEY(SKILL_POWER_BY_LEVEL_TYPE5)] = 0 5 6 8 10 12 14 16 18 20 22 24
Jul  8 20:12:42.655137 :: locale[uNKNOWN_KEY(SKILL_POWER_BY_LEVEL_TYPE6)] = 0 5 6 8 10 12 14 16 18 20 22 24
Jul  8 20:12:42.655141 :: locale[uNKNOWN_KEY(SKILL_POWER_BY_LEVEL_TYPE7)] = 0 5 6 8 10 12 14 16 18 20 22 24
Jul  8 20:12:42.655144 :: locale[LOCALE] = france
Jul  8 20:12:42.655151 :: Changed g_stLocale euckr to euckr
Jul  8 20:12:42.655156 :: SetLocale start
Jul  8 20:12:42.656344 :: 	--mysql_set_character_set(latin1)
Jul  8 20:12:42.656676 :: 	--mysql_set_character_set(latin1)
Jul  8 20:12:42.656756 :: 	--mysql_set_character_set(latin1)
Jul  8 20:12:42.656801 :: 	--mysql_set_character_set(latin1)
Jul  8 20:12:42.656841 :: 	--mysql_set_character_set(latin1)
Jul  8 20:12:42.656881 :: 	--mysql_set_character_set(latin1)

 

Merci d'avance

 

 

 

 

En postant ma demande d'aide, j'affirme avoir lu et accepté le règlement des demandes d'aides.

Edition signature : image trop grande.

Link to comment
  • Answers 4
  • Created
  • Last Reply

Top Posters For This Question

Popular Days

Top Posters For This Question

4 answers to this question

Recommended Posts

  • 0

on me dit sur le tchat que mon game est périmé, par contre comme c'est pas expliqué après la compilation, j'ai mis mon game dans share et db dans le dossier db après les avoir renommé car ils s'appellaient db_un chiffre et game_unchiffre est ce que c'est bon ?

Edition signature : image trop grande.

Link to comment
Guest
This topic is now closed to further replies.


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.