Error

[DgtlRenegade]

http://pastebin.com/KQKTqDpu

I've no idea what this error message means. I believe my computer shut off during server operation and the next time I loaded it, the server wouldn't start and I got this error.

 

[DgtlRenegade]

I can't get the edit button to work but I have a few updates. The level.dat file loads fine in MCEdit suggesting my world is recoverable. Lots of pink blocks (missing textures from mods) so I can't really tell where the issue is but all the chunks seem to load fine. Is there an easy way to disable all chunk loaders so I can make sure the issue isn't just a bad chunk? It would be so much easier to clean my world if I could enter it.

On a side note, I've tried setting the following to true b/c it would appear as though my crash is related to missing blocks.

# 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

Any suggestions would be highly appreciated. If you've seen this error before, please let me know.

 

[DgtlRenegade]

Solution:

This error actually ends up to be level.dat corruption. I could go into extreme detail, but essentially the Redstone mod was failing b/c it was a bad level.dat not because the mod itself was crashing the server. When I deleted the mod, I got new errors pointing towards level.dat. For anyone that doesn't know how to fix level.dat corruption, its pretty simple: make a new server with your old world seed specifically specified. This will generate your level.dat which you can copy paste on to your old level.dat (with the old dimension files). If you don't have your seed, you can try opening level.dat in NBT editor, but only some tags will be shown (the others are corrupt). So its possible you'll never be able to get your seed. You can still fix the server by using a random seed, but it will have weird effects when new chunks load in.

EDIT: I also needed B:removeErroringTileEntities=true b/c with the new level.dat it still needed to remove a few corrupted blocks.

Essentially, this error sucks. But I think I fixed it.

 

[lenscas]

Solution:

This error actually ends up to be level.dat corruption. I could go into extreme detail, but essentially the Redstone mod was failing b/c it was a bad level.dat not because the mod itself was crashing the server. When I deleted the mod, I got new errors pointing towards level.dat. For anyone that doesn't know how to fix level.dat corruption, its pretty simple: make a new server with your old world seed specifically specified. This will generate your level.dat which you can copy paste on to your old level.dat (with the old dimension files). If you don't have your seed, you can try opening level.dat in NBT editor, but only some tags will be shown (the others are corrupt). So its possible you'll never be able to get your seed. You can still fix the server by using a random seed, but it will have weird effects when new chunks load in.

EDIT: I also needed B:removeErroringTileEntities=true b/c with the new level.dat it still needed to remove a few corrupted blocks.

Essentially, this error sucks. But I think I fixed it.

Be careful when fixing things this way as the id mappings are also stored inside the level.dat and they won't always be the same. As a result if you change the level.dat files it may end up that almost all the blocks have changed what they where (for example all the copper ores are now tree logs)

 

[DgtlRenegade]

Be careful when fixing things this way as the id mappings are also stored inside the level.dat and they won't always be the same. As a result if you change the level.dat files it may end up that almost all the blocks have changed what they where (for example all the copper ores are now tree logs)

I always knew this method had some issues but was never told the specifics, thanks for the info. I'll have to keep an eye on the server for a bit. However, I don't know of another way I could have fixed my world.

So far, the only difference is the servers default spawn point is shifted over a few hundred blocks but that's not a big deal. I did look through the .dat file in NBT Explorer and I didn't notice anything I should be concerned about if it was changed.

I am a little concerned about what you said. Are you saying this effect will only occur in new chunks? If so, it may take a while to find. The server is pretty old so a lot of chunks have already been explored, it would be difficult to find new chunks. One of the reasons I typically use worldborder but I opted not to this time :S

 

[lenscas]

I always knew this method had some issues but was never told the specifics, thanks for the info. I'll have to keep an eye on the server for a bit. However, I don't know of another way I could have fixed my world.

So far, the only difference is the servers default spawn point is shifted over a few hundred blocks but that's not a big deal. I did look through the .dat file in NBT Explorer and I didn't notice anything I should be concerned about if it was changed.

I am a little concerned about what you said. Are you saying this effect will only occur in new chunks? If so, it may take a while to find. The server is pretty old so a lot of chunks have already been explored, it would be difficult to find new chunks. One of the reasons I typically use worldborder but I opted not to this time :S

it will have an effect on placed blocks, the vanilla blocks are if I remember correctly hard coded and the rest don't have to be changed.

 

[Henry Link]

Also, this solution seems a little extreme. The initial log you reported indicated a problem with a specific block and it even gave the blocks location in the error log. Did you make backups before you did all of these edits? Also, I strongly suggest you have some type of automated backup process. I know my server is backed up every 6 hours to my dropbox account. There is also some scripting to remove backups older than a week.

 

[DgtlRenegade]

Also, this solution seems a little extreme. The initial log you reported indicated a problem with a specific block and it even gave the blocks location in the error log. Did you make backups before you did all of these edits? Also, I strongly suggest you have some type of automated backup process. I know my server is backed up every 6 hours to my dropbox account. There is also some scripting to remove backups older than a week.

I did make a backup before the edit. However, I did not have a backup directly before the crash. Typically, I keep server backups regularly but I'm on my laptop at a university (not ideal circumstances for a server) and its difficult to keep track on top of.

These edits were the only way I could save the world. Yes, it indicated a problem with a specific block but removing those blocks caused another problem. I deduced it was my broken level.dat file that was causing these specific blocks to break, not the other way around. This is also backed up by the fact that half my level.dat file was missing when I opened it up with NBT and I noticed a lot more null spaces in Notepad++

I did have one small issue with one of the worlds causing crashes. It was not a very important world, so deleting it and moving on seemed to fix the problem. No other issues as of yet.