132 posts
15 reputation

IGN: MatthewKilp
By MatthewKilp » over 3 years ago

It has recently come to my server that our creative server has recently been crashing a lot, and also when crashing, not restarting itself correctly, causing the server to go offline and become unreachable for fairly long periods of time.

Based on the time that this started, I am fairly certain that the root cause of this issue was Dynmap: this is a web based map that allows people to view a map of Creative from their web browser. This was initially installed to allow players who had lost plots a while back to view the map, and try to locate any prominant structures they remember building, in order to try and make it easier to recover plots. However, this has lead to the server crashing,

I have paused the map render for now to check if this fixes the issues, however by now the main map has been fully rendered so this should be usable by players to help locate plots.

Once again. I'm sorry that I didn't notice the server was crashing - I'm currently trying to connect at least 2 times a day to ensure everything is online and working properly. If this is to happen again, please notify me as soon as possible to reduce the downtime: skype - matthewkilpatrick12345 ; email: [email protected]

UPDATE: The issues persisted after this point. I feel that they are now fixed, and have come to the conclusion that the following factors were infact the issue:

  1. A plot fairly near spawn had a load of floating pressure plates on it. In one of the crashes I witnessed today, the co-ordinates of this plot were included (I seem to remember it being classed as a physics issue in the logs), and this plot crashed my client a few times too. I have wiped the content of this plot and banned the user who it belonged to for intention to crash the server / lag players.
  2. A plugin that was installed onto the Creative server on the last day of 2016 that automatically launched fireworks throughout the day to celebrate new year. Before this point, I can’t remember server crashes this regular, so I believe that this may have been part of the issue. This has now been removed.

Need support? Email [email protected] or open a thread on our website.