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

[Crash]: Single Server Tick Took 60.00 seconds #3114

Open
nemo8338 opened this issue Jun 26, 2022 · 3 comments
Open

[Crash]: Single Server Tick Took 60.00 seconds #3114

nemo8338 opened this issue Jun 26, 2022 · 3 comments
Labels

Comments

@nemo8338
Copy link

nemo8338 commented Jun 26, 2022

Possible Fixes

Yes

Modpack Version

1.8.22

What happened?

For seemingly no obvious reason the server crashed when a player attempted to join. It had run for weeks without problems, and the player was not new. The server then got stuck in a loop of crashing and rebooting. I tried rebooting to earlier backups when I was on and the server was working fine, but the problem continued. Eventually it did load, though I don't know why, and I was able to join. It seemed to run fine. I had the original player join. This caused a crash, but not repeated crashing as before. We had a third player join and go to the area where the original player had been loading into. This caused a crash. Gave up for the night, loaded the server up the next day, joined as normal, but new chunks were not loading, and then the server crashed. I attempted to run the world on the newest version of the modpack. Same problem.

Crash Log

https://gist.github.com/nemo8338/4c8106d9dc577f02ce71846416b38904

@nemo8338 nemo8338 added the Crash label Jun 26, 2022
@vedalken254
Copy link

vedalken254 commented Jun 26, 2022

Sounds like a certain chunk is requiring a lot of processing. You can modify the time before the server will crash out in server.properties with the max-tick-time setting. I found that on my somewhat older hardware, I had to bump that to 120000 (default is 60000; both times are in ms so # of seconds x 1000). In ATM7, they actually defaulted the watchdog to not crash out on tick time (modded MC gets more and more intensive on the processing and RAM side the higher up the MC version is). Try adjusting that setting to 120000 and let me know if it still crashes.

Veddy

@MelanX
Copy link

MelanX commented Jun 26, 2022

-1 would also completely disable that

@vedalken254
Copy link

-1 would also completely disable that

That's what they did for ATM7, but I wouldn't recommend that for ATM6. With Modern enough hardware, 240 seconds should be the most you pump into that with ATM6. I recommended 120 seconds so they can see how bad the tick processing is getting (if it crashes at 120, up it to 180 and test again and so on). More a methodical "don't do more than is necessary" approach.

Veddy

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

No branches or pull requests

3 participants