Direct answer
If Minecraft runs as a systemd service, inspect its logs with sudo journalctl -u minecraft.service -n 100 --no-pager. Replace minecraft.service with the actual unit name.
Recommended procedure
- Find your unit name using
systemctl list-units --type=service(or read your service file). - Read recent output:
sudo journalctl -u minecraft.service -n 100 --no-pager. - Watch it live while reproducing a failure:
sudo journalctl -u minecraft.service -f. Press Ctrl+C to stop viewing. - Inspect recent boot events:
sudo journalctl -b -u minecraft.service. - Compare the first relevant exception or exit code with the game’s own
logs/latest.log, if that file exists.
Why this matters
journalctl shows logs collected by systemd, including startup failures that may occur before Minecraft creates latest.log. It does not automatically capture a Java process started directly in a terminal or an unrelated hosting panel.
How to verify the result
Restart or reproduce the problem only during a maintenance window. Confirm the journal contains messages for the correct service and timestamp. Avoid posting logs publicly if they contain tokens, usernames, paths or network details.
Version and compatibility notes
These commands apply to Linux systems running systemd, not Windows or every container. Log access may require elevated permissions.
Official references
Related guides
Help us improve this article
Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.