Log & crash update

The Aternos forums are now deprecated

Learn more about this change here.

For help regarding Aternos, we recommend you to visit our support center.

    • Official Post

    Hey hey!


    Over the last few days we've released some smaller and bigger updates as part of our "Log & crash update". It's now finished and we want to give you some information about the changes.


    As we've learned over the last years, Minecraft servers fail often, especially on start up (over 300,000 times on Aternos in a month). Failed server starts are by far the most frequent support problem. Most of these failed starts are due to misconfiguration, e.g. incompatible plugins or mods or small mistakes in configuration files etc. Almost all of these problems add an error message to the server log.


    Almost 2 years ago we've developed and published mclo.gs to help users with this problem and us and everybody else in supporting those users by providing an easy solution to share your log. It also had a basic feature to detect problems in the log automatically and suggest a solution. It's not used much besides our support, so we wanted to bring automated suggestions closer to our users.


    Therefore we've developed our latest update with the following changes:

    • All new log parsing and analysing for mclo.gs (including software and version detection)
    • Improved log sharing usability on Aternos
    • Log parsing and printing on the Aternos log and console pages (colors!)
    • Automated problem detection on the log page with some automatic solutions
    • Log problem count indicator in the navigation (red number)
    • New server status (crashed + saving)

    Some more in-depth information about some changes:


    Server status

    We often where asked why their server was stopped by our system and if there was anything wrong with our system randomly stopping servers. This was due to the status cycle that they were seeing on a failed start:

    Offline -> Loading -> Starting -> Stopping -> Offline

    We've now added two more status codes to reflect what's actually happening and make it clearer to the user when their server failed to start/crashed on startup. The status cycle for a failed start is now:

    Offline -> Loading -> Starting -> Saving -> Crashed

    We've split the stopping status in two different phases just like the starting (loading + starting). The new crashed status helps us to makes it clearer for the user why their server "stopped" and point them to the log. It actually behaves the same as offline. The status for a successful start is now:

    Offline -> Loading -> Starting -> Online -> Stopping -> Saving -> Offline


    Log parsing and analysing (for developers!)

    Behind the log parsing and analysis both on mclo.gs and on Aternos is a common library that we've developed in the last weeks for this purpose. We've already open sourced mclo.gs last year and this library is open source as well. You can find all of that on our Github:

    We're open for improvements or new problem detection & solution suggestions!


    We need your help!

    The latest features (especially the problems and solutions) still require translation in lots of different languages. If you want to help us (Thank you!), you can translate Aternos here: https://crowdin.com/project/aternos


    That's it for now, we hope you enjoy our latest update!

    Your Aternos-Team <3

  • Julian

    Closed the thread.