Server producing constant .net and java errors

[Leigh Ellis]

I've installed a clean 'New Tekkit' server and while everything works, I get constant error messages, which I would like to remove by either fixing the problem or hiding them.

If I run tekkit via the launch.bat I get a few errors at first then more errors which repeat every few seconds as follows:

2013-10-08 09:01:11 [iNFO] [Minecraft] Disconnecting /192.168.154.253:22568: Protocol error

2013-10-08 09:01:11 [iNFO] [Minecraft] /192.168.154.253:22568 lost connection

2013-10-08 09:01:11 [iNFO] [Minecraft] /192.168.154.253:28963 lost connection

2013-10-08 09:01:21 [sEVERE] [ForgeModLoader] Detected leaking worlds in memory. There are 4 worlds that appear to be persisting. A mod is likely caching the world incorrectly

 

2013-10-08 09:01:21 [sEVERE] [ForgeModLoader] The world 787ce7d9 (world) has leaked.

2013-10-08 09:01:21 [sEVERE] [ForgeModLoader] The world 6d8d0fdd (world) has leaked.

2013-10-08 09:01:59 [iNFO] [sTDERR] java.io.IOException: Bad packet id 114

2013-10-08 09:01:59 [iNFO] [sTDERR]    at ef.a(Packet.java:151)

2013-10-08 09:01:59 [iNFO] [sTDERR]    at cg.i(TcpConnection.java:324)

2013-10-08 09:01:59 [iNFO] [sTDERR]    at cg.c(TcpConnection.java:544)

2013-10-08 09:01:59 [iNFO] [sTDERR]    at ch.run(SourceFile:93)

2013-10-08 09:01:59 [iNFO] [Minecraft] Disconnecting /192.168.154.253:14053: Protocol error

2013-10-08 09:01:59 [iNFO] [Minecraft] /192.168.154.253:14053 lost connection

2013-10-08 09:02:08 [iNFO] [sTDERR] java.io.IOException: Bad packet id 114

2013-10-08 09:02:08 [iNFO] [sTDERR]    at ef.a(Packet.java:151)

2013-10-08 09:02:08 [iNFO] [sTDERR]    at cg.i(TcpConnection.java:324)

2013-10-08 09:02:08 [iNFO] [sTDERR]    at cg.c(TcpConnection.java:544)

2013-10-08 09:02:08 [iNFO] [sTDERR]    at ch.run(SourceFile:93)

2013-10-08 09:02:08 [iNFO] [Minecraft] Disconnecting /192.168.154.253:50209: Protocol error

2013-10-08 09:02:08 [iNFO] [Minecraft] /192.168.154.253:50209 lost connection

2013-10-08 09:03:09 [iNFO] [sTDERR] java.io.IOException: Received string length is less than zero! Weird string!

 

If I install McMyAdmin (which I want to use long term) and add the tekkit.jar to this, it still works but I get the following errors repeating:

 

 

08:54:24 CONSOLE: [iNFO] at net.minecraft.network.TcpConnection.func_74447_i(TcpConnection.java:327)

08:54:24 CONSOLE: [iNFO] at net.minecraft.network.TcpConnection.func_74450_c(TcpConnection.java:547)

08:54:24 CONSOLE: [iNFO] at net.minecraft.network.TcpReaderThread.run(SourceFile:94)

08:54:24 CONSOLE: [iNFO] /192.168.154.253:58634 lost connection

08:54:24 CONSOLE: [iNFO] java.io.IOException: Bad packet id 114

08:54:24 CONSOLE: [iNFO] at net.minecraft.network.packet.Packet.func_73272_a(Packet.java:153)

08:54:24 CONSOLE: [iNFO] at net.minecraft.network.TcpConnection.func_74447_i(TcpConnection.java:327)

Any idea how I can fix or hide them, or at least what they mean?

Thanks!

[Chefsbrian]

2013-10-08 09:01:21 [sEVERE] [ForgeModLoader] Detected leaking worlds in memory. There are 4 worlds that appear to be persisting. A mod is likely caching the world incorrectly

Well, that might be the problem. You've got some world issues. Whatever is messed up in memory is causing the server (or your client) to reject some of the information being passed along.

Also, somehow you've been given a Negative length string by the server... I don't even know what could do that...

2013-10-08 09:03:09 [iNFO] [sTDERR] java.io.IOException: Received string length is less than zero! Weird string!

[Gildan27]

For some reason, this almost feels like bad RAM or a bad network card to me...

[Chefsbrian]

If it was a bad network card, we would have failed download or failed to read errors. Memory maybe, but then it shouldn't be just tekkit dying, I'd expect to see a full bsod.

[Gildan27]

If it was a bad network card, we would have failed download or failed to read errors. Memory maybe, but then it shouldn't be just tekkit dying, I'd expect to see a full bsod.

Read errors? Exactly. Something is sending bad packet IDs and bad data, and causing protocol errors. Unless he's connecting with the wrong client or something.