UPDATE:
!!!Solution further down!!!
Do be careful with MFR Programmable RedNet Controller
What is the bug:
Server was running but players reported lag. Tickrate was at a calm 30ms overall but the server was skipping ticks. I figured before I do anything drastic Id just give it a quick restart. Now the world file wont load up (crashes at the very end of bootup after unloading rftools dimensions).
Crashlog is not providing any information that would actually allow a rookie like myself to fix it.
Taken from the server log this is what he does just before the error occurs:
[19:17:27] [Server thread/TRACE] [ForgeMicroblock/ForgeMicroblock]: Sending event FMLServerStartedEvent to mod ForgeMicroblock
[19:17:27] [Server thread/TRACE] [ForgeMicroblock/ForgeMicroblock]: Sent event FMLServerStartedEvent to mod ForgeMicroblock
[19:17:28] [Server thread/ERROR] [FML/]: Exception caught during firing event cpw.mods.fml.common.gameevent.TickEvent$WorldTickEvent@439f5bf3:
Paste.feed-the-beast.com log:
http://pastebin.com/R9ySZNE1
E: I have identified the problem to be in a player base in the overworld. I have found the chunkloader in that base and deleted it. Now the server will boot and only crash if a player ticks these chunks. That allowed me to produce a more specific crashlog and the problem seem to be enderIO conduits (E: it appeared at the time, this is false information). I have subsequently gone in and deleted conduits at multiple locations; one by one just producing new crashlogs. It would seem that it is not an isolated issue because it has been split between multiple chunks and systems. Below you can find a "better" crash report that still includes the original problem but more information to work with.
It is worth noting that the server was running and working and these problems with EnderIO have only arisen after a restart.
http://pastebin.com/0AraBHTV
E2: Yet another, different log, this time MFR.
http://pastebin.com/EhTEXiG0
Also had an energy node from extra utils crash me now so the problem is not isolated to enderio it would seem. I can remove as much as I want more and different stuff just gives the same error.
E3: SOLUTION
It turns out tfox was right so many thanks to him! Unfortunately in our case merely removing the MFR RedNet cables and RedNet controller did not do the trick. We went through and tested(deleted) every chunk one by one. Turns out that the chunk causing the issue was the one with the MFR controller inside of it (interestingly the cables worked as the controller was only thing in a seperate chunk) but a simple removal was not enough. Re-setting/gen'ing the entire chunk is what did it for us in the end.
!!!Solution further down!!!
Do be careful with MFR Programmable RedNet Controller
What is the bug:
Server was running but players reported lag. Tickrate was at a calm 30ms overall but the server was skipping ticks. I figured before I do anything drastic Id just give it a quick restart. Now the world file wont load up (crashes at the very end of bootup after unloading rftools dimensions).
Crashlog is not providing any information that would actually allow a rookie like myself to fix it.
Taken from the server log this is what he does just before the error occurs:
[19:17:27] [Server thread/TRACE] [ForgeMicroblock/ForgeMicroblock]: Sending event FMLServerStartedEvent to mod ForgeMicroblock
[19:17:27] [Server thread/TRACE] [ForgeMicroblock/ForgeMicroblock]: Sent event FMLServerStartedEvent to mod ForgeMicroblock
[19:17:28] [Server thread/ERROR] [FML/]: Exception caught during firing event cpw.mods.fml.common.gameevent.TickEvent$WorldTickEvent@439f5bf3:
Paste.feed-the-beast.com log:
http://pastebin.com/R9ySZNE1
E: I have identified the problem to be in a player base in the overworld. I have found the chunkloader in that base and deleted it. Now the server will boot and only crash if a player ticks these chunks. That allowed me to produce a more specific crashlog and the problem seem to be enderIO conduits (E: it appeared at the time, this is false information). I have subsequently gone in and deleted conduits at multiple locations; one by one just producing new crashlogs. It would seem that it is not an isolated issue because it has been split between multiple chunks and systems. Below you can find a "better" crash report that still includes the original problem but more information to work with.
It is worth noting that the server was running and working and these problems with EnderIO have only arisen after a restart.
http://pastebin.com/0AraBHTV
E2: Yet another, different log, this time MFR.
http://pastebin.com/EhTEXiG0
Also had an energy node from extra utils crash me now so the problem is not isolated to enderio it would seem. I can remove as much as I want more and different stuff just gives the same error.
E3: SOLUTION
It turns out tfox was right so many thanks to him! Unfortunately in our case merely removing the MFR RedNet cables and RedNet controller did not do the trick. We went through and tested(deleted) every chunk one by one. Turns out that the chunk causing the issue was the one with the MFR controller inside of it (interestingly the cables worked as the controller was only thing in a seperate chunk) but a simple removal was not enough. Re-setting/gen'ing the entire chunk is what did it for us in the end.
Last edited:
