-
-
Notifications
You must be signed in to change notification settings - Fork 38
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
Server shutting down automatically even with players connected #283
Labels
bug-not-confirmed
Bug that wasn´t reproduced
Comments
These are the logs from when i opened it until it crashed, didnt mean to mark this as completed |
Scratch that, I think it was just a crash... |
@realairacobra can you reproduce using loglevel 2? |
I'd love to do so but due to some employment issues i dont have that server
(which was literally just a thinkpad) anymore, apologies, cant replicate it.
…On Thu, Jul 25, 2024 at 9:33 PM gekigek99 ***@***.***> wrote:
@realairacobra <https://github.com/realairacobra> can you reproduce using
loglevel 2?
would you mind sharing also the config file?
—
Reply to this email directly, view it on GitHub
<#283 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AWKI6BYVTGR7I5GFBGQBDSDZOGKNFAVCNFSM6AAAAABGA46ZRGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJRGY3TQNBSGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current Behavior (🐛 Bug)
After joining and playing for a while the server automatically shuts down
Expected Behavior
After joining and playing for a while the server doesnt shut down until we leave
Steps to Reproduce
Open MSH
Join the server
Play for a while
It shuts down.
MSH Logs
MSH-Version
2.5.0
MSH-Commit
Compiled it today without the dev branch, no clue how to find it.
Operating system
ArcoLinuxXL
System architecture?
AMD64
Minecraft Version
1.20.1
Minecraft Server Software?
Fabric
Is there an existing issue for this?
The text was updated successfully, but these errors were encountered: