You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I open this ticket to keep in mind tracking the following issue : #604 (comment)
To sum-up, using globalSettings__logRollBySizeLimit=1073741824, filename is OK, log.txt.
But it is "wrongly" rotated. log.txt goes up to the limit, then new log lines go into log_001.txt.
We would rather expect moving log.txt to log_001.txt, and logging again into log.txt.
A possible workaround is to let globalSettings__logRollBySizeLimit= empty, so that we're back with the daily-rotated log file (but still without a fixed name, see upstream issue above).
And to create a fixed log.txt by ourselves :
# create the new daily log file
docker restart bitwarden-identity
# link the fixed name
ln -f /path/to/bwdata/logs/identity/Identity/$(date +%Y%m%d).txt /path/to/bwdata/logs/identity/Identity/log.txt
Can be easily scheduled (using cron for example) everyday at 00:00 👍
Hi @Mart124,
We're cleaning up our repositories in preparation for a major reorganization. Issues from last year will be marked as stale and closed after two weeks. If you still need help, comment to let us know and we'll look into it.
Thanks!
Hi,
I open this ticket to keep in mind tracking the following issue :
#604 (comment)
To sum-up, using
globalSettings__logRollBySizeLimit=1073741824
, filename is OK,log.txt
.But it is "wrongly" rotated.
log.txt
goes up to the limit, then new log lines go intolog_001.txt
.We would rather expect moving
log.txt
tolog_001.txt
, and logging again intolog.txt
.Seems like an issue with Serilog itself : serilog/serilog-sinks-file#40
Thx 👍
The text was updated successfully, but these errors were encountered: