Server Error caused by map corruption.

Discussion in 'Bukkit Help' started by osholt, Mar 9, 2011.

Thread Status:
Not open for further replies.
  1. Offline

    osholt

    I run a small server which suffers from the occasional random shut down.

    These random shut downs have become more frequent recently.

    My server is now repeatedly turning out errors like
    Code:
    2011-03-09 17:40:53 [INFO] Chunk (-5, -4) stored at  (-12, -5)
    2011-03-09 17:40:53 [SEVERE] java.lang.Throwable
    2011-03-09 17:40:53 [SEVERE] 	at org.bukkit.craftbukkit.util.LongHashtable.get(LongHashtable.java:34)
    2011-03-09 17:40:53 [SEVERE] 	at net.minecraft.server.ChunkProviderServer.b(ChunkProviderServer.java:109)
    2011-03-09 17:40:53 [SEVERE] 	at net.minecraft.server.World.c(World.java:202)
    2011-03-09 17:40:53 [SEVERE] 	at net.minecraft.server.World.getTypeId(World.java:145)
    2011-03-09 17:40:53 [SEVERE] 	at org.bukkit.craftbukkit.CraftWorld.getBlockTypeIdAt(CraftWorld.java:60)
    2011-03-09 17:40:53 [SEVERE] 	at org.dynmap.kzedmap.DefaultTileRenderer.scan(DefaultTileRenderer.java:115)
    2011-03-09 17:40:53 [SEVERE] 	at org.dynmap.kzedmap.DefaultTileRenderer.render(DefaultTileRenderer.java:82)
    2011-03-09 17:40:53 [SEVERE] 	at org.dynmap.kzedmap.KzedMap.render(KzedMap.java:189)
    2011-03-09 17:40:53 [SEVERE] 	at org.dynmap.MapManager.render(MapManager.java:193)
    2011-03-09 17:40:53 [SEVERE] 	at org.dynmap.MapManager$1.handle(MapManager.java:36)
    2011-03-09 17:40:53 [SEVERE] 	at org.dynmap.MapManager$1.handle(MapManager.java:1)
    2011-03-09 17:40:53 [SEVERE] 	at org.dynmap.AsynchronousQueue.running(AsynchronousQueue.java:92)
    2011-03-09 17:40:53 [SEVERE] 	at org.dynmap.AsynchronousQueue.access$000(AsynchronousQueue.java:10)
    2011-03-09 17:40:53 [SEVERE] 	at org.dynmap.AsynchronousQueue$1.run(AsynchronousQueue.java:58)
    2011-03-09 17:40:53 [SEVERE] 	at java.lang.Thread.run(Unknown Source)
    2011-03-09 17:40:53 [INFO] Chunk (-5, -4) stored at  (-12, -5)
    2011-03-09 17:40:53 [INFO] net.minecraft.server.Chunk
    2011-03-09 17:40:53 [SEVERE] java.lang.Throwable
    2011-03-09 17:40:53 [SEVERE] 	at net.minecraft.server.ChunkProviderServer.b(ChunkProviderServer.java:117)
    2011-03-09 17:40:53 [SEVERE] 	at net.minecraft.server.World.c(World.java:202)
    2011-03-09 17:40:53 [SEVERE] 	at net.minecraft.server.World.getTypeId(World.java:145)
    
    constantly.

    I know part of it is due to Dynmap which is being triggered by the map errors.
    The rest (I think is being caused by the map being partially corrupted.
    The entire map loads fine, if a bit slowly, but I do now experience huge lag when placing and destroying blocks in certain parts of the map and sometimes it doesn't work at all.

    Is there any way of fixing this and if not can you recommend a decent periodic backup plugin.

    Thank you in advance.

    osholt
     
  2. Offline

    Snakeruler

    I'd probably reccomend backing up your world folder, and deleting the original, if the maps corrupted; A new map should help fix that.

    (The back up is just incase it's still the same, so you can restore when needed.)
     
  3. Offline

    osholt

    I've been doing the odd backup like that once every few days, but my last map was corrupted the night before last and the new one put in place last night. We've already built tons and we really would like to keep it. The map itself is actually intact it's just some of the behind the scenes stuff isn't working properly.

    If anyone has any idea of actually how to fix the map or can at least tell me what this error actually refers to specifically then please tell me. If not, I will start my 4th new map in 2 weeks.
     
  4. Offline

    JemiloII

  5. Offline

    AdventurerOK

    Download MCEdit and open your world, then press Ctrl then I
    when the box pops up click repair regions, after a while it will say chunk -(5,-4) stored at( -12,-5)
    When I had this I actually saw the chunks right next to each other, both the same!
    By the way this will delete chunk (-12,-5)
     
Thread Status:
Not open for further replies.

Share This Page