1.16.2
1.16.3
1.16.4
1.16.5
All tested, same results.
If you want a work-around, kick all players before the server restarts – not posible if the server crashes though.
I'm sure a workaround can be made using a datapack to set the nearest bed to the player's respawn coordinates flag after a startup, using a score to see if they were online before a crash/restart... I'm not a datapack wizzard though.
Sorry I should have mentioned that it doesnt matter about newly generated chunks, it'll do reguardless.
I dont make reports often, I'll try to be more inclusive next time.
Also to note, i did one test in 1.16.2 where the zpiglins were inside a fence contraption and the portal was not, it didn't crash... but the other way around did.
I just saw your edit Galaxy.
The launcher is just a bash file to run the java command to include Xms/Xmx and purely launches the downloaded jar, nothing else.
The log litterally provides nothing. No Rcon connections, no cant keep up!'s...
It will show "User Authenticator" messages.
I created an external linux script to look for these messages and act as a different kind of watchdog for when it reaches a specific ammount of them signifying a freeze and players trying to re-join – This was not used in this case and I only use it on my main server... I have it record graphs of when these occur, but I do not believe they will be helpful, and purely for logging the freeze events ( and besides, that server is running fabric for other performance tweaks, so it invalidates using those graphs )
Thanks.
I really wanted to make sure that this bug is not burried, as this had recked havoc on my server for a few versions – didn't feel like I had enough research on it to report at the time until now and after reading other bug reports, and thought to give whatever I had.
Actually Galaxy, The watchdog is doing it's job in this case.
With the watchdog set to -1 the server hangs indefinately and the only thing that gets logged into latest.log is authentication (connection) attempts.
Also do you mind trying to reproduce this yourself and have a look?
This is not a duped bug report.
Occurs in 1.16.1
Adding this comment as I commented on MC-184656 not realziing it was a different error....
The logs spam is incredibly massive, this is a 1.15.x world which was upgraded to 1.16 directly.
Here is just one instance of them, they sometimes go off several in a row with no errors above or below them.
[media]Edit: Posting the comment to have it posted to the correct issue.
Edit: I'm going to keep an eye out now I'm on 1.16.1 as others have said it still occurs, its not in my latest.log as of right now.
Edit July 18 2020: Its doing it again, its still a problem, not just an initial update spam
happens for me in 1.16 release... upgraded from 1.15.2 (reset nether).... attached one of the many spams
[media]
20w20a is completely unusable for me due to this... have to revert to 20w19a
Occurs in 1.15.2 also, can be constantly reproduced by jumping and immediately going to bed while in the air, takes about 10-20 seconds and you will get kicked almost every single time.
Occurs in 1.15, 1.15.1, 1.15.2 also
Still seeing this in 1.15.2
Does not work on 1.19.3 either