I've been trying to fix my family's world file all day with no luck. My two kids and I have had this vanilla survival world for a couple of years now (vanilla world, SMP, 1.8.1, running server/jar on Linux box). From what I can tell in the logs, my son was playing last night, logged in around 8:29pm, then forgot he was logged in, turned off his monitor, and went to bed. Around 9:48pm in the log file, he drowned.
When he tried to log in this morning, he told me the server had crashed and I needed to restart it (checking the server, there is no log of the crash other than a hs_err_pid.log file created at 2:59am -- hosted here http://drhogie.com/hserr.log ). When I restarted it, I was able to log in with no issues (I was in a different area of the world) -- however whenever he tried to log in he would crash the world. So I told him to wait a bit, I restarted the server, and I logged in and went to his area of the world where he was. When I got to the area where he was at ( guesstimating, maybe ~50-60 blocks from where he died? ) the server crashed.
At this point I copied the world locally and started trying to debug it in single-player. For my given login, insta-crash every time with the same "ticking entity" error. I've tried running "Minecraft Region Fixer", it finds no errors on a scan. I've loaded up the world in MCEdit 1.x and I don't see any entities in the area that seem out of whack. If I move my player ~200 blocks away, the world loads up and I can move around. When I move into the area where the issue happens, it crashes again. I have uploaded the crashlog file for when I approach the area here: http://drhogie.com/crashlog.txt
While typing up this post and tinkering with it, I think I've found the problem. There's an entity that's in a given chunk that MCEdit can see enough to show me there's an entity, but when I analyze the area it doesn't find an entity. Even when I delete all blocks in that chunk, the red box still shows. So, to test, I deleted the entire 16x16x256 chunk from the local copy and reloaded it. I can see in the distance where the chunk has been deleted. When I walk close enough to (I'm guessing load entities? I'm assuming draw distance-wise, it loads blocks/terrain at a much farther distance than it loads entities/mobs) load the entity that doesn't exist, it crashes again. When I reloaded the world into MCEdit, it looks like it moved the non-existant entity into the next closest chunk. I've attached a screenshot of that here: http://drhogie.com/entity1.png -- http://drhogie.com/entity2.png -- http://drhogie.com/entity3.png .
Is there anyway I can get rid of this entity that MCEdit can't find? I'm guessing this is the problem at this point, but I don't really know enough to use MCEdit or NBTExplorer (which is a Minecraft hex editor I'm guessing?) on how to get rid of this. Any and all help would be much much appreciated -- we've put a lot of work into this survival world.
I've been trying to fix my family's world file all day with no luck. ...
While typing up this post and tinkering with it, I think I've found the problem. There's an entity that's in a given chunk that MCEdit can see enough to show me there's an entity, but when I analyze the area it doesn't find an entity. Even when I delete all blocks in that chunk, the red box still shows. So, to test, I deleted the entire 16x16x256 chunk from the local copy and reloaded it. I can see in the distance where the chunk has been deleted. When I walk close enough to (I'm guessing load entities? I'm assuming draw distance-wise, it loads blocks/terrain at a much farther distance than it loads entities/mobs) load the entity that doesn't exist, it crashes again. When I reloaded the world into MCEdit, it looks like it moved the non-existant entity into the next closest chunk. I've attached a screenshot of that here: http://drhogie.com/entity1.png -- http://drhogie.com/entity2.png -- http://drhogie.com/entity3.png .
Is there anyway I can get rid of this entity that MCEdit can't find? I'm guessing this is the problem at this point, but I don't really know enough to use MCEdit or NBTExplorer (which is a Minecraft hex editor I'm guessing?) on how to get rid of this. Any and all help would be much much appreciated -- we've put a lot of work into this survival world.
(EDIT: changed a jpg to png)
If u want to try it on u one:
I have this Problem on 10-20 of worlds i FIx, the entity is someware around the Chunk MC-Edit show it for u.
Fastest way is to mark 8-10 Chunks around this place and use "remove entitys.
If u want taht some one (Maybe i) try to fix the Problem pleas repost her:
The original crash that you had was a crash in the Java internals (garbage collection).
This can sometimes (often?) be a sign of hardware problems (e.g. bad memory) because bugs in the JVM are rare.
However you are using a BETA version of java. Beta versions have many more bugs than release versions.
You may want to switch back to most recent released version of Java, and you may want to run some system diagnostics.
As for the world, as Ritter said, you can delete all entities, which might help, at the cost of wiping any tame / penned mobs in the area (others will respawn). In the crash log the entity being ticked is DrHogie. I don't know if that's the character you were using when the crash happened and is not the buggy entity, or if you were using a different character and your son's character is DrHogie. But it may be his player data that is the problem.
You can move his player data off to the side temporarily. I don't if there's an editor that could be used to fix his data. I imagine there is.
Worse case you delete his data file, and his inventory gets wiped.
The original crash that you had was a crash in the Java internals (garbage collection).
This can sometimes (often?) be a sign of hardware problems (e.g. bad memory) because bugs in the JVM are rare.
However you are using a BETA version of java. Beta versions have many more bugs than release versions.
You may want to switch back to most recent released version of Java, and you may want to run some system diagnostics.
...
Dame did dent notice there are an BETA Java. As u say its good to go back to an stable version.
As for the world, as Ritter said, you can delete all entities, which might help, at the cost of wiping any tame / penned mobs in the area (others will respawn). In the crash log the entity being ticked is DrHogie. I don't know if that's the character you were using when the crash happened and is not the buggy entity, or if you were using a different character and your son's character is DrHogie. But it may be his player data that is the problem.
You can move his player data off to the side temporarily. I don't if there's an editor that could be used to fix his data. I imagine there is.
Worse case you delete his data file, and his inventory gets wiped.
I see the DrHogie entety to, if its the player it wood be nice to delete them (Make a copy before) and reenter the world.
"NBTExplorer" is a good tool to modifier Player and game data files (so long the are in a Minecraft readable format)
U can use them to copy the Player information from the defect profile to a new Profile.
You're both right about the initial crash -- From what i can tell there's a bad stick of RAM in the server. It will run fine for 1-3 weeks then I'll have to restart the server (i.e. the bad section of RAM isn't used until higher RAM usage).
The DrHogie entity is my character name. From what I can tell there's no issues with my entity: If I move the location away from the area everything runs fine. When I get in tonight I'll try it out with my son's character and see if his entity is corrupted or not.
So, my question is this: How far out should I go deleting entities? According to the map that I can tell ( http://hoganmc.net:8080/mc/#/-131/64/562/-4/0/0 ) it's in r-1,1.mca -- should I delete all entities in that entire region? We don't have any tame/penned mobs there, but I do in the large tower located in r-1,0.mca.
Also, what is truly causing this error? Is it an entity that "zigged when it should have zagged", then when the local client tries to load it, everything goes wonky? At this point I'm curious as to what is causing it to crash like this.
Thanks for the help gerbil & Ritter! I'll post an update tonight.
It's hard to say without looking at the code and the data. But if some of the data that's stored in the chunk file is inconsistent and doesn't make sense the code can do weird things that it isn't supposed to do. The crash you posted is an ArrayIndexOutOfBounds exception, this probably means that some number in the file is too big for whatever reason. Maybe it's a position, maybe it's something else. It's supposed to be a number in the range X-Y but it's Z and the code explodes when it uses Z. It's hard to say how this kind of corruption can happen, but let's say for a completely made up example an entity can be loose @ position X,Y,Z or it can be in a chest in slot X. The code crashes at some point where the data is saved inconsistently. It's updated the part of the data that says its in a chest, but it hasn't updated the position indication and it still has the XYZ data in it. Obviously the position in the world has a greater allowed range of X values than a chest does... When the game starts again and tries to put the entity in a chest at some huge X position, it explodes.
I'm currently uploading the fixed world files to our server, but I did as you both suggested: I deleted all entities within the range that everything went wonky with from all the chunks, and I also found the area that kept throwing up an error message about the arrayIndexOutOfBounds -- turns out that chunk wouldn't load at all in MCEdit, so I deleted all blocks within that chunk, replaced them as air, and the world regenerated that 16x16 chunk.
I moved all around the area with zero crashes -- I can't thank both of you enough for helping me out!
No, it's an ESSENTIAL idea. Due to the world size, I didn't have a regular backup scheduled. No longer. I'm doing nightly backups server-side, and weekly backups off-site from now on. If I can ever get the Linux Dropbox going again, I'll start using that.
I've been trying to fix my family's world file all day with no luck. My two kids and I have had this vanilla survival world for a couple of years now (vanilla world, SMP, 1.8.1, running server/jar on Linux box). From what I can tell in the logs, my son was playing last night, logged in around 8:29pm, then forgot he was logged in, turned off his monitor, and went to bed. Around 9:48pm in the log file, he drowned.
When he tried to log in this morning, he told me the server had crashed and I needed to restart it (checking the server, there is no log of the crash other than a hs_err_pid.log file created at 2:59am -- hosted here http://drhogie.com/hserr.log ). When I restarted it, I was able to log in with no issues (I was in a different area of the world) -- however whenever he tried to log in he would crash the world. So I told him to wait a bit, I restarted the server, and I logged in and went to his area of the world where he was. When I got to the area where he was at ( guesstimating, maybe ~50-60 blocks from where he died? ) the server crashed.
At this point I copied the world locally and started trying to debug it in single-player. For my given login, insta-crash every time with the same "ticking entity" error. I've tried running "Minecraft Region Fixer", it finds no errors on a scan. I've loaded up the world in MCEdit 1.x and I don't see any entities in the area that seem out of whack. If I move my player ~200 blocks away, the world loads up and I can move around. When I move into the area where the issue happens, it crashes again. I have uploaded the crashlog file for when I approach the area here: http://drhogie.com/crashlog.txt
While typing up this post and tinkering with it, I think I've found the problem. There's an entity that's in a given chunk that MCEdit can see enough to show me there's an entity, but when I analyze the area it doesn't find an entity. Even when I delete all blocks in that chunk, the red box still shows. So, to test, I deleted the entire 16x16x256 chunk from the local copy and reloaded it. I can see in the distance where the chunk has been deleted. When I walk close enough to (I'm guessing load entities? I'm assuming draw distance-wise, it loads blocks/terrain at a much farther distance than it loads entities/mobs) load the entity that doesn't exist, it crashes again. When I reloaded the world into MCEdit, it looks like it moved the non-existant entity into the next closest chunk. I've attached a screenshot of that here: http://drhogie.com/entity1.png -- http://drhogie.com/entity2.png -- http://drhogie.com/entity3.png .
Is there anyway I can get rid of this entity that MCEdit can't find? I'm guessing this is the problem at this point, but I don't really know enough to use MCEdit or NBTExplorer (which is a Minecraft hex editor I'm guessing?) on how to get rid of this. Any and all help would be much much appreciated -- we've put a lot of work into this survival world.
I've been trying to fix my family's world file all day with no luck. My two kids and I have had this vanilla survival world for a couple of years now (vanilla world, SMP, 1.8.1, running server/jar on Linux box). From what I can tell in the logs, my son was playing last night, logged in around 8:29pm, then forgot he was logged in, turned off his monitor, and went to bed. Around 9:48pm in the log file, he drowned.
When he tried to log in this morning, he told me the server had crashed and I needed to restart it (checking the server, there is no log of the crash other than a hs_err_pid.log file created at 2:59am -- hosted here http://drhogie.com/hserr.log ). When I restarted it, I was able to log in with no issues (I was in a different area of the world) -- however whenever he tried to log in he would crash the world. So I told him to wait a bit, I restarted the server, and I logged in and went to his area of the world where he was. When I got to the area where he was at ( guesstimating, maybe ~50-60 blocks from where he died? ) the server crashed.
At this point I copied the world locally and started trying to debug it in single-player. For my given login, insta-crash every time with the same "ticking entity" error. I've tried running "Minecraft Region Fixer", it finds no errors on a scan. I've loaded up the world in MCEdit 1.x and I don't see any entities in the area that seem out of whack. If I move my player ~200 blocks away, the world loads up and I can move around. When I move into the area where the issue happens, it crashes again. I have uploaded the crashlog file for when I approach the area here: http://drhogie.com/crashlog.txt
While typing up this post and tinkering with it, I think I've found the problem. There's an entity that's in a given chunk that MCEdit can see enough to show me there's an entity, but when I analyze the area it doesn't find an entity. Even when I delete all blocks in that chunk, the red box still shows. So, to test, I deleted the entire 16x16x256 chunk from the local copy and reloaded it. I can see in the distance where the chunk has been deleted. When I walk close enough to (I'm guessing load entities? I'm assuming draw distance-wise, it loads blocks/terrain at a much farther distance than it loads entities/mobs) load the entity that doesn't exist, it crashes again. When I reloaded the world into MCEdit, it looks like it moved the non-existant entity into the next closest chunk. I've attached a screenshot of that here: http://drhogie.com/entity1.png -- http://drhogie.com/entity2.png -- http://drhogie.com/entity3.png .
Is there anyway I can get rid of this entity that MCEdit can't find? I'm guessing this is the problem at this point, but I don't really know enough to use MCEdit or NBTExplorer (which is a Minecraft hex editor I'm guessing?) on how to get rid of this. Any and all help would be much much appreciated -- we've put a lot of work into this survival world.
(EDIT: changed a jpg to png)
normal?
ATTACHMENTS
se nosão
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
When he tried to log in this morning, he told me the server had crashed and I needed to restart it (checking the server, there is no log of the crash other than a hs_err_pid.log file created at 2:59am -- hosted here http://drhogie.com/hserr.log ). When I restarted it, I was able to log in with no issues (I was in a different area of the world) -- however whenever he tried to log in he would crash the world. So I told him to wait a bit, I restarted the server, and I logged in and went to his area of the world where he was. When I got to the area where he was at ( guesstimating, maybe ~50-60 blocks from where he died? ) the server crashed.
At this point I copied the world locally and started trying to debug it in single-player. For my given login, insta-crash every time with the same "ticking entity" error. I've tried running "Minecraft Region Fixer", it finds no errors on a scan. I've loaded up the world in MCEdit 1.x and I don't see any entities in the area that seem out of whack. If I move my player ~200 blocks away, the world loads up and I can move around. When I move into the area where the issue happens, it crashes again. I have uploaded the crashlog file for when I approach the area here: http://drhogie.com/crashlog.txt
While typing up this post and tinkering with it, I think I've found the problem. There's an entity that's in a given chunk that MCEdit can see enough to show me there's an entity, but when I analyze the area it doesn't find an entity. Even when I delete all blocks in that chunk, the red box still shows. So, to test, I deleted the entire 16x16x256 chunk from the local copy and reloaded it. I can see in the distance where the chunk has been deleted. When I walk close enough to (I'm guessing load entities? I'm assuming draw distance-wise, it loads blocks/terrain at a much farther distance than it loads entities/mobs) load the entity that doesn't exist, it crashes again. When I reloaded the world into MCEdit, it looks like it moved the non-existant entity into the next closest chunk. I've attached a screenshot of that here: http://drhogie.com/entity1.png -- http://drhogie.com/entity2.png -- http://drhogie.com/entity3.png .
Is there anyway I can get rid of this entity that MCEdit can't find? I'm guessing this is the problem at this point, but I don't really know enough to use MCEdit or NBTExplorer (which is a Minecraft hex editor I'm guessing?) on how to get rid of this. Any and all help would be much much appreciated -- we've put a lot of work into this survival world.
(EDIT: changed a jpg to png)
If u want to try it on u one:
I have this Problem on 10-20 of worlds i FIx, the entity is someware around the Chunk MC-Edit show it for u.
Fastest way is to mark 8-10 Chunks around this place and use "remove entitys.
If u want taht some one (Maybe i) try to fix the Problem pleas repost her:
http://www.minecraftforum.net/forums/minecraft-discussion/discussion/297844-official-corrupted-save-recovery-thread?page=91
This can sometimes (often?) be a sign of hardware problems (e.g. bad memory) because bugs in the JVM are rare.
However you are using a BETA version of java. Beta versions have many more bugs than release versions.
You may want to switch back to most recent released version of Java, and you may want to run some system diagnostics.
As for the world, as Ritter said, you can delete all entities, which might help, at the cost of wiping any tame / penned mobs in the area (others will respawn). In the crash log the entity being ticked is DrHogie. I don't know if that's the character you were using when the crash happened and is not the buggy entity, or if you were using a different character and your son's character is DrHogie. But it may be his player data that is the problem.
You can move his player data off to the side temporarily. I don't if there's an editor that could be used to fix his data. I imagine there is.
Worse case you delete his data file, and his inventory gets wiped.
Dame did dent notice there are an BETA Java. As u say its good to go back to an stable version.
I see the DrHogie entety to, if its the player it wood be nice to delete them (Make a copy before) and reenter the world.
"NBTExplorer" is a good tool to modifier Player and game data files (so long the are in a Minecraft readable format)
U can use them to copy the Player information from the defect profile to a new Profile.
The DrHogie entity is my character name. From what I can tell there's no issues with my entity: If I move the location away from the area everything runs fine. When I get in tonight I'll try it out with my son's character and see if his entity is corrupted or not.
So, my question is this: How far out should I go deleting entities? According to the map that I can tell ( http://hoganmc.net:8080/mc/#/-131/64/562/-4/0/0 ) it's in r-1,1.mca -- should I delete all entities in that entire region? We don't have any tame/penned mobs there, but I do in the large tower located in r-1,0.mca.
Also, what is truly causing this error? Is it an entity that "zigged when it should have zagged", then when the local client tries to load it, everything goes wonky? At this point I'm curious as to what is causing it to crash like this.
Thanks for the help gerbil & Ritter! I'll post an update tonight.
I'm currently uploading the fixed world files to our server, but I did as you both suggested: I deleted all entities within the range that everything went wonky with from all the chunks, and I also found the area that kept throwing up an error message about the arrayIndexOutOfBounds -- turns out that chunk wouldn't load at all in MCEdit, so I deleted all blocks within that chunk, replaced them as air, and the world regenerated that 16x16 chunk.
I moved all around the area with zero crashes -- I can't thank both of you enough for helping me out!
Thanks again!
normal?