Game qui Down

[stan-online 1]

Bonjour a tous !

 

Voilà, aujourd'hui après avoir ré installer mon dédié avec de nouvelles files, mon serveur ne marcher pas, je me suis dis que c'était au niveau des ports, et bien non.

 

En cherchant un peut, j'ai remarquer que mon game se downer...

 

ks357266# ps
 PID  TT  STAT      TIME COMMAND
 946  v0  Is+    0:00.00 /usr/libexec/getty Pc ttyv0
 947  v1  Is+    0:00.00 /usr/libexec/getty Pc ttyv1
 948  v2  Is+    0:00.00 /usr/libexec/getty Pc ttyv2
 949  v3  Is+    0:00.00 /usr/libexec/getty Pc ttyv3
 950  v4  Is+    0:00.00 /usr/libexec/getty Pc ttyv4
 951  v5  Is+    0:00.00 /usr/libexec/getty Pc ttyv5
 952  v6  Is+    0:00.00 /usr/libexec/getty Pc ttyv6
 953  v7  Is+    0:00.00 /usr/libexec/getty Pc ttyv7
84873  p0  Ss     0:00.03 -csh (csh)
84877  p0  R+     0:00.00 ps
82552  p1- I      0:01.65 ./db
82554  p1- I      0:03.81 ./auth (game)
ks357266#

 

Après plusieurs essaie, je n'es pas trouver la solution.

 

Si quelqu'un as une idée je suis preneur !

 

Merci.

 

Cordialement,

[antok 62]

Au moment du crash tu as une erreur sur putty ?

 

Sinon regarde les logs des channels que tu lance

[stan-online 1]

Non justement, le truck c'est que sa ne se démare même pas,

 

Exemple : Je fait "./close.sh'' ensuite ''./start.sh'' dirrectement après je fais ''ps'' Et sa me fais la même chose

 PID  TT  STAT      TIME COMMAND
 946  v0  Is+    0:00.00 /usr/libexec/getty Pc ttyv0
 947  v1  Is+    0:00.00 /usr/libexec/getty Pc ttyv1
 948  v2  Is+    0:00.00 /usr/libexec/getty Pc ttyv2
 949  v3  Is+    0:00.00 /usr/libexec/getty Pc ttyv3
 950  v4  Is+    0:00.00 /usr/libexec/getty Pc ttyv4
 951  v5  Is+    0:00.00 /usr/libexec/getty Pc ttyv5
 952  v6  Is+    0:00.00 /usr/libexec/getty Pc ttyv6
 953  v7  Is+    0:00.00 /usr/libexec/getty Pc ttyv7
84873  p0  Ss     0:00.03 -csh (csh)
87839  p0  S      0:00.46 ./db
87841  p0  S      0:00.09 ./auth (game)
87847  p0  R+     0:00.00 ps
ks357266#

 

Aucune erreur sur putty.

 

Logs channels :

SYSERR: Aug 17 14:18:07 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '" "' at line 1
query: SELECT id FROM guild" "
SYSERR: Aug 17 14:18:09 :: ReadSpecialDropItemFile: ReadSpecialDropItemFile : there is no item 91056 : node red_dragon
SYSERR: Aug 17 14:18:09 :: Boot: cannot load SpecialItemGroup: locale/germany/special_item_group.txt
SYSERR: Aug 17 14:21:54 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Aug 17 14:21:54 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '" "' at line 1
query: SELECT id FROM guild" "
SYSERR: Aug 17 14:21:55 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Aug 17 14:21:55 :: socket_block: fcntl: nonblock: Bad file descriptor
SYSERR: Aug 17 14:23:44 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '" "' at line 1
query: SELECT id FROM guild" "
SYSERR: Aug 17 14:23:46 :: ReadSpecialDropItemFile: ReadSpecialDropItemFile : there is no item 91056 : node red_dragon
SYSERR: Aug 17 14:23:46 :: Boot: cannot load SpecialItemGroup: locale/germany/special_item_group.txt
SYSERR: Aug 17 15:35:11 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '" "' at line 1
query: SELECT id FROM guild" "
SYSERR: Aug 17 15:35:13 :: ReadSpecialDropItemFile: ReadSpecialDropItemFile : there is no item 91056 : node red_dragon
SYSERR: Aug 17 15:35:13 :: Boot: cannot load SpecialItemGroup: locale/germany/special_item_group.txt

[antok 62]

Règle toutes les erreurs du syserr et ça devrait marcher x)

[stan-online 1]

Merci Antok

 

Résultat : Je ré installe mon dédié.