Server Not Starting (Log File Empty)

[Zortrox]

I can't seem to get a server to start using the msm <server> start command; it just outputs

Maintaining world symbolic links... Done.
Synchronising flagged worlds on disk to RAM... Done.
Starting server... Done

Although the final done happens 30 seconds later with the server not actually starting.

I have read through multiple issues, including this one, but nothing seems to be working to fix this. I checked the log files, but there aren't any errors written to it. Using other msm commands doesn't show any errors either (e.g. updating jargroups, listing servers, etc.) I have reinstalled MSM and restarted my server too, but that didn't work either.

I can start the server with no issues using the java -jar server.jar in the Minecraft server directory (inside msm), so it's not a memory, server configuration, or EULA issue.

Server Specs:
Ubuntu 18.04.1
8 GB of RAM
OpenJDK version 10.0.2
Minecraft Server Manager 0.9.10 Beta
Minecraft version 1.13.2

"msm config" output:

DEBUG="false"
USERNAME="minecraft"
SERVER_STORAGE_PATH="/opt/msm/servers"
JAR_STORAGE_PATH="/opt/msm/jars"
VERSIONING_STORAGE_PATH="/opt/msm/versioning"
VERSIONING_FILE_EXTENSION="sh"
RAMDISK_STORAGE_ENABLED="true"
RAMDISK_STORAGE_PATH="/dev/shm/msm"
WORLD_ARCHIVE_ENABLED="true"
WORLD_RDIFF_PATH="/opt/msm/rdiff-backup/worlds"
RDIFF_BACKUP_ENABLED="false"
RDIFF_BACKUP_NICE="19"
RDIFF_BACKUP_ROTATION="7"
UPDATE_URL="https://raw.githubusercontent.com/msmhq/msm/master"
WORLD_ARCHIVE_PATH="/opt/msm/archives/worlds"
LOG_ARCHIVE_PATH="/opt/msm/archives/logs"
BACKUP_ARCHIVE_PATH="/opt/msm/archives/backups"
RSYNC_BACKUP_ENABLED="false"
WORLD_RSYNC_PATH="/opt/msm/rsync/worlds"
JARGROUP_TARGET="target.txt"
JARGROUP_DOWNLOAD_DIR="downloads"
SERVER_PROPERTIES="server.properties"
DEFAULT_USERNAME="minecraft"
DEFAULT_SCREEN_NAME="msm-{SERVER_NAME}"
DEFAULT_VERSION="unknown"
DEFAULT_WORLD_STORAGE_PATH="worldstorage"
DEFAULT_WORLD_STORAGE_INACTIVE_PATH="worldstorage_inactive"
DEFAULT_LOG_PATH="logs/latest.log"
DEFAULT_WHITELIST_PATH="white-list.txt"
DEFAULT_BANNED_PLAYERS_PATH="banned-players.txt"
DEFAULT_BANNED_IPS_PATH="banned-ips.txt"
DEFAULT_OPS_PATH="ops.txt"
DEFAULT_OPS_LIST=""
DEFAULT_JAR_PATH="server.jar"
DEFAULT_FLAG_ACTIVE_PATH="active"
DEFAULT_COMPLETE_BACKUP_FOLLOW_SYMLINKS="false"
DEFAULT_WORLDS_FLAG_INRAM="inram"
DEFAULT_RAM="1024"
DEFAULT_INVOCATION="java -Xms{RAM}M -Xmx{RAM}M -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalPacing -XX:+AggressiveOpts -jar {JAR} nogui"
DEFAULT_STOP_DELAY="10"
DEFAULT_RESTART_DELAY="10"
DEFAULT_MESSAGE_STOP="SERVER SHUTTING DOWN IN {DELAY} SECONDS!"
DEFAULT_MESSAGE_STOP_ABORT="Server shut down aborted."
DEFAULT_MESSAGE_RESTART="SERVER REBOOT IN {DELAY} SECONDS!"
DEFAULT_MESSAGE_RESTART_ABORT="Server reboot aborted."
DEFAULT_MESSAGE_WORLD_BACKUP_STARTED="Backing up world."
DEFAULT_MESSAGE_WORLD_BACKUP_FINISHED="Backup complete."
DEFAULT_MESSAGE_COMPLETE_BACKUP_STARTED="Backing up entire server."
DEFAULT_MESSAGE_COMPLETE_BACKUP_FINISHED="Backup complete."
DEFAULT_CONFIRM_SAVE_ON=""
DEFAULT_CONFIRM_SAVE_OFF=""
DEFAULT_CONFIRM_SAVE_ALL=""
DEFAULT_CONFIRM_START=""
DEFAULT_CONFIRM_KICK=""
DEFAULT_CONFIRM_TIME_SET=""
DEFAULT_CONFIRM_TIME_ADD=""
DEFAULT_CONFIRM_TOGGLEDOWNFALL=""
DEFAULT_CONFIRM_GAMEMODE=""
DEFAULT_CONFIRM_GIVE=""
DEFAULT_CONFIRM_XP=""

[nickovs]

I had the same issue when I moved to my new Ubuntu 18.04 server. The issue appears to be that OpenJDK 10 no longer supports the -XX:+CMSIncrementalPacing command line option. I patched the issue on my machine by editing the /etc/msm.conf file to change the line that used to say:

DEFAULT_INVOCATION="java -Xms{RAM}M -Xmx{RAM}M -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalPacing -XX:+AggressiveOpts -jar {JAR} nogui"

to just say:

DEFAULT_INVOCATION="java -Xms{RAM}M -Xmx{RAM}M -XX:+AggressiveOpts -jar {JAR} nogui"

and that solved the problem for me.

Note that I took out the UseConcMarkSweepGC option as well because this is now deprecated and when you include it you get a warning saying that it may disappear in the future.

Anyway, it seems like to proper fix for this is for the built-in default setting for the invocation to be updated to work with the latest JDK.

[Zortrox]

Thank you; that solved the issue on my end! I'll mark this as closed since we don't need two issues about Incremental Pacing.