Ben Campbell

you forgot to mention that it doesn't matter because minecraft is a dead game since mojang spent 5+ years making horrible updates and now MS owns it and they don't plan to update it. lol.

McDodge your logic is flawed but no point in arguing since I agree that 1.8 need to go back into beta. There just isn't enough stability or new features/content in 1.8 to justify it's release. But I guess that's just my opinion as a gamer and developer.

@McDodge: Concerning Server-Client wired in the same room I had this issue as well and found out my map was corrupted. I used MCEdit to manually delete the corrupted blocks (actual single corrupted blocks, typically entities gone bad for some reason or another) and then the server worked again. This goes back to an earlier issue with map corruption that was prevalent in the snapshots around the same time Bunnies were introduced. I didn't have time to go back and look for your server specs but have you tried using a fresh map or using MC edit to check for fixable map corruption?

@Kyle: Concerning RAM and too many entities. I built a machine that spawned way too many zombies and got this error constantly until I used MC edit to manually delete entities from the server. I also had a lot of issues trying to max out the RAM my server was using. Part of the problem is that if you dedicate too much RAM to the server then the computer can't commit memory to the processes it needs to run the server in the first place and keep the OS going, etc, and that will cause major lag and netty time-out.

Like was stated before there is no one single solution to this issue. You best chance at resolving this problem is to do further debugging on your map to see if you can find and resolve whatever it is that is making your server lag or time-out.

Heck, even just keeping Wi-Fi active on your router can enable unwanted hackers to break into your internet without your knowledge, causing just enough lag to force this time-out. Try disabling your Wi-Fi on your router maybe? I have a million suggestions to this problem.

People need to relax about this "Error" because that is exactly what it is. An error message. It is not a glitch or a bug. It is an error message that is telling you that the asychnronous netty event timed-out.

Even if Mojang fixed 110% of every glitch and bug in MC some people would STILL see this ERROR MESSAGE from time-to-time, when their communication with the server in question has timed out (usually at log-in).

Typical causes for this ERROR MESSAGE:

1) The server sucks and doesn't have enough RAM, or is bogged down with buggy plug-ins, or the server is lagging because it is trying to process too much at once (Admin built a super-crazy redstone clock, too many entities on the map, etc).

2) The End-User has a crappy computer and is taking too long to load the map.

3) The ISP or internet connection of the server itself is bad or slow or bogged down(in the case that it's normally a good connection)

4) The ISP or internet connection of the player is experiencing similar problems as above.

To conclude this post there are basically a ton of reasons you may see this error message, and those reasons themselves are what need to be fixed, not this error message. I several times solved this issue on my server simply by doing a /kill @e command.

This was labeled as a dupe however using the resolution in the dupes did not fix the issue, and therefore i do not believe it is the same issue.

I am using a Surface 2 Pro 256gig to play MC personally however this issue has been confirmed by almost everyone else I've talked to since the snapshot came out on wednesday and they are all using completely different computers.. macs and PCs alike.

It really seems nothing like the duplicate issues describe.

If an issue is going to be marked as duplicate, the person who marks it better be damn sure about it. I'm not getting paid for these reports.

I tried to run 14w27b with several old maps, a de-corrupted 14w26c map, and a fresh map, and still got the same exact "ERROR StatusLogger" error. I threw out my 14w26a-b maps when 26c was released so I do not think any of my maps have that 14w26 issue except for maybe the one 14w26c map that I managed to de-corrupt with MC edit by deleting entities. I really gotta start waiting a week or two before trying these snapshots out lol.

History: Updated to 14w26b, then used a pre-w26 back-up world with 14w26c. Worked fine all night. Next morning when trying to log in I got the io.netty.handler.timeout.ReadTimeoutException with 3 separate accounts. The only error on the Server side is "[User authenticator #1]/INFO: UUID of player (player) is (string).

Tried deleting player data as well as user cache. No change.

Tried loading my pre-w26 map with 14w26c and it is loading again, however my 14w26c map, which of course I put about 18 hours of work into in one day, will no longer load, even with the 14w26c snapshot.

Sorry for lack of detail this is my first post here.

EDIT: I tried to open my broken 14w26c map in MCEdit, and it opened, so I flew around the map a bit until it started to lag a lot by a new mob arena that I created with command blocks. The entities show up as red blocks in MCEdit and before logging out previously my son had decided to change all of the Zombie heads to Sand blocks. I don't know if that had anything to do with it but I selected the area in MCEdit and used the Delete Entities option and the lag went away and the map now once again works using snapshot 14w26c and I was able to salvage all the work I thought I lost. I know this isn't an MCEdit forum but it allowed me to correct the issue.