FTB Ultimate Server - Unable to log in (1.1.2)

  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
Status
Not open for further replies.

Kaise123

New Member
Jul 29, 2019
2
0
0
Alright, Hopefully I can get some help with this here as some extensive Googling has only gotten me some limited information.

Yesterday, I was on my FTB server, It's a private server set up for myself and some friends. While I was mining up some Blue alloy wire, It suddenly wouldn't mine (Made the block breaking animation but never disappeared). I waited a bit thinking it was just a lag spike, Then it didn't fix so I disconnected. After that, I was unable to connect to the server, Both the server AND the client showed the same error after waiting at the 'Logging in' screen for some time:

Code:
2013-08-22 09:39:33 [INFO] [STDERR] java.net.SocketTimeoutException: Read timed out
2013-08-22 09:39:33 [INFO] [STDERR] at java.net.SocketInputStream.socketRead0(Native Method)
2013-08-22 09:39:33 [INFO] [STDERR] at java.net.SocketInputStream.read(Unknown Source)
2013-08-22 09:39:33 [INFO] [STDERR] at java.net.SocketInputStream.read(Unknown Source)
2013-08-22 09:39:33 [INFO] [STDERR] at java.net.SocketInputStream.read(Unknown Source)
2013-08-22 09:39:33 [INFO] [STDERR] at java.io.FilterInputStream.read(Unknown Source)
2013-08-22 09:39:33 [INFO] [STDERR] at ef.a(Packet.java:142)
2013-08-22 09:39:33 [INFO] [STDERR] at cg.i(TcpConnection.java:324)
2013-08-22 09:39:33 [INFO] [STDERR] at cg.c(TcpConnection.java:544)
2013-08-22 09:39:33 [INFO] [STDERR] at ch.run(SourceFile:93)

Thinking it was my internet, I rebooted my modem/router, But I got the same thing. Then, I thought the server must have crashed/frozen, So I logged in (Via SSH, I'll add server details below) and tried to reboot it. It froze shutting down while saving the world, So I used ctrl-c to terminate it, Thinking that it was probably just a bug. However, After it started again nothing had changed and I still had the same error, And it also occurred for any other person trying to log in.

So, I downloaded all the server files and ran it locally, Same issue. After some searching, I found it suggested that it could be a machine or something in my world loaded by chunk loaders that was causing it to freeze, In other words the world was corrupted. All suggestions I have found just say to restore to an earlier backup. Unfortunately, I don't have ANY backups of the server, Which is very stupid I know.

Now, I know that the rules/FAQ section says that no support is offered for fixing world corruption but in this case I think it should be recoverable, If someone could tell me where to go from here? I am able to load the world up in MCEdit without issue, And the server also works just by removing the region file from the world directory (So it just seems to be the main overworld that is affected). Can anyone tell me how I can find what area is causing this so I can remove it with McEdit? There are no more than 4 chunk loaders in the world, And they have been there for quite some time without issue. I've tried the 'Fix regions' option in MCEdit, And also selecting all and removing entities, which doesn't work either.

If I can't just remove the affected chunk/block, Could someone tell me if I can copy/paste the entire world into a schematic and then paste it into the same place on a new seed, And whether that would work?

Some additional general information:
Server:
CentOS 5.9 x64 VPS with 2GB of RAM
Been running for around 2 months non stop with fairly minimal activity. No bugs have been encountered during this time that affected the server.
There is no error about the world when the server loads. Here are the logs from running it locally on my PC: (ForgeModLoader-server-0.log, More than 500KB so I couldn't pastebin it: http://www.kaise123.com/minecraft/ForgeModLoader-server-0.log )

Thanks in advance for any assistance :)
 

Kaise123

New Member
Jul 29, 2019
2
0
0
This is clearly a problem with the connection between client-server or data transfer. It could be a problem with the client installation or server installation. Backup your saves and try reinstalling the server. Try logging in to other servers. There is a thread on Minecraft Forums on this.


As I said in my post, I had tried restarting the server, client, and networking equipment on my end. The issue also occurred, as stated, to another friend of mine trying to connect from a different location. I also stated that it didn't work when I download the server and ran it locally, either.

I have however resolved it myself after many hours of tinkering. For anyone else who arrives here with this issue, For me it was something in the world that was stopping anyone from connecting, as it was freezing the server, as that chunk was loaded by a chunkloader.

What had happened was I was upgrading my friend's magma crucible - reconfiguring the wiring so that it was neater and slightly more efficient. We have our crucibles set up using Bluetricity coming from solar panels, Going into a (Bluelectric) battery box. After the battery box, a bluelectric engine is used to power the crucible itself. Then, A loop is made from a chest going past the crucibles with netherrack keeping them full at all times, then returning to the chest. The issue that was causing the corruption/glitch in the world was that when I placed the battery box down, The pipe below it with the netherrack cycling past had connected to it, causing the netherrack to be deposited into what I think is a charging slot in the battery box. AS SOON as the netherrack went into the battery box, I was instantly disconnected with the 'read timed out' error, And unable to reconnect.

I was able to fix it by removing the crucibles/battery boxes with MCEdit. Then, I re uploaded the world and everything worked fine. The reason that I know that it was the Netherrack causing it is that I replaced the magma crucibles and set them up the same way again, and it happened for a second time at the exact same time. I then just re-uploaded the fixed region file that I knew it was in (In my case, r.-1.-1.mca) and it worked again. This time I moved the battery boxes back and the server has run smoothly ever since.

So my suggestion is that if this happens to you and it's not your internet or the connection to the server, Then try using MCedit to remove areas of the world that players were in right before it happened (MCEdit will show where players were located in the world) and delete the sections. IF that fixes it, Narrow it down until you can remove just the glitched/corrupted blocks, or live with the damage.

Hopefully I helped if anyone else has this issue, As I couldn't find it anywhere even after I knew the cause. And good luck if it happens to you :)
 
Status
Not open for further replies.