Closed Gebcrafter closed 7 years ago
Looking at your logfile, I see 2 issues:
RF Tools Dimensions and the McJty compat library don't seem to match in version
You game is overloaded and has to skip time to keep up. Please use one of the profiling tools available to see what's lagging the game---this looks like something we get reported for months but only as the final crash when the game gets so slow it stops completely. And those crash logs don't have any data on what's slowing the game down...
Also, if Minecraft is overloaded why does everything else in my world work correctly? The only thing not running properly (or at all for that matter) are the extraction conduits.
Having the same problem, although it seems to happen every time I restart the server. I then have to go break the insert side of the item conduit and place it again. My McJty mods definitely all match the Compat library and McJtyLib. I just updated them in a batch with the first release versions, nor are there messages indicating they are not in sync.
The server is not at all overloaded except one single message right after it completes the startup sequence. Perhaps that blip causes it on restart. Would be hard to catch it with Sampler since the startup sampling stops right before, and it's over before I could do anything. There are no other overloaded messages.
This seems to be a recent development. I didn't have that issue a version or two before.
EDIT: A /mt reload also seems to trigger it, which does sort of hang the server for a bit. Which backs up your caused by overload theory.
I can confirm that that is my problem, except substitute 'on server restart' to 'every hour or so'.
Has anyone figured anything out? Im not sure what to do. Modded is unplayable at this point.
I am also having the same issue, item conduits will randomly stop extracting and basically jam up my whole system. I can break a random conduit on the line that isn't even connected to an inventory and extracting will resume.
I haven't been able to reproduce this so far. As this only happens in long running instances, I will need to set up a debugging version that can give me data without being restarted all the time and let that run for a couple of hours. Weekend type stuff...
Alright, thanks Henry. <3
You're awesome Henry!
This is happening also to me, I'm using Direwolf20's 1.10.2 pack only one of my garden's conduits won't work at all now (as of this morning), I removed the whole line (15 conduits) and replaced, still won't empty the Farming station, only thing connected in line with them are the energy conduits, not seen this happen before in all the years been using enderio conduits
Experiencing the same issue on the DW20 1.10.2 pack, version 1.1.4.
I haven't modified the pack in any way, just downloaded/installed using the curse launcher.
As others are reporting item conduits stop extracting after working perfectly okay, and require to be broken and replaced.
Some additional info which doesn't perfectly match other reports:
likely related to or duplicate of #3943 ?
Can confirm, the issue is occurring when the chunk they're in is unloaded, either through traveling far enough away to unload it if no chunkloader is used, or upon server/ssp restart. Breaking and replacing a piece of conduit resets the network to work again. Occurs with both item and fluid conduits.
We are having the same issue as explained by @Silvrus . Our server restarts ever 12h. We load the chunk with FTB Utilities.
I'd like to add one observation. one line of conduits seems to not be as problematic. If you add a power or fluid conduit to an item, or any combination, that is when the problem is more prominent
An other instance is when the conduit run is long. it doesn't like the cross chunk.
Pack: [ALL the mods - expert]
i personally only see the problem when something is exported via item counduit to a chest, not in other circumstances. So: build a system with at least 2 or 3 types of conduits one of which is item conduit and export to a chest. You will see the issue on chunk reset on a server after restart, probably not on single player if the chuncs stay loaded.
One word: All this "me too"-ing (not just here) isn't really helpful unless it is a "me too on the current Ender IO version". I can "me too" any fixed bug if I use an Ender IO version from before it was fixed.
There were a couple of massive changes to conduits, block ticking, chunk loading avoidance, etc. at the end of December. So unless I either experience this myself (which would be ideal because I could then simply attach a debugger and see what's happening) or get a solid report of it happening with a current version, I am going to assume it was fixed with those changes.
I still have the same issue on Direwolf 20's 1.10 pack (Version 1.4.1). EnderIO Version: 1.10.2-3.1.156 EnderCore Version: 1.10.2-0.4.1.64-beta
I have a somewhat long conduit line (about 20 blocks). with multiple extraction and insertion points, criss crossing with a ender io power line. The problem occurs after a few hours (sometimes even less then an hour) and is fixed by replacing an arbitrary item conduit in the line. I cant confirm that is related to chunk loading, since it happened to me while i was only a few blocks around and the complete area of the conduit line is chunkloaded as well.
Do you need any more info on this?
Several words: @HenryLoenwind can you not close and lock the bug if it's fixed... If not I'm going to assume your assumptions on whether or not the bug was fixed are irrelevant.
@finnock you are 13 versions behind on Ender IO but do include the important Endercore change. Still, 157, 158, 160, 162 and 164 changed things with conduits.
@aaronmallen Did you miss some words or mistyped some letters? That doesn't really make sense to me.
@HenryLoenwind well i was on the release version (stable). i updated now to 164 and could reproduce the same error. i will try to make a minimal world save on a flatworld to try and reproduce the error.
that would be great. The only way I could reproduce it was on a server where I didn't have low level access.
The only way I could reproduce it was on a server where I didn't have low level access.
Can you generally not have low level access when it is on a server? Because i think it is not reproducible on single player. So would a world save of a multiplayer world where it happens even help?
I've been following this issue for a bit, and am still experiencing the issue as well using the direwolf20 1.10 (1.6.1) pack. In fact, having just watched the video uploaded this morning: you can observe him having the same problem at 5:51, where his refined storage system has no empowered seeds because the empowerer hooked up with EnderIO item conduits was unloaded when he was previously harvesting Ender Draconium in The End; therefore stopping the refined storage system from auto-crafting the empowered seeds.
https://youtu.be/rnJjYyPkYtE?t=5m51s
I observe the same issue on my multiplayer server, with the exception that I usually have to break a block on the item conduit, and replace it in order to get things crafting again. Or, restarting the server will usually suffice as well.
Admittedly I'm new to debugging anything Minecraft, but I'm willing to help get whatever further info I can.
Edit: Oh, and forgot to mention -- the pack at version 1.6.1 is using build 156. I can try updating to the latest if you believe that would help resolve.
More (hopefully useful) info: I was able to stop this problem by using an IC2 chunkloader to load the entire network. The Extra Utils 2 Chunk Loading Ward did NOT solve this problem for some reason.
Yeah, it seems chunkloading is a "solution" but not all chunkloaders are equal. I experienced this bug even when the network was loaded using FTButil chunk loading. Experienced other odd behavior too. But since switching to loading using Persistent Bits, this and the other issues have not happened.
Issue Description:
Item conduits randomly stop extracting after working fine for hours.
What happens:
Item conduits, after working fine for hours, stop extracting. I then have to break them, place them again, and set them to always on.
What you expected to happen:
Item conduits to stay on, hence the extraction setting 'always on'
Steps to reproduce:
Affected Versions (Do not use "latest"):
Your most recent log file where the issue was present:
http://pastebin.com/kUSb6krv