I keep getting time outs, where the server seems fine but my client stops interacting with the server. Not sure if its my client the the network. When I drop, and check the server, its still up with 10+ people. anyone else have this issue?
I noticed this issue before when I was on the server the first 1-2 hours. It does affect everyone, but the duration of the lag spike is in relation with the amount of players getting kicked. I did try to catch the cause but was too slow with the thread dump. I will let the system print out full threaddumps every time the tps drop. Please let me know when such a big lag spike/time out happens again. Else I won't be able to find it within the +100k lines of log.
@Ralph_Anthony can you please run a Speedtest.net by Ookla - The Global Broadband Speed Test post your down/up Also do you live in a rouge like Dungeon?
Thats not the issue... hahah how is your Ping to the server. When you select multiplayer, Above the players online, hover over the signal bars. what the MS?
129-160ms[DOUBLEPOST=1416758074,1416716579][/DOUBLEPOST]Seems to be happening to everyone right now. 0/52 (127ms) - time out on login.
-snip thought it was Compact machines because this spammed my console. Not sure if this could be an issue, Spoiler [16:42:31] [Client thread/WARN] [FML]: Unable to lookup CompactMachines:interfaceblock for public static org.dave.CompactMachines.block.BlockCM org.dave.CompactMachines.init.ModBlocks.interfaceblock. Is there something wrong with the registry? [16:42:31] [Client thread/WARN] [FML]: Unable to lookup CompactMachinesersonalShrinkingDevice for public static org.dave.CompactMachines.item.ItemPersonalShrinkingDevice org.dave.CompactMachines.init.ModItems.personalShrinkingDevice. Is there something wrong with the registry? [16:42:31] [Client thread/WARN] [FML]: Unable to lookup CompactMachines:atomShrinker for public static org.dave.CompactMachines.item.ItemAtomShrinker org.dave.CompactMachines.init.ModItems.atomShrinker. Is there something wrong with the registry? [16:42:31] [Client thread/WARN] [FML]: Unable to lookup CompactMachines:atomEnlarger for public static org.dave.CompactMachines.item.ItemAtomEnlarger org.dave.CompactMachines.init.ModItems.atomEnlarger. Is there something wrong with the registry? [16:42:31] [Client thread/WARN] [FML]: Unable to lookup CompactMachines:interfaceItem for public static org.dave.CompactMachines.item.ItemInterface org.dave.CompactMachines.init.ModItems.interfaceItem. Is there something wrong with the registry? [16:42:31] [Client thread/WARN] [FML]: Unable to lookup CompactMachines:quantumEntangler for public static org.dave.CompactMachines.item.ItemEntangler org.dave.CompactMachines.init.ModItems.quantumEntangler. Is there something wrong with the registry?
honestly the timeouts are a huge determent to play and have recently been lasting longer than if the server had crashed
Ive noticed these timeouts here on Modsauce and on MyG. I think it might have something to do with 1.7.10
It's something to do with one of the plugins , we found it out a while back on Galaxy by having a short period with no plugins installed and we had no timeouts.
As you are telling Mine your Galaxy, i also have to say that we have some disconnects on Dw20. So Plugins might be a good idea.
That's not 100% sure. It was only for 30 minutes and this after a restart. I think there is not allways a timeout in the 30 minutes after a restart.
That is true but there was also next to no lag during that 30 mins compared to the same stuff happening with plugins on
wonder if its Rouge like dungeons. I know Bevo has it but he turned them down to where they rarely spawn(havnt seen one yet). But on modsauce they are everywhere. I believe there are alot on galaxy as well..... These thing have like 50 spawners in them at least.... all spawning mobs.[DOUBLEPOST=1417008442,1417007542][/DOUBLEPOST]Might need to disable Hardcore Ender Expansion [INVALID] Homeland Enderman crashing server · Issue #66 · chylex/Hardcore-Ender-Expansion · GitHub If you do the "Knowledge note" will need to be removed from Vote rewards
just got the threaddump done this time. gist:a60a259749d5e140a05b ^the main/server thread is waiting: Code: "Server thread" - Thread t@19 java.lang.Thread.State: TIMED_WAITING at java.lang.Thread.sleep(Native Method) But I don't see any of the other threads blocking it.
Sleeping != blocking. From the stack trace, I'd guess that it is waiting for the async save operation to finish.
