daemon.log rotating too quickly due to containerd logs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Suvro Ghosh |
Bug Description
Brief Description
-----------------
The /var/log/daemon.log file (on controller hosts) is rotating out after approximately 2 days when an application (e.g. stx-openstack or stx-monitor) is installed. In order to debug user issues, we should aim for about 2 weeks of log retention.
More than 85% of the logs are coming from containerd. It looks like they are due to liveness checks - for example:
2020-06-
2020-06-
2020-06-
2020-06-
2020-06-
Severity
--------
Major: debugging issues is difficult as the daemon.log file may have rotated out before the problem is detected and/or the logs are collected
Steps to Reproduce
------------------
Install the system and create some additional pods (e.g. by installing one of the starlingx applications mentioned above)
Expected Behavior
------------------
The daemon.log files keep about 2 weeks of logs.
Actual Behavior
----------------
The daemon.log is being rotated out after about 2 days.
Reproducibility
---------------
Reproducible
System Configuration
-------
Any
Branch/Pull Time/Commit
-------
Designer load from starlingx master: BUILD_DATE=
Last Pass
---------
Unknown
Timestamp/Logs
--------------
See logs above
Test Activity
-------------
Developer Testing
Workaround
----------
None
tags: | added: stx.containers |
Marking for stx.5.0 as it's not clear how we can address this in starlingx. This may require follow up with the containerd community