Disconnected by Server: Internal server error

[DarkDuck]

On my home server the log reads
"Minerduck disconnected - internal error"

Thats the only log as it's not a crash. I have experienced this myself once or twice, but for it to happen to me I have to try and access the ui of a redpower circuit (say a state cell) while holding a nano sabre.

this is a known issue but cannot be fixed as minecraft will insist on doing both the activation of the sabre and cell.

[Phlexor]

Yep, trying to work out the link book disconnection. The chainsaw issue in the twilight is also a known and long standing issue, the link book one is new.

[Phlexor]

Okay, it happened again and I had Debug level logging turned on in the console. Nothing showed up at all except the normal Loading World message:

2013-03-03 13:56:18 [INFO][STDOUT] Loading World: remote/220.233.153.44~25565/ftb_world

Considering this never happened before the downtime and nothing has changed on the client end, it HAS to be a server problem, nothing that I can do about it further.

[Sorontar]

The server at that time said the following in response:

2013-03-03 13:56:58 [WARNING] Failed to handle packet for Phlexor72/116.240.162.84: java.lang.NullPointerException

The error log says:

2013-03-03 13:56:55 [INFO] [STDOUT] Sending serverside check to: Phlexor72
2013-03-03 13:56:56 [INFO] [ForgeModLoader] [Thaumcraft] Removed 587 aura nodes when world 41 unloaded.
2013-03-03 13:56:58 [INFO] [ForgeModLoader] Unloading dimension 41
2013-03-03 13:56:58 [SEVERE] [ForgeModLoader] A critical server error occured handling a packet, kicking 2282995
2013-03-03 13:56:58 [WARNING] [Minecraft] Failed to handle packet for Phlexor72/116.240.162.84: java.lang.NullPointerException
2013-03-03 13:56:58 [INFO] [STDOUT] Unloading Player: Phlexor72
20

So the server is not really saying why it failed to handle the packet. However it later responds to another attempt saying:

2013-03-03 13:59:59 [FINEST] [ForgeModLoader] Received valid FML login packet from /116.240.162.84:63622
2013-03-03 13:59:59 [INFO] [Minecraft] User Phlexor72 connecting with mods [ThermalExpansion, RedPowerWiring, BuildCraft|Silicon, APUnofficial, TwilightForest, OmniTools, ThermalExpansion|Transport, BuildCraft|Transport, GraviSuite, IC2NuclearControl, BuildCraft|Core, RedPowerCompat, ThermalExpansion|Factory, MoCreatures, RedPowerLogic, ObsidiPlates, IC2, ThermalExpansion|Energy, drceph.petrogen, ExtrabiomesXL, StevesCarts, Thaumcraft, ExtraBees, TC, Mystcraft, Forestry, ComputerCraft, BinnieCore, AdvancedMachines, AdvancedSolarPanel, BuildCraft|Factory, IronChest, RedPowerMachine, BuildCraft|Energy, GregTech_Addon, Railcraft, RedPowerCore, MiscPeripherals, PortalGun, CCTurtle, ModularForceFieldSystem, RedPowerControl, factorization, RedPowerLighting, RedPowerBase, BuildCraft|Builders, RedPowerWorld]
2013-03-03 13:59:59 [INFO] [Minecraft] Phlexor72[/116.240.162.84:63622] logged in with entity id 6431100 at (-307.5, 66.2, 478.5)
2013-03-03 13:59:59 [INFO] [STDOUT] Loading Player: Phlexor72
2013-03-03 13:59:59 [INFO] [STDOUT] Sending serverside check to: Phlexor72

So obviously there were issues with the login packet. It is not clear whether it is the client or server's fault.

Sorontar

[Phlexor]

I read somewhere that having a Train Workbench where you spawn to (login or TP) can cause crashes, and it does sometimes crash the client with the normal error log (not internal sever error), so I removed the Train Workbench (which in itself caused a crash). I'll see how things go, but I don't think its related. Worth a shot though.