[Crash] Request to access thread dumps from Java due to server crash

The Aternos forums are now deprecated

Learn more about this change here.

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

  • Hello, so I have a PaperMC 1.15.2 server with a few plugins and I've been rarely seeing this occasion where the server will start up, and then say it's crashed while starting up. This can also happen if the server has been running for some time. When I inspect the log, sometimes it'll show a "watchdog thread death" or sometimes nothing to indicate an error. I've also checked the "crash-reports" folder to see if there's anything but I only see a crash report that happened over a month ago for a different reason. I thought it was due to plugins but this glitch seems very inconsistent (as in happening once every 20 server starts) and there's no errors to imply that it came from any plugins.

    Anyways, I want to know if there's a way to view the thread dumps from Java that may generate, because the Minecraft server logs aren't telling the whole story and while I understand there's a few files that are guarded for privacy sake, it's quite frustrating to not be able to precisely tell what's going on.

  • To give an example of when it crashed with the watchdog error, I have a snippet of what it looked like:

    [13:05:41 ERROR]: Main thread terminated by WatchDog due to hard crash
    java.lang.ThreadDeath: null
    at java.lang.Thread.stop(Thread.java:853) [?:1.8.0_252]
    at net.minecraft.server.v1_15_R1.MinecraftServer.stop(MinecraftServer.java:736) ~[minecraft_server.jar:git-Paper-375]
    at net.minecraft.server.v1_15_R1.DedicatedServer.stop(DedicatedServer.java:753) ~[minecraft_server.jar:git-Paper-375]
    at net.minecraft.server.v1_15_R1.MinecraftServer.close(MinecraftServer.java:712) ~[minecraft_server.jar:git-Paper-375]
    at org.bukkit.craftbukkit.v1_15_R1.util.ServerShutdownThread.run(ServerShutdownThread.java:28) ~[minecraft_server.jar:git-Paper-375]

  • I'll take a look to see what's going on. In any case, I still feel that having access to the thread dumps or any other logs besides the server log would be much more helpful in diagnosing the problem. Alternatively, having a way to track the memory usage would also be helpful.

  • Roman

    Closed the thread.