All the Mods 7 - ATM7

All the Mods 7 - ATM7

3M Downloads

World crash on my server but working in singleplayer.

Kimisyl opened this issue ยท 2 comments

commented

Hello! I recently updated my world from 0.4.21 to 0.4.25
The world seemed to work fine at first, but while navigating with a jetpack to a new chunk, everything crashed. A structure I never found before / I was using a treasure map given by a cartographer. 2 other players was online, nothing in particular to report from their part.

The whole server crashed. Latest backup was 24 hours earlier because I didn't dare to check the changelogs (my bad)

Since then, I try to salvage my world but I keep getting various crash report, here is the latest
https://pastebin.com/unsUH4wD

I tried to remove my playerdata file. It didn't work, so I removed all the playerdata files.

I took the world in singleplayer and it's working fine, I can load and play as usual. But As soon as I port this save to my server, it keeps crashing in less than a minute.

In the latest lines before crash I kept getting an unknown username for a UUID and playeradvancements issues.
So I added a random Username no space in my usernamecache.json, but I don't know how I should fix playeradvancements. This isn't a connected player, he isn't recognised on my server, so maybe a random entity ?

The crashing report is showing Mekanism and Pipez energy and we know we had many issues with the energy cables, especially the nitro cables in 0.4.21 could this be related ?

I tried to run the Region Fixer only the idcounts.dat was unreadable. So I removed the file and removes all the map files.
Still not working.

I'm out of idea.

commented

The server watchdog is shutting down your server due to a tick taking too long.

Description: Watching Server
 
java.lang.Error: ServerHangWatchdog detected that a single server tick took 60.00 seconds (should be max 0.05)

While this won't fix the lag, you should be able to stop the crashes by setting max-tick-time to -1 in your server.properties file.

commented

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.