Server Crash: Help Requested.

Discussion in 'Bukkit Help' started by joshpwnstango, Jul 5, 2013.

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

    joshpwnstango

    ---- Minecraft Crash Report ----
    // On the bright side, I bought you a teddy bear!

    Time: 7/5/13 11:41 AM
    Description: Ticking tile entity

    java.lang.NullPointerException
    at net.minecraft.server.v1_6_R1.TileEntityBrewingStand.l(TileEntityBrewingStand.java:125)
    at net.minecraft.server.v1_6_R1.TileEntityBrewingStand.h(TileEntityBrewingStand.java:83)
    at net.minecraft.server.v1_6_R1.World.tickEntities(World.java:1263)
    at net.minecraft.server.v1_6_R1.WorldServer.tickEntities(WorldServer.java:480)
    at net.minecraft.server.v1_6_R1.MinecraftServer.t(MinecraftServer.java:573)
    at net.minecraft.server.v1_6_R1.DedicatedServer.t(DedicatedServer.java:226)
    at net.minecraft.server.v1_6_R1.MinecraftServer.s(MinecraftServer.java:487)
    at net.minecraft.server.v1_6_R1.MinecraftServer.run(MinecraftServer.java:420)
    at net.minecraft.server.v1_6_R1.ThreadServerApplication.run(SourceFile:582)


    A detailed walkthrough of the error, its code path and all known details is as follows:
    ---------------------------------------------------------------------------------------

    -- Head --
    Stacktrace:
    at net.minecraft.server.v1_6_R1.TileEntityBrewingStand.l(TileEntityBrewingStand.java:125)
    at net.minecraft.server.v1_6_R1.TileEntityBrewingStand.h(TileEntityBrewingStand.java:83)

    -- Tile entity being ticked --
    Details:
    Name: Cauldron // net.minecraft.server.v1_6_R1.TileEntityBrewingStand
    Block type: ID #117 (tile.brewingStand // net.minecraft.server.v1_6_R1.BlockBrewingStand)
    Block data value: 7 / 0x7 / 0b0111
    Block location: World: (2390,59,-32569), Chunk: (at 6,3,7 in 149,-2036; contains blocks 2384,0,-32576 to 2399,255,-32561), Region: (4,-64; contains chunks 128,-2048 to 159,-2017, blocks 2048,0,-32768 to 2559,255,-32257)
    Actual block type: ID #117 (tile.brewingStand // net.minecraft.server.v1_6_R1.BlockBrewingStand)
    Actual block data value: 7 / 0x7 / 0b0111
    Stacktrace:
    at net.minecraft.server.v1_6_R1.World.tickEntities(World.java:1263)
    at net.minecraft.server.v1_6_R1.WorldServer.tickEntities(WorldServer.java:480)

    -- Affected level --
    Details:
    Level name: world
    All players: 3 total; [EntityPlayer['Finalstar123'/217, l='world', x=167.27, y=72.25, z=203.60](Finalstar123 at 167.27277318220752,72.24918707874468,203.60169502036138), EntityPlayer['Kinglief0'/595, l='world', x=32723.68, y=72.00, z=-23187.47](Kinglief0 at 32723.676190445436,72.0,-23187.467897171682), EntityPlayer['mathre190'/765, l='world', x=2392.36, y=58.00, z=-32566.55](mathre190 at 2392.361750278507,58.0,-32566.552088954715)]
    Chunk stats: ServerChunkCache: 1811 Drop: 0
    Level seed: 6612981310136733776
    Level generator: ID 00 - default, ver 1. Features enabled: true
    Level generator options:
    Level spawn location: World: (-83,80,140), Chunk: (at 13,5,12 in -6,8; contains blocks -96,0,128 to -81,255,143), Region: (-1,0; contains chunks -32,0 to -1,31, blocks -512,0,0 to -1,255,511)
    Level time: 5965880 game time, 5920568 day time
    Level dimension: 0
    Level storage version: 0x04ABD - Anvil
    Level weather: Rain time: 54739 (now: false), thunder time: 44559 (now: false)
    Level game mode: Game mode: survival (ID 0). Hardcore: false. Cheats: false
    Stacktrace:
    at net.minecraft.server.v1_6_R1.MinecraftServer.t(MinecraftServer.java:573)
    at net.minecraft.server.v1_6_R1.DedicatedServer.t(DedicatedServer.java:226)
    at net.minecraft.server.v1_6_R1.MinecraftServer.s(MinecraftServer.java:487)
    at net.minecraft.server.v1_6_R1.MinecraftServer.run(MinecraftServer.java:420)
    at net.minecraft.server.v1_6_R1.ThreadServerApplication.run(SourceFile:582)


    That is the crash log that was posted of today, it has been rendering my server usless every few hours: Upon seeing the error in the console the server experiences serious lag, no interactions nor commands can occur save for walking and chat.

    Shortly after that the server completely goes offline.

    I was curious to know if anyone has any fix to this? i have updated to the most recent bukkit build. i have Essentials, groupmanager, factions, vote, votifier, and simpleautoannouncer plugins installed that is all.
     
  2. you have a brewing Stand
    Code:
    Name: Cauldron // net.minecraft.server.v1_6_R1.TileEntityBrewingStand
    Block type: ID #117 (tile.brewingStand // net.minecraft.server.v1_6_R1.BlockBrewingStand)
    Block data value: 7 / 0x7 / 0b0111
    in your world "world", at 2390,59,-32569 (in chunk 149,-2036 at 6,3,7, stored in region file 4,-64)
    Code:
    Block location: World: (2390,59,-32569), Chunk: (at 6,3,7 in 149,-2036; contains blocks 2384,0,-32576 to 2399,255,-32561), Region: (4,-64; contains chunks 128,-2048 to 159,-2017, blocks 2048,0,-32768 to 2559,255,-32257)
    causing a server tick error. the server likely happens when it comes into draw distance/when you get near it. correct?
     
  3. Offline

    joshpwnstango

    im not sure being the owner, with 30-60 average players i assume they have brewing stands. but it seems to be fairly random when it occurs but to say that when it occurs no player is near a stand would be foolish to say. Im going to assume it is likely.
     
  4. Offline

    mbaxter ʇıʞʞnq ɐ sɐɥ ı

    If you're going to use dev builds you need to stay on top of them and not run outdated builds.
     
  5. Offline

    Jade

    That, and read the post Seph made for the release. The one where it states that development builds aren't supported and should only be used if you intend on helping to work toward a beta or recommended build.
     
  6. Offline

    joshpwnstango

    I force update every 12 hours to keep current with devs, figured id report the error as it is something thats been mentioned in previous fixes... But thank you for addressing the most common issues.

    I will say that this most recent dev has seemed to be the most stable. Ive only crashed once today.
     
  7. Offline

    Kuwoobie

Thread Status:
Not open for further replies.

Share This Page