-
Bug
-
Resolution: Duplicate
-
None
-
Minecraft 1.8
-
None
-
Ubuntu 14.04 LTS, x64
AWS/EC2 m3.medium instance:
Intel(R) Xeon(R) CPU E5-2670 v2 @ 2.50GHz
3840MiB RAM
Java:
java version "1.8.0_20"
Java(TM) SE Runtime Environment (build 1.8.0_20-b26)
Java HotSpot(TM) 64-Bit Server VM (build 25.20-b23, mixed mode)
Java args:
java -server -Xms2G -Xmx2G -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+CMSIncrementalPacing -XX:ParallelGCThreads=2 -XX:+AggressiveOpts -jar minecraft_server.1.8.jar nogui
Also using:
java -Xms2G -Xmx2G -jar minecraft_server.1.8.jar noguiUbuntu 14.04 LTS, x64 AWS/EC2 m3.medium instance: Intel(R) Xeon(R) CPU E5-2670 v2 @ 2.50GHz 3840MiB RAM Java: java version "1.8.0_20" Java(TM) SE Runtime Environment (build 1.8.0_20-b26) Java HotSpot(TM) 64-Bit Server VM (build 25.20-b23, mixed mode) Java args: java -server -Xms2G -Xmx2G -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+CMSIncrementalPacing -XX:ParallelGCThreads=2 -XX:+AggressiveOpts -jar minecraft_server.1.8.jar nogui Also using: java -Xms2G -Xmx2G -jar minecraft_server.1.8.jar nogui
-
Unconfirmed
(same things happen regardless of java args used to start server)
Server only hosts ~5-10 players.
Players suffering consistently from the following:
- All players simultaneously being kicked approx. every 30 minutes. This kick is generally preceded by familiar symptoms such as blocks not dropping when struck, players being duplicated, and rubberbanding.
Example from log:
[Server thread/INFO]: player lost connection: TranslatableComponent{key='disconnect.genericReason', args=[Internal Exception: java.io.IOException: Connection reset by peer], siblings=[], style=Style{hasParent=false, color=null, bold=null, italic=null, underlined=null, obfuscated=null, clickEvent=null, hoverEvent=null, insertion=null}}
OR
[Server thread/INFO]: player lost connection: TextComponent{text='Disconnected', siblings=[], style=StyleUnknown macro: {hasParent=false, color=null, bold=null, italic=null, underlined=null, obfuscated=null, clickEvent=null, hoverEvent=null, insertion=null}}
- Excessive game (seemingly not video or network) latency making movement on foot/horse extremely slow. Horse will move orders of magnitude slower for instance. This corresponds to the familiar log message:
Can't keep up! Did the system time change, or is the server overloaded? Running 2605ms behind, skipping 52 tick(s) - note the order of ms behind, this is typically the range. When debug is turned on, the attached files show the various types of tick related issues happening on the server.
- Server grinding to halt due to above issue, once the server reports approx. 5-10 times that it cannot "Keep up", the delay becomes too great and the server is unplayable.