[1.43 SMP] Server Crash - Unknown Cause

I logged on to see my server crashed with the following NPE.

Description: Exception in server tick loop
java.lang.NullPointerException
at up.p(World.java:2576)
at dan200.computer.shared.BlockComputerBase.getPeripheralAt(BlockComputerBase.java:143)
at dan200.computer.shared.BlockComputerBase.refreshInput(BlockComputerBase.java:190)
at dan200.computer.shared.BlockComputerBase.a(BlockComputerBase.java:159)
at up.m(World.java:677)
at up.h(World.java:659)
at dan200.computer.shared.NetworkedComputerHelper.update(NetworkedComputerHelper.java:115)
at dan200.computer.shared.TileEntityComputer.g(TileEntityComputer.java:104)
at up.h(World.java:1938)
at gr.h(WorldServer.java:439)
at net.minecraft.server.MinecraftServer.q(MinecraftServer.java:632)
at ft.q(DedicatedServer.java:241)
at net.minecraft.server.MinecraftServer.p(MinecraftServer.java:563)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:469)
at ep.run(SourceFile:539)

This is CC 1.43 running on Forge 297.

Mods I'm using:

Spoiler

NullPointerException Search for this or read the many other post that are just like this with the same failure information.
You need to use a different version of Forge.

Wasn't 1.43 released to address compatibility with latest Forge releases?

Yes - and this is not a compatibility issue. It seems something is up in a mod which edits base classss - we don't touch the code which errored.

What mods are you using in your jar?

Cloudy, on 06 October 2012 - 11:05 AM said:

Yes - and this is not a compatibility issue. It seems something is up in a mod which edits base classss - we don't touch the code which errored.

What mods are you using in your jar?

There aren't any mods in the server jar besides Forge 297.

If the client side could have somehow crashed the server, the client has NEI and Optifine as well as Forge 297.

Well, I've just looked into the code which is causing the issue - and it definitely isn't our issue. This is an NullPointerException inside World.java - not sure how it could have happened, but there is no fault in our code.

Interesting. Been running for ~12 hours since the original post without issue. Hopefully it will not present a frequent problem.