Talk:It's a hARDA world LOTR Server/@comment-90.215.125.121-20170603123425/@comment-25612015-20170604075330

The root cause is that another user (Jo428) connected with incorrect starting position, which leads to a server freeze in both KCauldron and Thermos.

There were 2 issues:


 * Thermos says it is stopping the server but does not exit the system process. My monitoring software did not catch this kind of "zombie" freeze: now it should


 * When a user has an incorrect starting position, my monitoring software can usually autofix it to its spawn point (bed). It works in 95% of the cases encountered, except lately with __Boi__ and Jo428: I have to fix this manually until I can write a better NBT file handling tool...

So, now the server should be able to auto restart in these cases, but will freeze each time one of these antibiotic resistant incorrect starting position player logs in...