Whenever anyone gets near a certain location in a certain world on my server, it crashes. It doesn't matter how many people are connected, it always crashes and the client displays read timed out. I did some hunting and found that an entity in the wrong place could cause this, so I opened up the world using mcedit and removed two ender crystals that were floating up in the sky. But, when I went back on to the server, It still crashed. As soon as I got to the location, Chunks stopped loading and eventually it gave me read timed out. Is this caused by world corruption or something else and is there any way I can fix this or will I have to delete the world? I have disabled all of my plugins. I'm not sure if we are allowed to bump... Why, why won't anyone reply? EDIT by Moderator: merged posts, please use the edit button instead of double posting.
Please wait a full day to bump, Try removing the entire chunks and letting them regenerate and see if that works.
How do I do that? Because i cant with worldedit because i cant get near the spot where it crashes without it crashing...
If that happened with WE, then restart your server, then delete all of the players .dat files in essentials that are having the problem.
No, i made a mistake. Delete the essentials .yml files for the players that are effected. That will remove their homes, last place, and nicknames. Dont touch the .dat files. My bad.
and also fix completely nothing, as essentials has nothing to do with the crash. the file that needs deletion is the WORLD player.dat, as that stores location.
Essentials files saves location...I have had this same exact error on my server, I deleted the player.yml file of the affected people. Look I'm here to give suggestions. You can go act like a smart ass somewhere else, as I have seen you give advice that isn't correct.
... what you say is a lie, because that data in the YML doesnt effect anything, essentials teleport people on log on, this data is for dynmap. player.dat is the ONLY thing that saves the actual player location.
it SAVES your location, it doesnt MODIFY the location. you can modify that entry and nothing will happen. delete the file and the player will be at the exact same place.
Dude I'm giving advice, something EXACTLY like this happened on my server. If you can't accept the fact others give advice, keep it to yourself. Deleting the .dat files will work, but I'm telling when I had this exact error and deleting the .yml file worked for me.
essentials last location saving is not what the server on log on. last location is called only when saved on player quit. there is no possible way that modifying this entry would effect it in anyway. https://github.com/essentials/essentials/tree/2.9
It fixed my fucking error before. I'm just fucking giving advice. All you do on bukkit is act like a little prick to other members, and look like some hotshot. I'm done arguing with you, we don't need to both act childish in a public thread.
are you seriously saying that the essentials userdata causes local chunk corruption which is fixed on deleting the files? why do you blame essentials for no reason?
Never did I say it causes shit. The plugin saves locations. Want to k ow what other plugins save locations that can help out? Bukkit for starters, any multiworld plugin, most anti grief plugins, hell even autofireworks saves player locations. There is always more than one answer to an open ended question.
I dont think the problem is a player location. Whenever any player goes in a certain direction from the portal I have in the world, chunks stop loading and it crashes. I have deleted my own Sigong.dat file in my world folder numerous times (necrodoom is right that that is the position) and every time I go to this location it crashes. If the fix would be to regenerate chunks, I dont know which chunk has the problem and many people have built stuff in that area, so It would be tricky. Is there any way to determine which chunk(s) is causing the problem?
Nothing except [Warning] Can't keep up! Did the system time change or is the server overloaded? Then it crashes and gives the console read timed out. So there must be something in that direction that causes so much lag the server crashes.
Nothing that I can find. I'm assuming its an entity causing this problem. Is there any way to teleport to stuff on mcedit?
dont think so. if you know where the problematic area is, you could probably try /clear, /stoplag or /killall if you have plugins that does them near the area.
Try using Minecraft Region Fixer - run your world through that with the verbose option. You may have thousands of entities in one area killing your server when that chunk is loaded. Minecraft Region Fixer can purge them
I used it and it says it deleted 3519 entities in chunk (6,25). Could this have been what was causing the problem?
