1.5.0: Server lag and more problems..

Pravenhold

New Member
Jul 29, 2019
5
0
0
Version:
1.7.0

What is the bug:
1.7.0 server is experiencing extreme lag after upgrading from 1.5.0 to 1.7.0 also players are kicked out and can no longer login.. due to nettyIO Network dispatcher exception null something.

the log shows this

[11:40:19] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 7370ms behind, skipping 147 tick(s)
[11:40:42] [Server thread/WARN]: Skipping Entity with id ThermalFoundation.blizzSlowball

and this last message is repeated like 200 times until ending and the next couple of thousand logentries are "Can't keep up!"

i can't see a single thing in the log on what it could be that causes this..
i will have to do a rollback to 1.5.0 that had no problems since players are complaining..

Mod & Version:


Paste.feed-the-beast.com log:


Can it be repeated:


Known Fix:
 

Pravenhold

New Member
Jul 29, 2019
5
0
0
latest log ehm nettyio #14 error
and world leaked.. alot..
 

Attachments

  • logs%2Ffml-server-latest.log.txt
    2.7 MB · Views: 137

GreenZombie

New Member
Jul 29, 2019
2,402
-1
0
It sounds like
1. thermal foundation changed/ dropped the entity id 'ThermalFoundation.blizzSlowball'
2. the player in question is in the part of the map where, for one reason or another, this item spawned a lot.

If they are being skipped on load they should not be saved out and the warning spam should go away. However the exception being reported might be preventing the effected chunks from saving properly. Which is born out from the writeToStream errors in the log.

/killall passed an entity name should be able to purge all entities of a type from the world, but only when loaded. hmmm. Perhaps the way to deal with this is upgrade in smaller increments rather than jumping from 1.5.0 to 1.7.x
 

Pravenhold

New Member
Jul 29, 2019
5
0
0
Ah forgot about this thread. And yeah, it was a huge amount of blizz and blaze.. A player had autospawners on and the grinders were jammed. So that was causing the extreme lag..