How to Reliably Run a Minecraft Server on OCI Using Systemd for Auto-Restarts

-

 

In this guide, we will build on the previous tutorial for setting up a modded Minecraft server on Oracle Cloud Infrastructure (OCI). You will learn how to configure your Minecraft server to run as a systemd service, ensuring it starts automatically at boot and restarts in case of crashes.

Step 1: Verify Your Server Setup

Before proceeding, ensure that:

  1. You have completed the basic setup of a Minecraft server on OCI as outlined in the previous guide.
  2. The Minecraft server files are located in ~/minecraft and can be started with the command: 
    java -Xmx8G -Xms8G -jar forge-*.jar nogui
    Replace 8G with your desired RAM allocation.

Step 2: Create a Systemd Service File

  1. Open a terminal and switch to the root user:

    sudo su

  2. Navigate to the systemd configuration directory:

    cd /etc/systemd/system

  3. Create a new service file for your Minecraft server:

    nano minecraft.service

  4. Add the following configuration to the file:

    [Unit]
Description=Minecraft Server
After=network.target

[Service]
User=ubuntu
WorkingDirectory=/home/ubuntu/minecraft
ExecStart=/usr/bin/java -Xmx8G -Xms8G -jar forge-*.jar nogui
Restart=always
RestartSec=10
StandardOutput=append:/home/ubuntu/minecraft/server.log
StandardError=append:/home/ubuntu/minecraft/server.log

[Install]
WantedBy=multi-user.target
    • Replace ubuntu with the username of the user running the server.
    • Adjust the -Xmx and -Xms values to match your server's resources.

  5. Save and exit the file by pressing Ctrl+O, Enter, and Ctrl+X.

Step 3: Reload Systemd and Enable the Service

  1. Reload the systemd daemon to recognize the new service: 
    systemctl daemon-reload
  2. Enable the Minecraft service to start at boot: 
    systemctl enable minecraft.service
  3. Start the Minecraft service: 
    systemctl start minecraft.service
  4. Check the service status to ensure it is running: 
    systemctl status minecraft.service
    You should see output indicating that the service is active and running.

Step 4: Configure Firewall for Automatic Restarts

If you have not already configured the firewall for port 25565 (Minecraft’s default port), ensure the rule is set in your OCI Console:

  1. Go to Networking > Virtual Cloud Networks in the OCI Console.
  2. Select the VCN and then the Subnet.
  3. Under Security Lists, confirm that an ingress rule exists for:
    • Source CIDR: 0.0.0.0/0
    • Destination Port Range: 25565
    • Protocol: TCP

Step 5: Test the Service

  1. Stop the service to simulate a crash: 
    systemctl stop minecraft.service
  2. Wait for a few seconds and verify that the service restarts automatically: 
    systemctl status minecraft.service
  3. You can also check the log file for restart activity: 
    tail -f /home/ubuntu/minecraft/server.log

Step 6: Update and Manage Your Service

  • To Restart the Service Manually:

    systemctl restart minecraft.service

  • To Disable the Service from Starting at Boot:

    systemctl disable minecraft.service

  • To Edit the Service File:

    nano /etc/systemd/system/minecraft.service

    After editing, always reload the systemd daemon:

    systemctl daemon-reload

  • To View Logs:

    journalctl -u minecraft.service

Now your Minecraft server is configured to run as a systemd service. It will automatically start on boot, restart after crashes, and log its output to server.log for easy debugging.

Comments

Post a Comment

Popular posts from this blog

Mastering Prompt Engineering: How to Think Like an AI and Write Prompts That Never Fail

-
Image
Introduction: Why Prompt Engineering Is a Moving Target   Prompt engineering itself doesn’t evolve rapidly - but the models it depends on change all the time. Every new generation of large language models comes with new reasoning layers, expanded context windows, modified decoding defaults, and new forms of safety alignment. These shifts alter how models interpret, prioritize, and execute instructions. A prompt that produces clean, reliable output one week might start producing verbose or inconsistent results after a silent update. The role of a prompt engineer is therefore not just to write good prompts, but to detect, analyze, and adapt to these changes. Successful practitioners treat prompt design as an ongoing process of experimentation rather than a fixed discipline. Understanding the Core Ideas Behind Prompt Design At its core, prompt engineering is about communication - bridging human intent and machine interpretation. A good prompt does three things clearly: defines who th...
Read more

Is Docker Still Relevant in 2025? A Practical Guide to Modern Containerization

-
  Docker took the IT world by storm when it was first released in 2013, introducing a simple yet powerful way to create, deploy, and manage containerized applications. Fast forward to 2025, and the containerization landscape has grown exponentially, with tools like Kubernetes, Podman, and Buildah gaining traction. So, is Docker still relevant? Let’s dive in. Docker's Core Strengths Docker remains one of the most user-friendly and widely adopted containerization tools. Its key features include: Ease of Use : Docker’s CLI and Docker Compose make it simple for developers to build and run containerized applications. Rich Ecosystem : Docker Hub is still the go-to repository for prebuilt images. Cross-Platform Support : Seamless operation across various platforms ensures it remains a top choice for development. For small to medium-sized projects, Docker’s simplicity makes it invaluable. It's a great choice for development environments, prototyping, and quick deployments. The Competit...
Read more

Going In With Rust: The Interview Prep Guide for the Brave (or the Mad)

-
 Why Rust? (No, Seriously, Why?)      Choosing Rust as your language for a coding interview is, at best, bold — and at worst, borderline reckless. Rust is not known for being ergonomic under time pressure. Unlike Python or Java, it doesn’t hold your hand when you’re fumbling through edge cases and messy input. The compiler is famously strict, and while that’s great for production code, it can feel like an enemy in a 45-minute interview. Forget about “just trying something” — Rust will make you justify every move. Want to mutate a value inside a loop? Better understand borrowing rules. Need a linked list? Be ready to bring in Rc , RefCell , and a prayer. Want to pass a slice around without cloning everything? Ownership will make you earn it. Many LeetCode problems assume a fast, flexible language — Rust is neither of those, out of the box. There’s no REPL. You can’t “just print stuff” — not without fighting the borrow checker and formatting macros. Even simple operati...
Read more