Hercules Elf Bot - Aug 11, 2008 9:05
Originally posted by [b]akd[/b]
http://www.eathena.ws/board/index.php?autocom=bugtracker&showbug=2040
Few times ago, I had had a disk space problem that makes my database refusing connexions after the initial connexion of my eA server (125xx).
In this type of case, the problem is the following:
-> Login server is refusing connexion most of the time,
-> Char server is refusing connexion,
-> Players that were connected to the map server are able to continue to play. Even if data can't be saved.
No servers make crash reports...
This is a big mistake.
If I've well understood the way eA works, data are saved every x seconds. If the mysql server become reachable again, you can have synchronisation issues, duplicate items and so on.
In my case, the database refused connexion from 1am and I was able to correct the problem at 5pm. The problem was so high, I have to reboot the hosting system.
Correct behavior is the follow:
When database become unreachable, all players should be kicked and map server should (choose the right answer):
-> disconnect /voiceless (pretty bad)
-> make an error log then disconnect (better, but in which way if you put most of the log of because of lag issues?)
There is no way at all the server continue to process, it needs to shut down to preserve database integrity (and in that way allow nobody to whining that they lost some experience etc.)
This post has been edited by akd: Aug 11 2008, 02:07 AM