mirror of https://github.com/lidarr/Lidarr
Updated Log Files (markdown)
parent
2e84563bdb
commit
ca39b26ed5
|
@ -13,6 +13,8 @@ If you're unable to access the Lidarr UI to set the logging level you can do so
|
|||
You can clear log files and the logs database directly from the UI, under System -> Logs -> Files and System -> Logs respectively.
|
||||
|
||||
### Multiple Log Files ###
|
||||
Lidarr uses rolling log files, each one limited to 1MB in size. The current log file is always `lidarr.txt`, for the the other files `lidarr.0.txt` is the next newest (the higher the number the older it is) up to 6 log files total. This log file contains fatal,error,warn and info entries.
|
||||
When Debug log level is enabled, additional `lidarr.debug.txt` rolling log files will be present, up to 51 files. This log files contains fatal,error,warn,info and debug entries. It usually covers a 40h period.
|
||||
Lidarr uses rolling log files, each one limited to 1MB in size. The current log file is always `lidarr.txt`, for the the other files `lidarr.0.txt` is the next newest (the higher the number the older it is) up to 6 log files total. This log file contains fatal,error,warn and info entries.
|
||||
|
||||
When Debug log level is enabled, additional `lidarr.debug.txt` rolling log files will be present, up to 51 files. This log files contains fatal,error,warn,info and debug entries. It usually covers a 40h period.
|
||||
|
||||
When Trace log level is enabled, additional `lidarr.trace.txt` rolling log files will be present, up to 51 files. This log files contains fatal,error,warn,info,debug and trace entries. Due to trace verbosity it only covers a couple of hours.
|
Loading…
Reference in New Issue