Infinity server: Unable to lookup chisel:cobblestoneWall error

  • Tech Support section is for getting help with FTB related problems. If there's a repeatable issue that can be labeled as a bug, then please use the issue tracker for the pack or the app at GitHub issue trackers - If there's no repository for a pack that means that the pack is old and/or will not be updated. Eventual bugs for older packs will not be fixed.

Kreegir

New Member
Jul 29, 2019
4
0
0
Title:
Infinity server: Unable to lookup chisel:cobblestoneWall error
Launcher Version:
1.4.7
Modpack:
Infinity
Modpack Version:
1.5.1
Log Link:
Details of the issue:
hello all

After a week of using my Infinity server i am suddenly getting an error message.

im running it on fedora server 21 with the latest java. this time it crashed the moment my friend tried to login but it has done it where it is just me playing.

[23:18:39] [Netty IO #1/INFO] [FML]: Attempting connection with missing mods [act, JourneyMapServer] at CLIENT
[23:18:41] [Netty IO #1/INFO] [FML]: Unexpected packet during modded negotiation - assuming vanilla or keepalives : net.minecraft.network.play.client.C00PacketKeepAlive
[23:18:41] [Server thread/INFO] [FML]: [Server thread] Server side modded connection established
[23:18:41] [Server thread/INFO] [mcjty.rftools.RFTools]: SMP: Sync dimensions to client
[23:18:41] [Server thread/INFO]: Tralganess[/208.38.6.139:50336] logged in with entity id 115066 at (370.8422113395087, 72.66429868991432, -33.02534237866442)
[23:18:41] [Server thread/INFO] [Waila]: Player EntityPlayerMP['Tralganess'/115066, l='world', x=370.84, y=72.66, z=-33.03] connected. Sending ping
[23:18:41] [Server thread/INFO] [mcjty.rftools.RFTools]: SMP: Player logged in: Sync diminfo to clients
[23:18:41] [Server thread/INFO] [mcjty.rftools.RFTools]: Sync dimension info to clients!
[23:18:41] [Server thread/INFO] [mcjty.rftools.RFTools]: Send validation data to the client
[23:18:41] [Server thread/INFO] [mcjty.rftools.RFTools]: Cleaning up RFTools dimensions
[23:18:42] [Server thread/INFO] [FML]: Unloading dimension 0
[23:18:42] [Server thread/INFO] [FML]: Unloading dimension -1
[23:18:42] [Server thread/INFO] [FML]: Unloading dimension -34
[23:18:42] [Server thread/INFO] [FML]: Unloading dimension -112
[23:18:42] [Server thread/INFO] [FML]: Applying holder lookups
[23:18:42] [Server thread/WARN] [FML]: Unable to lookup chisel:cobblestoneWall for public static com.cricketcraft.chisel.block.BlockMarbleWall com.cricketcraft.chisel.init.ChiselBlocks.cobblestoneWall. Is there something wrong with the registry?
[23:18:42] [Server thread/WARN] [FML]: Unable to lookup chisel:eek:bsidian2 for public static com.cricketcraft.chisel.block.BlockCarvable com.cricketcraft.chisel.init.ChiselBlocks.obsidian2. Is there something wrong with the registry?
[23:18:42] [Server thread/INFO] [FML]: Holder lookups applied
[23:18:42] [pool-3-thread-1/INFO] [EnderIO]: ServerChannelRegister: Dimensional Trasciever data saved to /home/minecraft/Infinity/./world/enderio/dimensionalTransceiver.json
[23:18:42] [Server thread/INFO] [STDOUT]: [mcjty.rftools.RFTools:serverStopped:193]: ###### RFTools.serverStopped
[23:18:42] [Server thread/INFO] [FML]: The state engine was in incorrect state SERVER_STOPPING and forced into state SERVER_STOPPED. Errors may have been discarded.
Server process finished

any help is much appreciated.
 
Last edited:

mc.crab

Well-Known Member
Feb 2, 2013
1,397
116
89
@Kreegir If you are still looking for for a solution, you could try changing these two lines in forge.cfg to true. Make a backup before trying it.

# Set this to true to remove any Entity that throws an error in its update method instead of closing the server and reporting a crash log. BE WARNED THIS COULD SCREW UP EVERYTHING USE SPARINGLY WE ARE NOT RESPONSIBLE FOR DAMAGES.
B:removeErroringEntities=false

# Set this to true to remove any TileEntity that throws an error in its update method instead of closing the server and reporting a crash log. BE WARNED THIS COULD SCREW UP EVERYTHING USE SPARINGLY WE ARE NOT RESPONSIBLE FOR DAMAGES.
B:removeErroringTileEntities=false

@brandonf1218 Do you have a log?