Server Crash occourd by your plugin
pthoelken opened this issue · 1 comments
I've already talked to a paper developer in discord and he told me, that the server crash last night is occourd by your plugin. May be you can help us in this case? Unfortunately I can't tell you any steps to reproduce the problem.
Thanks in advance for your investigation.
I am sorry, but I do not see where this is caused by my plugin.
There are the following things related to my plugin:
[02:11:49] [Minepacks-Connection-Pool housekeeper/WARN]: [at.pcgamingfreaks.MinepacksStandalone.libs.com.zaxxer.hikari.pool.HikariPool] Minepacks-Connection-Pool - Thread starvation or clock leap detected (housekeeper delta=1m3s839ms160µs229ns).
This is just a warning that the connection pool housekeeping task run about 1 minute delayed. I would expect this since your server stopped responding.
Than there is this:
[02:11:50] [Paper Watchdog Thread/ERROR]: Current Thread: Minepacks-Connection-Pool housekeeper
[02:11:50] [Paper Watchdog Thread/ERROR]: PID: 78 | Suspended: false | Native: false | State: TIMED_WAITING
[02:11:50] [Paper Watchdog Thread/ERROR]: Stack:
[02:11:50] [Paper Watchdog Thread/ERROR]: [email protected]/jdk.internal.misc.Unsafe.park(Native Method)
[02:11:50] [Paper Watchdog Thread/ERROR]: [email protected]/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:252)
[02:11:50] [Paper Watchdog Thread/ERROR]: [email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1661)
[02:11:50] [Paper Watchdog Thread/ERROR]: [email protected]/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1182)
[02:11:50] [Paper Watchdog Thread/ERROR]: [email protected]/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899)
[02:11:50] [Paper Watchdog Thread/ERROR]: [email protected]/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1056)
[02:11:50] [Paper Watchdog Thread/ERROR]: [email protected]/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1116)
[02:11:50] [Paper Watchdog Thread/ERROR]: [email protected]/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630)
[02:11:50] [Paper Watchdog Thread/ERROR]: [email protected]/java.lang.Thread.run(Thread.java:831)
Telling us that the Minepacks-Connection-Pool housekeeper thread is sleeping. Again, as expected, it just run 1 second ago and informed us that it was running late.
And then there is the plugin disabling without issues.
What's interesting in your crash log is that seemingly every thread is sleeping. Including the main thread.
Judging by the name of this call app//net.minecraft.server.v1_16_R3.MinecraftServer.sleepForTick(MinecraftServer.java:1220) it looks like the server was done with the current tick and went to sleep till the next tick, but the system didn't wake it up again.
This looks to me like there was a problem with your host system, not the Minecraft server itself, that prevented all these sleeping threads from being scheduled.