Fatal Error and char-server REFUSED

[Petey Pablo 0]

Anyone can help me with this? Thank you very much!

 

[Fatal Error]: Servers are out of sync! recompile from scratch (25)
[Info]: Connection request of the char-server 'Hercules' @ 127.0.0.1:6121 (account: 'ragnarok1
', pass: 'ragnarok2
', ip: '127.0.0.1')
[Notice]: Unknown account (account: ragnarok1
, received pass: ragnarok2
, ip: 127.0.0.1)
[Notice]: Connection of the char-server 'YourRO' REFUSED.
[Info]: Closed connection from '127.0.0.1'.

 

Edited August 28, 2016 by Will Su

[Petey Pablo 0]

Any staff here in hercules? I need help

[Monsieur Panda 38]

You somehow broke the internet !

 

- Did you compile your client after your last update ?

- Are you sure about your database Login / password ?

[Petey Pablo 0]

Fixed fatal error. Only this closed connection problem after successfuly login then I got failed to connect.

 

[Info]: Connection request of the char-server 'Hercules' @ 127.0.0.1:6121 (account: 'ragnarok1', pass: 'ragnarok2', ip: '127.0.0.1')
[Notice]: Authentication accepted (account: ragnarok1, id: 1, ip: 127.0.0.1)
[Notice]: Connection of the char-server 'Hercules' REFUSED.
[Info]: Closed connection from '127.0.0.1'.

[WhiteEagle 6]

I got the same problem. 

I try to change in map and server.conf from 127.0.0.1 to host ip,

used a new account with S

and always the same error that the connection refused T_T

[Nysari 0]

I know this is a crazy old thread and OP has likely moved on -- but in case anyone else like me is searching for the "servers are out of sync!" error and finds this as the only question...

 

I had this issue and figured out a solution that worked for me and thought I'd share. In my case, I think I must have accidentally tried to recompile with the server still running which caused a whole kerfuffle that made the server not have a clean exit. "./athena-start stop" seemed to be working fine, but the servers were still technically running.

 

I ran "ps -ef | grep ragnarok" ("ragnarok" is my server user, so this may be different if you created an alternate name). This is what I saw even though my server was stopped:

ragnarok@revitaro-backend:~/Hercules/conf$ ps -ef | grep ragnarok
ragnarok 13489 18634  0 17:09 pts/1    00:00:00 ps -ef
ragnarok 13490 18634  0 17:09 pts/1    00:00:00 grep ragnarok
root     18632 18612  0 14:43 pts/1    00:00:00 sudo su ragnarok
root     18633 18632  0 14:43 pts/1    00:00:00 su ragnarok
ragnarok 18634 18633  0 14:43 pts/1    00:00:00 bash
ragnarok 22159     1  0 00:41 ?        00:00:15 ./login-server
ragnarok 22160     1  0 00:41 ?        00:00:13 ./char-server
ragnarok 22161     1  0 00:41 ?        00:01:44 ./map-server
ragnarok 23383     1  0 14:56 pts/1    00:00:01 ./login-server
ragnarok 29904     1  0 15:32 pts/1    00:00:01 ./login-server

Note the 3 processes for "./login-server" and the instances for "./char-server" and "./map-server" -- those are the problem children.

I killed them one by one using their process IDs (second column from the left).

ragnarok@revitaro-backend:~/Hercules/conf$ kill 22159
ragnarok@revitaro-backend:~/Hercules/conf$ kill 22160
ragnarok@revitaro-backend:~/Hercules/conf$ kill 22161
ragnarok@revitaro-backend:~/Hercules/conf$ kill 23383
ragnarok@revitaro-backend:~/Hercules/conf$ kill 29904

I cleaned it up a  bit -- but while running these the servers started emitting their standard shutdown messages (the ones you normally see with ./athena-start stop).

 

After doing this and a new configure packet ver, "make clean", and "make", my server worked normally again. Hopefully this helps someone else!