Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sleep/Online Loop #58

Open
XBagon opened this issue Nov 16, 2023 · 0 comments
Open

Sleep/Online Loop #58

XBagon opened this issue Nov 16, 2023 · 0 comments

Comments

@XBagon
Copy link

XBagon commented Nov 16, 2023

I tried lazymc on a few different servers and while the Fabric server worked flawlessly, the Paper server just needed to be set to not timeout, the Forge server behaved special.
It started the server when I tried to join, but after I left it was caught in a loop of endlessly freezing and unfreezing, which I noticed because the CPU usage wasn't getting any lower, after I left.
I looked at the lazymc output, which continued on and on like this.

[00:38:48] [Server thread/INFO] [minecraft/ServerGamePacketListenerImpl]: XBagon lost connection: Disconnected
[00:38:48] [Server thread/INFO] [minecraft/DedicatedServer]: XBagon left the game
[00:38:48] [Server thread/INFO] [voicechat/]: Disconnecting client XBagon
>  INFO  lazymc::montior > Server has been idle, sleeping...
 INFO  lazymc::monitor > Server is now sleeping
 INFO  lazymc::monitor > Server is now online
 INFO  lazymc::montior > Server has been idle, sleeping...
 INFO  lazymc::monitor > Server is now sleeping
 INFO  lazymc::monitor > Server is now online
 INFO  lazymc::montior > Server has been idle, sleeping...
 INFO  lazymc::monitor > Server is now sleeping
 INFO  lazymc::monitor > Server is now online
 INFO  lazymc::montior > Server has been idle, sleeping...
 INFO  lazymc::monitor > Server is now sleeping
 INFO  lazymc::monitor > Server is now online

This is forge-1.18.2-40.2.2 on Ubuntu.

EDIT:
The Fabric server also crashes due to the tick lasting too long: [Server Watchdog/ERROR]: Considering it to be crashed, server will forcibly shutdown.
So setting max-tick-time=-1 is needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant