Jump to content

BloodyIron

Members
  • Content Count

    18
  • Joined

  • Last visited

  1. That is currently set to false, we haven't changed it. Is that the value we want?
  2. We're pretty much default, as in we seeded with a new world and reset configs, so... you want to see specifically?
  3. Yeah we've had to manually move people out of problematic areas repeatedly now, and advise people to reduce exploration in general (which is totally lame). Taking the map offline and repairing it is infeasible with how frequently this has happened, one day it happened about 6 times. I'm looking for a permanent fix. The work-around is good to know, but doesn't work for us. Any more ideas?
  4. So also, we had to turn off necromancy as summoning a minion ALWAYS crashes a server and we cannot get that stable at all Any info, please?
  5. So an additional report. User reports that a chunk was generated in front of them, then suddenly it generated a second time with a building on it. It's a stone tower sort of building but does not seem to be related to battle towers. It then disconnected him identically to all the other crashes. Fortunately he talked to me about it and I was able to modify his coords before reconnecting so it didn't crash the server, but I believe if I had not forcefully changed his coordinates before reconnecting this would have crashed the server.
  6. Okay so I'm not sure if any more updates are going to happen for 1.6.4 past Hexxit 2.0.1c, but since the relevant thread for 2.0.1c is locked (for reasons I'm sure) I am posting here. The last like... 4 crashes we've had in the last week have been related to new chunk generation. People get into chunk areas that are problematic and... the server dies. Here is the starting java error we're seeing: 2014-10-18 13:57:14 [WARNING] Failed to handle packet for PLAYERNAME/(SERVERIPADDRESS): java.lang.NullPointerException java.lang.NullPointerException at net.minecraft.world.gen.structure.StructureStart.func_75068_a(StructureStart.java:47) at net.minecraft.world.gen.structure.MapGenStructure.func_75051_a(MapGenStructure.java:81) at net.minecraft.world.gen.ChunkProviderGenerate.func_73153_a(ChunkProviderGenerate.java:533) at org.bukkit.craftbukkit.v1_6_R3.generator.NormalChunkGenerator.func_73153_a(NormalChunkGenerator.java:59) at net.minecraft.world.gen.ChunkProviderServer.func_73153_a(ChunkProviderServer.java:399) at net.minecraft.world.chunk.Chunk.func_76624_a(Chunk.java:1346) at net.minecraft.world.gen.ChunkProviderServer.originalGetChunkAt(ChunkProviderServer.java:270) at net.minecraft.world.gen.ChunkProviderServer.getChunkAt(ChunkProviderServer.java:194) at net.minecraft.server.management.PlayerInstance.<init>(PlayerInstance.java:57) at net.minecraft.server.management.PlayerManager.func_72690_a(PlayerManager.java:140) at net.minecraft.server.management.PlayerManager.func_72691_b(PlayerManager.java:240) at net.minecraft.server.management.PlayerManager.func_72685_d(PlayerManager.java:343) at net.minecraft.server.management.ServerConfigurationManager.func_72358_d(ServerConfigurationManager.java:379) at net.minecraft.network.NetServerHandler.func_72498_a(NetServerHandler.java:611) at net.minecraft.network.packet.Packet10Flying.func_73279_a(Packet10Flying.java:51) at net.minecraft.network.TcpConnection.func_74428_b(TcpConnection.java:470) at net.minecraft.network.NetServerHandler.func_72570_d(NetServerHandler.java:233) at net.minecraft.network.NetworkListenThread.func_71747_b(NetworkListenThread.java:54) at net.minecraft.server.dedicated.DedicatedServerListenThread.func_71747_b(DedicatedServerListenThread.java:34) at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:910) at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:330) at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:777) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:659) at net.minecraft.server.ThreadMinecraftServer.run(ThreadMinecraftServer.java:16) And then the player that has triggered the problem gets disconnected, they report "internal server error", as in the server kicks them. Then the player tries to reconnect, and we get a much more destructive error that seems to actually lead to the server crashing: 2014-10-18 13:57:31 [INFO] Sending serverside check to: PLAYERNAME 2014-10-18 13:57:31 [INFO] [BetterFurnaces]: Sending Server Config to Client 2014-10-18 13:57:31 [SEVERE] java.lang.NullPointerException 2014-10-18 13:57:31 [SEVERE] at net.minecraft.world.gen.structure.StructureStart.func_75068_a(StructureStart.java:47) 2014-10-18 13:57:31 [SEVERE] at net.minecraft.world.gen.structure.MapGenStructure.func_75051_a(MapGenStructure.java:81) 2014-10-18 13:57:31 [SEVERE] at net.minecraft.world.gen.ChunkProviderGenerate.func_73153_a(ChunkProviderGenerate.java:533) 2014-10-18 13:57:31 [SEVERE] at org.bukkit.craftbukkit.v1_6_R3.generator.NormalChunkGenerator.func_73153_a(NormalChunkGenerator.java:59) 2014-10-18 13:57:31 [SEVERE] at net.minecraft.world.gen.ChunkProviderServer.func_73153_a(ChunkProviderServer.java:399) 2014-10-18 13:57:31 [SEVERE] at net.minecraft.world.chunk.Chunk.func_76624_a(Chunk.java:1336) 2014-10-18 13:57:31 [SEVERE] at org.bukkit.craftbukkit.v1_6_R3.chunkio.ChunkIOProvider.callStage2(ChunkIOProvider.java:55) 2014-10-18 13:57:31 [SEVERE] at org.bukkit.craftbukkit.v1_6_R3.chunkio.ChunkIOProvider.callStage2(ChunkIOProvider.java:15) 2014-10-18 13:57:31 [SEVERE] at org.bukkit.craftbukkit.v1_6_R3.util.AsynchronousExecutor$Task.finish(AsynchronousExecutor.java:188) 2014-10-18 13:57:31 [SEVERE] at org.bukkit.craftbukkit.v1_6_R3.util.AsynchronousExecutor.finishActive(AsynchronousExecutor.java:347) 2014-10-18 13:57:31 [SEVERE] at org.bukkit.craftbukkit.v1_6_R3.chunkio.ChunkIOExecutor.tick(ChunkIOExecutor.java:30) 2014-10-18 13:57:31 [SEVERE] at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:832) 2014-10-18 13:57:31 [SEVERE] at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:330) 2014-10-18 13:57:31 [SEVERE] at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:777) 2014-10-18 13:57:31 [SEVERE] at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:659) 2014-10-18 13:57:31 [SEVERE] at net.minecraft.server.ThreadMinecraftServer.run(ThreadMinecraftServer.java:16) 2014-10-18 13:57:31 [SEVERE] Encountered an unexpected exception NullPointerException java.lang.NullPointerException at net.minecraft.world.gen.structure.StructureStart.func_75068_a(StructureStart.java:47) at net.minecraft.world.gen.structure.MapGenStructure.func_75051_a(MapGenStructure.java:81) at net.minecraft.world.gen.ChunkProviderGenerate.func_73153_a(ChunkProviderGenerate.java:533) at org.bukkit.craftbukkit.v1_6_R3.generator.NormalChunkGenerator.func_73153_a(NormalChunkGenerator.java:59) at net.minecraft.world.gen.ChunkProviderServer.func_73153_a(ChunkProviderServer.java:399) at net.minecraft.world.chunk.Chunk.func_76624_a(Chunk.java:1336) at org.bukkit.craftbukkit.v1_6_R3.chunkio.ChunkIOProvider.callStage2(ChunkIOProvider.java:55) at org.bukkit.craftbukkit.v1_6_R3.chunkio.ChunkIOProvider.callStage2(ChunkIOProvider.java:15) at org.bukkit.craftbukkit.v1_6_R3.util.AsynchronousExecutor$Task.finish(AsynchronousExecutor.java:188) at org.bukkit.craftbukkit.v1_6_R3.util.AsynchronousExecutor.finishActive(AsynchronousExecutor.java:347) at org.bukkit.craftbukkit.v1_6_R3.chunkio.ChunkIOExecutor.tick(ChunkIOExecutor.java:30) at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:832) at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:330) at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:777) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:659) at net.minecraft.server.ThreadMinecraftServer.run(ThreadMinecraftServer.java:16) 2014-10-18 13:57:31 [SEVERE] This crash report has been saved to: /AFOLDER/crash-2014-10-18_13.57.31-server.txt 2014-10-18 13:58:00 [WARNING] The server is going slow. Last server tick was 28880ms ago 2014-10-18 13:58:00 [WARNING] Last Tick: 1413662251174 Current Time: 1413662280054 Warning: 20000 Timeout: 60000 and shortly thereafter the server instance handles the crash dump and terminates. The only solution we have found is to manually remove the person from the known problematic area in the dimension, and this seems to happen (so far) only in the overworld. I am _SUSPECTING_ that it may be battletowers, as we are seeing odd behavior with it (namely 6 or more battletowers generate in a line all over the place), but I am not yet certain. If anyone has some advice, please tell me As for an update to 2.0.1c, if possible that would be swell
  7. Okay so I think maybe my question got lost. 1.2.10c, is this intended to be the last 1.6.4 release for Tekkit? What are the plans for 1.6.4 Tekkit, and is 1.2.10c final, or whatever? As I have mentioned a few times now, we want to update Galacticraft to fix a bug we are actually experiencing, and updating in piece-meal doesn't work for us. As such a change from say 1.2.9e to 1.2.10(something) we could handle, I'm just not sure if 1.2.10c is the last one for 1.6.4, etc. Please advise? Oh, and thanks for your help everyone.
  8. I'm not sure how that's relevant, since there are already permission declarations for opis, except the 1.2.2 and 1.2.1 version still requires that privilege list in it's config, which is lame :/ no other idea how to do this?
  9. Hey so for Opis, to get the run functions and stuff in the GUI I need to add a player to the "privileged" list in opis, but this isn't how I want to handle permissions, we organize permissions through "bukkit" permission style. Granting groups access to specific things. For now I can use the privileged thing, but do you know of another way to do it? Also, without OP'ing people.
  10. Oh okay, yeah it's probable that my crash was due to using MobiusCore 1.2.2 then. For now I'm going to stick to Opis 1.2.1 though as we have it working Thanks for that tidbit though
  11. Hey so I've tried reading through this thread but I'm a bit confused. Is 1.2.10c going to be the last build for 1.6.4? I'm waiting for the recommended build for 1.6.4 so we can update our things, as we want the newer version of galacticraft to fix some bugs we're having (rockets disappearing after crafting).
  12. As a point of interest, I tried using Opis and Mobius 1.2.2 for 1.6.4, and I was getting crashing on server init, but when I switched to 1.2.1 all seemed to be well. This is more for other people to read.
  13. That Opis + Mobius looks neat, I'm going to read more on it now, thanks!
  14. Oh turns out a force field was going berzerk, yet I couldn't determine this from timings or other methods :/
  15. Can you elaborate on that please?
×
×
  • Create New...