Server crash and network broken after placing Energy Interface

Question

Server crash and network broken after placing Energy Interface

xoxfaby opened this issue 6 years ago · 9 comments

xoxfaby commented 6 years ago

Issue type:

🐛 Bug

Short description:

After placing an Energy Interface next to a DE Infuser ( not sure if related ), the server hard crashed and the network got completely screwed up. After restarting the server the network wasn't work, aiming at energy interfaces to show the energy in Waila spams errors in the server log like crazy, some stuff is being transferred, other stuff isn't, random exporters and importers are erroring. placing and removing parts of the network throws a bunch of errors too.

Steps to reproduce the problem:

Literally just placed the Energy Interface next to the Infuser. I tried to see if just those things in a fresh world would cause any issues and they didn't. Can't reproduce on my server since the network seems completely broken.

Expected behaviour:

Things don't go to shit.

Versions:

This mod: 1,6.2
Minecraft: 1.12.2
Forge: 14.23.5.2781

Log file:

There were so many errors that I just included every log I found from the time it crashed and after. The crash should've happened shortly before 4:04 server time and after is all rebooting and errors.

http://shr.cx/logs.7z

rubensworks · Answer 1 · 2019-02-03T13:22:31.000Z

This seems to be the same problem as CyclopsMC/IntegratedDynamics#680, will push a fix.

rubensworks · Answer 2 · 2019-02-03T13:25:44.000Z

@xoxfaby Could you try the latest ID dev build (1269) to see if this fixes your problem?

You may need to reset your network by breaking/replacing a cable because of the earlier crash.

xoxfaby · Answer 3 · 2019-02-03T15:45:27.000Z

https://gist.github.com/65c5043928daccfdbf0e349bce61d492

Gist
cs6p.txt
GitHub Gist: instantly share code, notes, and snippets.

xoxfaby · Answer 4 · 2019-02-03T15:49:19.000Z

https://gist.github.com/xoxfaby/b2e250cb12ff0d41ad87adae3830e00f

Gist
HBak.txt
GitHub Gist: instantly share code, notes, and snippets.

rubensworks · Answer 5 · 2019-02-04T07:31:45.000Z

@xoxfaby So was this before, after or during your network reset?

xoxfaby · Answer 6 · 2019-02-04T11:45:00.000Z

During. And after.

…

On Mon, Feb 4, 2019, 08:31 Ruben Taelman ***@***.*** wrote: @xoxfaby <https://github.com/xoxfaby> So was this before, after or during your network reset? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#148 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA87HYPTsWkg7GZt--d1eLzZF-6IfV7Vks5vJ-HhgaJpZM4abhBj> .

rubensworks · Answer 7 · 2019-02-04T16:13:30.000Z

Ah, interesting. This is in fact a totally different problem, but also related to chunk loading.

Pushed a new ID build (1271) that should fix the error.

Could you let me know how that work for you @xoxfaby?

xoxfaby · Answer 8 · 2019-02-04T16:31:26.000Z

Looks like your fix worked! If something does pop up I will update, but as soon as I placed a new cable, everything sprung back into action.

rubensworks · Answer 9 · 2019-02-04T16:33:33.000Z

Great! Thanks for testing. I'll include these fixes in the next release.