Troubleshooting

Common operations

Access application logs

Log are stored on the OwlPlug workspace in user home directory.

Windows

C:/Users/{you}/.owlplug/logs

MacOs

/home/{you}/.owlplug/logs

Increase log level

1. Browse to OwlPlug workspace directory

Windows

C:/Users/{you}/.owlplug

MacOs

/Users/{you}/.owlplug

2. Create a new file logging.properties in the workspace directory, and add the following line to set OwlPlug log level to DEBUG.

# logging.properties
com.owlplug=DEBUG

Available log levels are TRACE, DEBUG, INFO, WARN, ERROR, FATAL, OFF, ALL. The default log level is INFO for com.owlplug logger.

Common errors

Error message on startup: OwlPlug is already running

OwlPlug is probably stuck and invisible. Try to manually kill the process from command line or Task manager.

If any OwlPlug process are running, check logs to identify the conflict.

Error message on startup: Failed to launch JVM

Antivirus may disrupt application startup and execution. Owlplug may also require to be run as Administrator on Windows depending local security policies.

Crash during a plugin Scan / Sync

When Native Discovery is enabled in Options, plugins are deeply scanned to retrieve metadata. If something bad happen during metadata discovery, the entire application will crash. This is a known issue in OwlPlug (and some DAWs when you try to load a corrupted plugin)

To retrieve which plugin is responsible of the crash, you can change OwlPlug log level to DEBUG and look for the last scanned plugin in logs.

You can also try to run OwlPlug from a terminal to catch logs produced on STDOUT by native components and plugins.

Windows

OwlPlug.exe | MORE