Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Server Monitoring

Track your Ragnarok server's health — uptime, crashes, errors and warnings

RagnaSync can keep an eye on your Ragnarok server for you. Once monitoring is running, RagnaSync knows which of your sub-servers are up, captures crashes, and collects the errors and warnings your server prints to its console — all visible from your dashboard, and (optionally) reflected on your public Status Page.

Think of it as a health monitor that's always watching, so you don't have to SSH in to find out something broke.

What it watches

Signal
What you get

Per-server status

The live state of each sub-server — Login, Char, Map and Web — reported as started, stopped, restarting, or crashed.

Crashes

Full crash reports (backtrace, threads, registers) whenever a server segfaults. See Crash Logs.

Console errors

Lines your server logs at error level, collected so you can spot problems over time.

Console warnings

Warning-level console output, tracked the same way.

Each sub-server reports independently, so you can tell at a glance whether it was the map-server that went down while login and char stayed up.

Turning it on

Monitoring is built into the RagnaSync launcher — the same ragnasync.sh (Linux) or ragnasync.bat (Windows) script you use for crash reporting. When you run your servers through the launcher instead of starting them directly, it watches each process and reports status, crashes, and console output back to RagnaSync automatically.

There's nothing extra to toggle. As soon as the launcher starts reporting, your dashboard lights up:

  1. Make sure your channels.conf has your ragnasync_client_guid (set during install — this is how RagnaSync knows the reports are yours).

  2. Start your servers through the launcher. See Crash Logs → Setup for the exact command on your platform.

  3. Open your dashboard — the Monitoring page appears under the Ragnarok section once the first reports arrive.

The launcher installs its own dependencies (like GDB and curl) the first time it runs, so you don't need to set anything up by hand.

The Monitoring dashboard

Under Ragnarok → Monitoring in your dashboard, you'll find a single view of everything the monitor has collected:

  • Crash, error and warning counts for the period you pick.

  • A trend chart showing when those happened, so a spike is easy to spot.

  • A period selector — Last Hour, Last 24 Hours, Last 7 / 14 / 30 Days.

This is the place to check after a rough night: did the map-server crash three times at 2am, or was it just a wave of warnings? The trend chart makes the pattern obvious.

The Monitoring menu item only shows up once there's something to show. If you don't see it yet, your servers haven't reported in — double-check they're running through the launcher.

On your public Status Page

The per-server status the monitor reports also powers the detail on your public Status Page:

  • With monitoring running — your status page breaks uptime down per sub-server: Login, Char, Map and Web, each shown on its own.

  • Without it — the page falls back to a single Server up/down indicator based on whether your server is connected to RagnaSync.

So installing the monitor doesn't just help you — it gives your players a more detailed picture of what's up and what's down.

Crash logs

Crash capture is the deepest part of monitoring and has its own page covering setup, what's in a report, and how to read it:

➡️ Crash Logs

Notes

  • Monitoring is read-only — it observes and reports, it never changes how your server runs.

  • Only you can see your server's monitoring data; it's scoped to your guild.

  • Normal shutdowns are reported as stopped, not crashed — a crash is specifically an abnormal exit (SIGSEGV, SIGABRT, etc.).

PreviousContainer Logs
NextConsole Logs

Last updated