mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2025-12-11 09:13:02 +03:00
vaultwarden silently fails if LOG_FILE is defined but has no permission to write there #960
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dionysius on GitHub.
Subject of the issue
I was running vaultwarden manually, env variables preloaded and failed silently with exit code 1. env variable
LOG_FILEwas set to a correct path, but that path had not yet the correct permission. After setting the correct permission and starting vaultwarden again, the log file existed and a new error message could be read. I can't say which part is the cause of the silent exit - either way vaultwarden should probably write an error message to stderr.Deployment environment
Install method: source (debian packaging I just created and made publicly available: https://github.com/dionysius/vaultwarden-deb but its not relevant to understand this issue)
Clients used: none
Reverse proxy and version: none
MySQL/MariaDB or PostgreSQL version: sqlite3
Other relevant details: LOG_FILE has been removed as journalctl output is sufficient so I'm not affected anymore, but this is still a bug
Steps to reproduce
sudo -HEu vaultwarden vaultwarden--Eovertakes env that has been preloaded before)Expected behaviour
An error to stderr indicating the problem of the exit
Actual behaviour
No output
Troubleshooting data
Before fixing permissions
After fixing permissions: