I'm suddenly getting a constant server crash almost immediately after starting up. I've been running 1.10 all day today without a problem, but suddenly this started this evening. This is a vanilla private server.
Your server is shutting down due to lag try upping your ram and finish configuring your java arguments to match your hardware
That has never happened prior to 1.10 though. There are only 4 people on this server and it has plenty of RAM. I've been running this machine as a server since 1.2 under the same conditions.
Mc is slowly getting more intensive CPU and ram wise but your crash report shows watching server which is like a safety net to stop the server as it can't tick fast enough and to prevent damage. And your java arguments are incomplete as they only show your ram configured these need to machines your hardware same as you do in your client
Mc is slowly getting more intensive CPU and ram wise but your crash report shows watching server which is like a safety net to stop the server as it can't tick fast enough and to prevent damage. And your java arguments are incomplete as they only show your ram configured these need to machines your hardware same as you do in your client
So what you are saying is that 1.10, a pretty small little patch, suddenly means a 4 player server requires more RAM than 5GB? I'm just not buying that. It crashes when I'm the only one on, so really a 1 player server requires more than 5GB? Where as 1.9.4 ran perfectly fine, and 5GB was really overkill.
As for these java arguments, unless you have documentation on them, your statement is meaningless to me. My server is set up as Mojang suggests it right here... https://minecraft.net/en/download/server. Simply stating "finish your java arguments" doesn't help, I have no idea what that means.
Sorry I miss read your ram amount as for the java arguments there are plenty of documentation here in the forums and just searching the web as mojang don't provide and java configuration as the combinations of hardware, operating systems and server types is just two much which is why they leave it to you to enter in the client and server start up script's.
Well look, while it might be nice to have those arguments which I can find no info on anywhere (and I'm beginning to question whether they actually exist). I'm certain it isn't required as I've never had them before. I'm fairly certain 1.10 has corrupted something. My only question is can it be fixed or do I need to revert to a backup and abandon 1.10 until they bring out a patch to prevent this?
Ok, so it turns out it was corrupted entities. I noticed some lines on server start indicating it was "Keeping entity [x] that already existed". I'd never seen those lines on startup before. So I used the kill command and suddenly lag went away and server stopped crashing. Definitely appears to be a bug in 1.10.
[noparse][14:11:42 INFO]: Starting minecraft server version 1.10
[14:11:42 INFO]: Loading properties
[14:11:42 INFO]: Default game type: SURVIVAL
[14:11:42 INFO]: Generating keypair
[14:11:42 INFO]: Starting Minecraft server on *:25565
[14:11:42 INFO]: Using default channel type
[14:11:42 INFO]: Preparing level "world"
[14:11:43 INFO]: Preparing start region for level 0
[14:11:44 INFO]: Preparing spawn area: 2%
[14:11:44 WARN]: Keeping entity Pig that already exists with UUID f0b0087d-05b0-40fc-aaef-867d04f46f7e
[14:11:44 WARN]: Keeping entity Pig that already exists with UUID a1f28568-8593-4e10-aeda-6ed6e139e925
[14:11:44 WARN]: Keeping entity Chicken that already exists with UUID 5e09b1c9-63f5-4294-93f6-3b064d535555
[14:11:45 INFO]: Preparing spawn area: 57%
[14:11:45 WARN]: Keeping entity Chicken that already exists with UUID 4a12b1a7-1423-4d06-8703-df08f3126875
[14:11:45 INFO]: Done (2.953s)! For help, type "help" or "?"
[14:14:32 INFO]: Killed Chicken
[14:14:42 INFO]: Killed Chicken
[14:14:52 INFO]: Killed Pig
[14:15:03 INFO]: Killed Pig[/noparse]
We are getting this incessantly and even after killing them, they come back. I've stayed in the same spot, killed the same mob listed in the log 4 times and it still comes back. Have you seen the same behaviour, or did your problem completely go away?
I'm suddenly getting a constant server crash almost immediately after starting up. I've been running 1.10 all day today without a problem, but suddenly this started this evening. This is a vanilla private server.
http://pastebin.com/f9HKC1HM
Your server is shutting down due to lag try upping your ram and finish configuring your java arguments to match your hardware
That has never happened prior to 1.10 though. There are only 4 people on this server and it has plenty of RAM. I've been running this machine as a server since 1.2 under the same conditions.
I'm fairly certain this is a new issue with 1.10.
Mc is slowly getting more intensive CPU and ram wise but your crash report shows watching server which is like a safety net to stop the server as it can't tick fast enough and to prevent damage. And your java arguments are incomplete as they only show your ram configured these need to machines your hardware same as you do in your client
So what you are saying is that 1.10, a pretty small little patch, suddenly means a 4 player server requires more RAM than 5GB? I'm just not buying that. It crashes when I'm the only one on, so really a 1 player server requires more than 5GB? Where as 1.9.4 ran perfectly fine, and 5GB was really overkill.
As for these java arguments, unless you have documentation on them, your statement is meaningless to me. My server is set up as Mojang suggests it right here... https://minecraft.net/en/download/server. Simply stating "finish your java arguments" doesn't help, I have no idea what that means.
Sorry I miss read your ram amount as for the java arguments there are plenty of documentation here in the forums and just searching the web as mojang don't provide and java configuration as the combinations of hardware, operating systems and server types is just two much which is why they leave it to you to enter in the client and server start up script's.
One of the issues of being java based
Well look, while it might be nice to have those arguments which I can find no info on anywhere (and I'm beginning to question whether they actually exist). I'm certain it isn't required as I've never had them before. I'm fairly certain 1.10 has corrupted something. My only question is can it be fixed or do I need to revert to a backup and abandon 1.10 until they bring out a patch to prevent this?
Ok, so it turns out it was corrupted entities. I noticed some lines on server start indicating it was "Keeping entity [x] that already existed". I'd never seen those lines on startup before. So I used the kill command and suddenly lag went away and server stopped crashing. Definitely appears to be a bug in 1.10.
We are getting this incessantly and even after killing them, they come back. I've stayed in the same spot, killed the same mob listed in the log 4 times and it still comes back. Have you seen the same behaviour, or did your problem completely go away?