Replies: 1 comment 2 replies
-
That warning is normal. When it resumes it sees that a bunch of time has elapsed between ticks.
Something might have pinged the port and woke it up. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I recently created a minecraft server and set up autopause. I thought everything was working as I created this for my kids and dont use it myself. I was doing some maintenance on my server today and realized minecraft was running and my kids have not been using it. I crashed the server and attached to the container via compose up. After 5 mins the server paused however after about 5 more minutes I got this error message:
[18:51:06] [Server thread/WARN] [minecraft/MinecraftServer]: Can't keep up! Is the server overloaded? Running 284715ms or 5694 ticks behind
I had btop running in a second window and my cpu usage was extremely low and most the time was around 1% on all cores. After this message popped up the container restarted itself. This leads me to believe that the container has been running for weeks and never truly pausing. Its not the end of the world but I would like to be able to free up resources when the server is not an use. Also my other services are extremely lightweight as to not burn up electricity. Any help towards a solutions is much appreciated. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions