Troubleshooting

Troubleshooting

Diagnose startup, logging and rollback problems.

The plugin does not start

Symptom	Cause and solution
Could not open the duckdb database	Driver not loaded or file locked. Paper needs internet on first start to download the drivers. The file must not be used by a second server instance.
Unknown database.type	Typo in database.type. Allowed: duckdb, sqlite, mysql, clickhouse.
MySQL: Access denied	Check user, password and rights. The database must exist.
ClickHouse: connection error	Check the HTTP port (default 8123) and the ssl setting.
Wrong Java version	Minecraft 26.3 and this plugin need Java 25.

Nothing is being logged

1. Run /up status. If it shows Paused, enable logging again with /up consumer.
2. Check the matching log.* option in config.yml and in the world file (<world>.yml).
3. Check blacklist.txt for the user, block or command.
4. During a migration entries are queued and written afterwards.

Lookup returns nothing

• Check the spelling of the name in u: (case does not matter).
• The time span may be too small. Try t:7d.
• Lookup defaults to #global. Limit it with r: if you get too much.
• Use valid actions, see Actions.

Rollback changes nothing

• t: is required. The default radius is 10 blocks.
• The entries may already be rolled back (struck through in a lookup).
• Use #preview to see what would happen.
• Only these actions can be rolled back: block, container, inventory, kill, spawn.
• Mobs can only be revived when their data was saved at the time of the kill.

The database is too large

• Set auto-purge-days in config.yml.
• Delete selectively: /up purge t:30d a:kill.
• /up purge #optimize compacts the file.
• Disable log.chat, log.pickup or log.commands if you do not need them.

Migration fails

• The command only works in the console.
• On failure the old database stays active. Check the console message and the credentials of the target database.
• Use --full-validation to verify the data row by row after copying.

Reporting a problem

Please include: server software and version, plugin version (/up status), the database engine and the relevant console excerpt.

#command rollback finds nothing

• Only commands run by players are tracked, after this feature was added.
• Check log.command-blocks in config.yml and in the world file.
• Commands that change more than 262,144 blocks, or use execute with relative coordinates, at, positioned, in or align, are not tracked.
• Without r: the whole server is searched. With u: only that player's commands are used.

Output is wrapped or cut off

Lower chat.width-px in config.yml (default 300) and run /up reload.

Too many or too few alerts

Adjust detection.* in config.yml, see Configuration. Each player can turn alerts off with /up alerts.

A rollback was interrupted

It resumes automatically after the next start. Look for [Recovery] in the console. Recovery is not available with ClickHouse.

CoreProtect import problems

Message	Cause and solution
can only be started from the console	Run /up import-coreprotect in the console
CoreProtect database not found	Check the file path
already contains imported CoreProtect data	The data was imported before. --force imports again and creates duplicates
Invalid table prefix	--prefix= may only contain letters, digits and _

---

Related pages: FAQ · Databases · Configuration