Jump to content
  • 0

Random Server Crashes--Cannot login anymore


Lanuk

Question

Title: Random Server Crashes--Cannot login anymore

Version: 1_0_4

OS: Ubuntu 12.04 LTS 64-bit (Linux)

Java Version: Ermm, according to forge: [iNFO] [ForgeModLoader] Java is OpenJDK 64-Bit Server VM, version 1.6.0_27, running on Linux:amd64:3.5.0-23-generic

Description of Problem:

Sometimes while wandering my server or something I will be kicked and get a "Internal Server Error" message in MC. Usually to fix this I'd have to restart. Now, even after restarting my server, I cannot login, and keep getting this "Internal Server Error".

Error Messages:

I am not sure what the difference between this and Error Log is, so I am just going to post in error log!

Error Log:


15:20:23 [iNFO] Lanuk[/192.168.2.4:51494] logged in with entity id 74 at ([world] 976.3563146482702, 111.5, -1159.3009106414115)

15:20:23 [iNFO] Loading Player: Lanuk

15:20:23 [iNFO] Sending serverside check to: Lanuk

>2013-07-24 15:20:24 [sEVERE] [ForgeModLoader] A critical server error occured handling a packet, kicking 74

net.minecraft.util.ReportedException: Ticking player

	at net.minecraft.entity.player.EntityPlayerMP.func_71127_g(EntityPlayerMP.java:457)

	at net.minecraft.network.NetServerHandler.func_72498_a(NetServerHandler.java:501)

	at net.minecraft.network.packet.Packet10Flying.func_73279_a(SourceFile:136)

	at net.minecraft.network.TcpConnection.func_74428_b(TcpConnection.java:442)

	at net.minecraft.network.NetServerHandler.func_72570_d(NetServerHandler.java:222)

	at net.minecraft.network.NetworkListenThread.func_71747_b(NetworkListenThread.java:53)

	at net.minecraft.server.dedicated.DedicatedServerListenThread.func_71747_b(SourceFile:30)

	at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:847)

	at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:320)

	at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:716)

	at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:600)

	at net.minecraft.server.ThreadMinecraftServer.run(SourceFile:573)

Caused by: java.lang.NullPointerException

	at net.minecraft.entity.DataWatcher.func_75681_e(DataWatcher.java:101)

	at net.minecraft.entity.EntityLiving.func_94056_bM(EntityLiving.java:3166)

	at net.minecraft.entity.EntityLiving.func_70023_ak(EntityLiving.java:3151)

	at chocolate.mods.BD.items.ItemArmorHelmetScouter.onUpdateEquiped(ItemArmorHelmetScouter.java:42)

	at chocolate.mods.BD.items.ItemArmorBase.onArmorTickUpdate(ItemArmorBase.java:18)

	at net.minecraft.entity.player.InventoryPlayer.func_70429_k(InventoryPlayer.java:314)

	at net.minecraft.entity.player.EntityPlayer.func_70636_d(EntityPlayer.java:599)

	at net.minecraft.entity.EntityLiving.func_70071_h_(EntityLiving.java:871)

	at net.minecraft.entity.player.EntityPlayer.func_70071_h_(EntityPlayer.java:333)

	at net.minecraft.entity.player.EntityPlayerMP.func_71127_g(EntityPlayerMP.java:406)

	... 11 more

15:20:24 [WARNING] Failed to handle packet for Lanuk/192.168.2.4: net.minecraft.util.ReportedException: Ticking player

net.minecraft.util.ReportedException: Ticking player

	at net.minecraft.entity.player.EntityPlayerMP.func_71127_g(EntityPlayerMP.java:457)

	at net.minecraft.network.NetServerHandler.func_72498_a(NetServerHandler.java:501)

	at net.minecraft.network.packet.Packet10Flying.func_73279_a(SourceFile:136)

	at net.minecraft.network.TcpConnection.func_74428_b(TcpConnection.java:442)

	at net.minecraft.network.NetServerHandler.func_72570_d(NetServerHandler.java:222)

	at net.minecraft.network.NetworkListenThread.func_71747_b(NetworkListenThread.java:53)

	at net.minecraft.server.dedicated.DedicatedServerListenThread.func_71747_b(SourceFile:30)

	at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:847)

	at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:320)

	at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:716)

	at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:600)

	at net.minecraft.server.ThreadMinecraftServer.run(SourceFile:573)

Caused by: java.lang.NullPointerException

	at net.minecraft.entity.DataWatcher.func_75681_e(DataWatcher.java:101)

	at net.minecraft.entity.EntityLiving.func_94056_bM(EntityLiving.java:3166)

	at net.minecraft.entity.EntityLiving.func_70023_ak(EntityLiving.java:3151)

	at chocolate.mods.BD.items.ItemArmorHelmetScouter.onUpdateEquiped(ItemArmorHelmetScouter.java:42)

	at chocolate.mods.BD.items.ItemArmorBase.onArmorTickUpdate(ItemArmorBase.java:18)

	at net.minecraft.entity.player.InventoryPlayer.func_70429_k(InventoryPlayer.java:314)

	at net.minecraft.entity.player.EntityPlayer.func_70636_d(EntityPlayer.java:599)

	at net.minecraft.entity.EntityLiving.func_70071_h_(EntityLiving.java:871)

	at net.minecraft.entity.player.EntityPlayer.func_70071_h_(EntityPlayer.java:333)

	at net.minecraft.entity.player.EntityPlayerMP.func_71127_g(EntityPlayerMP.java:406)

	... 11 more

15:20:24 [iNFO] Unloading Player: Lanuk

Link to comment
Share on other sites

4 answers to this question

Recommended Posts

  • 0

I will create a separate post about this since your crashing issue sounds like mine, ie the crashing while wandering, minus the crashing when trying to log back in, I thought I would post what I have been seeing so you can test to see if the issue is the same.

I have been noticing, from some very basic testing, that the better dungeons mod with Hexxit 1.0.5 causes an internal server error every time it tries to spawn a better dungeons castle or even the nether villages when I have my Hexxit server running on multicraft.jjservers.com, yet no one else is kicked out (3 people including myself) since they are in areas that we have already explored. Now what is interesting is when I run the same Hexxit server on my local machine running Windows I can wander all day long and not get a crash and the better dungeons structures are generated. The question is what is the multicraft server doing that is causing the generation issue? The multicraft server has 3 GB of RAM allocated to it too and is only using up 25% of the RAM as well.

If you go in to creative mode and give yourself a castles.prop and then try to spawn it. I suspect you will crash out, but if you take the same server and start it on a Windows computer then try to spawn a castles.prop, your Minecraft will not give an internal server error.

FYI - The server I am on is running a newer version of Java - INFO Java is Java HotSpot 64-Bit Server VM, version 1.7.0_21, running on Linux:amd64:2.6.32-358.0.1.el6.x86_64, installed at /usr/java/jdk1.7.0_21/jre

Link to comment
Share on other sites

  • 0

PS. After more testing I think the crash in question is due to certain better dungeons templates. I'm not sure which ones but if I try to spawn a castles.prop in a snow area which ever random template the mod chose to use causes the internal server error.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...