Skip to content
Vonix Network Wiki

Vonix Server Utilities — Troubleshooting & Diagnostics

Release Line: 2.0.2 Diagnostic IndexStandalone Line

This runbook covers operational health checks, SQLite concurrency tuning, and loader-specific lifecycle behaviors in VSU 2.0.2.

1. Quick Verification Command

Section titled “1. Quick Verification Command”

To verify that VSU has initialized properly and bound to its database:

/vonixsu version

Expected output:

  • Version: 2.0.2
  • Active Loader: Fabric, Forge, or NeoForge
  • Database Status: Connected (WAL mode)

2. Common Issues & Solutions

Section titled “2. Common Issues & Solutions”

Issue: “Players cannot use /home or /tpa after installing LuckPerms”

Section titled “Issue: “Players cannot use /home or /tpa after installing LuckPerms””
  • Context: In historical v1.6.0 releases, installing LuckPerms without configuring default group permissions locked non-opped players out of all commands.
  • Resolution in 2.0.2: VSU enforces Union Semantics (HasLuckPermsNode OR OpLevel >= opFallback). Non-op players automatically retain access to basic commands (opFallback = 0). If players are locked out, ensure you are running 2.0.2 or verify that negative permission nodes (vsu.command.* = false) have not been assigned in LuckPerms.

Issue: “Database locked error in logs during world save”

Section titled “Issue: “Database locked error in logs during world save””
  • Cause: SQLite file contention. Occurs if the server directory is placed on an NFS or SMB network share that does not support POSIX advisory locks properly, or if an external backup tool is reading data.db without using SQLite backup primitives.
  • Resolution:
    1. Ensure the server’s working directory resides on a local SSD/NVMe drive.
    2. Confirm WAL mode is active (data.db-wal and data.db-shm should appear next to data.db).
    3. When backing up data.db, copy the file during low-traffic windows or use the .backup command in sqlite3.

Issue: “/back or /backdeath does not record location on Forge servers”

Section titled “Issue: “/back or /backdeath does not record location on Forge servers””
  • Context: In older Forge ports, death events did not always bridge into the common Architectury handlers.
  • Resolution: VSU 2.0.1+ delivers command, player tick, and death events through native Forge event subscribers on 1.18.2, 1.19.2, and 1.20.1. Ensure you have not installed an outdated v1.5 or v1.6 jar.

Issue: “/accsee reports ‘No accessory provider available’”

Section titled “Issue: “/accsee reports ‘No accessory provider available’””
  • Cause: /accsee is a bridge command. It requires Curios API (on Forge and NeoForge) or Trinkets API (on Fabric) to be installed on the server.
  • Resolution: This is expected behavior when playing without accessory mods. If your modpack uses Curios or Trinkets, verify that the mod jar is present and active.

Issue: “Crash on startup: UnsupportedClassVersionError (class file version 69.0)”

Section titled “Issue: “Crash on startup: UnsupportedClassVersionError (class file version 69.0)””
  • Cause: Running Minecraft 26.1.2 on an older Java version (e.g. Java 17 or 21).
  • Resolution: The NeoForge 26.1.2 target requires Java 25. Update your server startup script to point to a JDK 25 installation.