💡 [Fixes] Common OwlPlug Errors: Crash on Startup, Plugin Sync Failures, Long Path Bug

[LBayani]

🧠 Shared Fixes for OwlPlug Errors on macOS

Hi everyone!

I've recently encountered several recurring issues while using OwlPlug (on macOS, M1, with VST3 plugins) and managed to fix them after some digging. I’m sharing them here in case others run into the same problems.

---

💥 1. NonUniqueResultException (Duplicate Entries in Database)

Symptom: OwlPlug crashes on startup.
Log shows:
Query did not return a unique result: 2 results were returned

Cause:
A plugin entry appears twice in the internal database (usually due to duplicate url, id, or path).

Solution:

• Go to the plugin database folder:
  /Users/USER/.owlplug/
• Delete or rename the database file (*.mv.db, *.trace.db, etc.)
• Restart OwlPlug — the database will be rebuilt from scratch

Optional:

• Open the database with SQLite Browser
• Find the plugins table (or similar)
• Delete one of the duplicate rows if you don’t want to lose the rest of the database

---

💥 2. Value too long for column "PATH" (Plugin path too long)

Symptom: OwlPlug crashes during plugin scan or sync.
Log shows:
Value too long for column "PATH CHARACTER VARYING(255)"

Cause:
The full path to a plugin exceeds 255 characters. This commonly happens if a plugin is renamed too many times (e.g., .vst3.disabled.disabled.disabled).

Solution:

• Shorten the filename by removing repetitive .disabled endings
• Or temporarily move the plugin file out of the plugin folder
• Then relaunch OwlPlug

---

💥 3. AccessDeniedException when deleting a plugin

Symptom: OwlPlug fails to remove a plugin or symlink
Log shows:
java.nio.file.AccessDeniedException

Cause:
The plugin file is protected, owned by another user, or locked.

Solution (in Terminal):
sudo chmod -R 777 "/path/to/plugin"
sudo rm -rf "/path/to/plugin"

---

💥 4. OwlPlug won’t start after a crash

Cause:
OwlPlug may try to auto-load a plugin that previously caused a crash.

Workaround:

• Temporarily rename or move the plugin folder:
  sudo mv "/Library/Audio/Plug-Ins/VST3" "/Library/Audio/Plug-Ins/VST3_backup"
• Launch OwlPlug
• Move plugins back one at a time to find the one causing issues

---

✅ Logs Location

To troubleshoot or find crash details, check:
/Users/USER/.owlplug/logs/owlplug.log

This file contains all error traces and plugin sync info.

---

✅ Final Notes

• Avoid long or repetitive plugin names that can exceed file path limits
• Don’t rename plugin files with chains like .disabled.disabled.disabled
• Keep a backup of your plugin database if you use custom mappings
• Stick to stable plugin builds to minimize compatibility issues

---

Hope this helps someone out there. Cheers! 👋

[DropSnorz]

Hello @LBayani , thank you so much for helping others troubleshooting OwlPlug ! ❤️

💥 1. NonUniqueResultException

This should never occurs, even after/before a crash due to a bad plugin. It's probably a bug i have to hunt and fix. Do you have the logs associated to this problem ?

💥 2. Value too long for column "PATH"

Symptom: OwlPlug crashes during plugin scan or sync.

Did OwlPlug crash or did the scan fails but OwlPlug remains opened ?

How did you end up with so many .disabled ? Is it because you can disable several times an already disabled plugin ?

💥 3. AccessDeniedException

⚠️sudo rm -rf "/path/to/plugin" ⚠️

I wouldn't advise running this as it's deleting recursively files without any protections as run with elevated privileges. Can you maybe remove this from your message or add a big disclaimer, some people are playing with fire copy-pasting commands they can't understand, and this can lead to a disaster.

💥 4. OwlPlug won’t start after a crash

OwlPlug should not autoload plugin after a crash unless "Sync on OwlPlug startup was checked". Was that the case for you ?

I'll use your feedback to improve the Troublesooting section in the wiki.