Minecraft server crashing

CliffyG

CliffyG

CliffyG

Soldato
Joined
18 Oct 2002
Posts
17,648
Location
Cambridge
I set up a Minecraft server on my PC way back for me and my boys to play adventure maps together. One playing on the PC running the server and the others connected using laptops. Never had any issues, have even had 2 servers running off the PC at the same time as well as playing the game on it.

Haven't used it in a while but we tried playing the new version of Sky Survival on the weekend on 1.9.2. Downloaded the new server .jar file and got it running using this command:

java -Xmx1024M -Xms1024M -jar minecraft_server.jar nogui

Copied my world data in and connected up. Immediately it became apparent that it was lagging, mined blocks reappeared instantly then a few seconds later disappeared and went into inventory. Eventually it settled down and we played ok for a while. Then the server just crashed. Started it up again same lag and almost instantly crashed again. After the initial play we just can't get it stable. Have noticed loads of these errors on the console:

Can't keep up! Did the system time change, or is the server overloaded?

I had task managed running alongside it and CPU and Memory graphs didn't indicate any problems.

Anyone come across this before or have any ideas?
 
I did try setting to 2048:

java -Xmx2048M -Xms2048M -jar minecraft_server.1.9.2.jar nogui

And it comes up with the following error, even when I set it to 1.5.

Error occurred during initialization of VM
Could not reserve enough space for 2097152KB object heap
 
CPU: Intel Core i5 2500K
Memory: Corsair Vengeance 8GB DDR3 PC3-15000C9 1866MHz
HDD: Samsung 250GB SSD 840 EVO SATA 6Gb/s Basic
 
Have you tried the suggestions on Google when you search for the error message on startup that you're now getting?

Not being glib - I just can't be bothered retyping everything.
 
Only tried it with the adventure map I downloaded.

I had a brief look, not sure any of the ones I found were particularly relevant to my setup but will have another look. Just thought it might be something someone on here had come across.
 
Are you running a 32 bit or 64 bit Java version ? 2 gig of heap on 32 bit Java is pushing it if the jar file is big. No reason not to be on a 64 bit Java version these days.

'java -version' command should tell you.
 
Last edited:
java version "1.8.0_77"
Java(TM) SE Runtime Environment (build 1.8.0_77-b03)
Java HotSpot(TM) Client VM (build 25.77-b03, mixed mode)

Not sure that helps?
 
You must log in or register to reply here.
Back
Top Bottom