You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I ran into an issue due to which I'm unable to resume my Minecraft server after a freeze.
I understand that it's possible to configure lazymc to restart the server instead of freezing it. And I've found that opting for the restart solves my trouble. Yet I'm interested in the shorter period it would take to resume the server from a freeze rather than from a stop. So I decided to report this crash hoping that it might be useful.
Thanks for maintaining lazymc!
Specifications
I'm using lazymc as a part of okazakee's Docker container.
Ubuntu 22.04.2 LTS Jammy Jellyfish
lazymc 0.2.10
Purpur git-Purpur-1975 (MC: 1.19.4)
Minecraft 1.19.4, protocol 762
Steps to reproduce
In lazymc.toml, make sure freeze_process is set to true. It should be the default.
Run the container
As I understand it, the container checks for updates on lazymc, Purpur and Minecraft and sets Java startup flags before passing the baton to lazymc.
Join the server. And having done so, let lazymc wake it up for the first time.
Disconnect and wait a minute until lazymc freezes the server.
Try joining the server again.
After completing the final step, my server immediately crashed. The following crash log was then produced.
I had the same problem with paper and just set timeout-time: 0 in spigot.yml, which writes a thread dump every time the server is woken up after some time, but you can ignore that and it works just fine.
Fix for Vanilla/Fabric/Forge:
This happens because minecraft realizes that a tick has taken way too long. You can fix this by setting max-tick-time=-1 in server.properties
I tested it with fabric and forge 1.20.
Hi,
I ran into an issue due to which I'm unable to resume my Minecraft server after a freeze.
I understand that it's possible to configure
lazymc
to restart the server instead of freezing it. And I've found that opting for the restart solves my trouble. Yet I'm interested in the shorter period it would take to resume the server from a freeze rather than from a stop. So I decided to report this crash hoping that it might be useful.Thanks for maintaining
lazymc
!Specifications
I'm using
lazymc
as a part of okazakee's Docker container.Steps to reproduce
lazymc.toml
, make surefreeze_process
is set totrue
. It should be the default.lazymc
wake it up for the first time.lazymc
freezes the server.After completing the final step, my server immediately crashed. The following crash log was then produced.
Purpur crash log.
Work-around to solve the immediate issue
In
lazymc.toml
uncommentfreeze_process
and set it tofalse
to configure the program to stop the Minecraft server as a way of putting it to sleep.The text was updated successfully, but these errors were encountered: