Log Files

Table of contents

• Log file paths
• Java fatal logs

Use log files to troubleshoot errors, unexpected behavior, or startup failures in dbvr.

To see runtime logs, run dbvr with the --debug-logs option. All logs are printed directly to the console.

For post-analysis, use the log files stored in the workspace directory.

Log file paths

dbvr writes log files to the workspace directory. Logs are stored in:

<workspace>/.metadata

Tip:For details on how to locate your workspace, see workspace location.

• on Windows, open Explorer and enter the path %APPDATA%\DBeaverData\workspace6\.metadata.
• on Linux, execute cd $XDG_DATA_HOME/DBeaverData/workspace6/.metadata.
• on MacOS, navigate to ~/Library/DBeaverData/workspace6/.metadata in Finder. To view hidden folders, press Cmd+Shift+..

Two standard log files:

• <workspace>/.metadata/.log - contains all warnings and errors occurring during normal operation.
• <workspace>/.metadata/dbeaver-debug.log - includes the same information as .log plus additional debug details.

Note: The dbeaver-debug.log file has a maximum size limit of 10 MB. If the file size exceeds this limit, a new log file is created.

Java fatal logs

If dbvr terminates unexpectedly, the cause is usually a JVM crash.

In this case, the JVM creates a fatal error log file named hs_err_pid*.log. The file is typically written to the same directory as the dbvr launcher. If that directory is write-protected, the log may be created in a different location.

For information on how to locate this file, see the official documentation.