-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Logrotate example
Pieter edited this page Dec 17, 2020
·
3 revisions
Over time, the Bitwarden_RS log file can grow to a significant size. Using logrotate, we can periodically rotate logs.
sudo nano /etc/logrotate.d/bitwarden
/var/log/bitwarden/*.log {
# Perform logrotation as the bitwarden user and group
su bitwarden bitwarden
# Rotate daily
daily
# Rotate when the size is bigger than 5MB
size 5M
# Compress old log files
compress
# Keep 4 rotations of log files before removing or mailing to the address specified in a mail directive
rotate 4
# Truncate the original log file in place after creating a copy
copytruncate
# Don't panic if not found
missingok
# Don't rotate log if file is empty
notifempty
# Add date instaed of number to rotated log file
dateext
# Date format of dateext
dateformat -%Y-%m-%d-%s
}
To view a compressed log file without manually decompressing:
zcat logfile.gz
zless logfile.gz
zgrep -i keyword_search logfile.gz
- Which container image to use
- Starting a container
- Updating the vaultwarden image
- Using Docker Compose
- Using Podman
- Building your own docker image
- Building binary
- Pre-built binaries
- Third-party packages
- Deployment examples
- Proxy examples
- Logrotate example
- Overview
- Disable registration of new users
- Disable invitations
- Enabling admin page
- Disable the admin token
- Enabling WebSocket notifications
- Enabling Mobile Client push notification
- Enabling U2F and FIDO2 WebAuthn authentication
- Enabling YubiKey OTP authentication
- Changing persistent data location
- Changing the API request size limit
- Changing the number of workers
- SMTP configuration
- Translating the email templates
- Password hint display
- Disabling or overriding the Vault interface hosting
- Logging
- Creating a systemd service
- Syncing users from LDAP
- Using an alternate base dir (subdir/subpath)
- Other configuration