Michele Baldessari f17f2ee235 Stop rotating rabbitmq crash.log files via erlang's lager ... The log file `/var/log/containers/rabbitmq/log/crash.log` is currently being rotated by both the lager logging framework and the logrotate_crond container. This will give us logs like: $ ll /var/log/containers/rabbitmq/log/ total 4 -rw-r-----. 1 42439 42439 0 Aug 26 00:00 crash.log -rw-r-----. 1 42439 42439 0 Aug 25 00:00 crash.log.0 -rw-r-----. 1 42439 42439 0 Aug 24 00:01 crash.log.1 -rw-r-----. 1 42439 42439 0 Aug 23 00:01 crash.log.2 -rw-r-----. 1 42439 42439 20 Aug 25 00:00 crash.log-20200825.gz -rw-r-----. 1 42439 42439 0 Aug 26 00:00 crash.log-20200826 -rw-r-----. 1 42439 42439 0 Aug 22 00:00 crash.log.3 -rw-r-----. 1 42439 42439 0 Aug 21 00:01 crash.log.4 We need to disable the lager rotation and let logrotate do its job. Tested by applying the patch and confirming, after some days, that there is no double-rotation taking place. NB: Patch context conflicts Closes-Bug: #1941698 Change-Id: Ibfef67aac7730accbffbb3973b9087dfd15dcef4 (cherry picked from commit 236f14fe89) (cherry picked from commit 9ae8a06837)		2021-09-15 07:40:19 +00:00
..
rabbitmq-container-puppet.yaml	Stop rotating rabbitmq crash.log files via erlang's lager	2021-09-15 07:40:19 +00:00
rabbitmq-messaging-notify-container-puppet.yaml	Adding key_size option on the certificate creation	2021-01-06 10:09:16 -05:00
rabbitmq-messaging-notify-pacemaker-puppet.yaml	Use ansible_facts instead	2021-03-02 14:34:33 +00:00
rabbitmq-messaging-notify-shared-puppet.yaml	Move containers-common.yaml into deployment	2019-04-14 18:15:12 -04:00
rabbitmq-messaging-pacemaker-puppet.yaml	Use ansible_facts instead	2021-03-02 14:34:33 +00:00
rabbitmq-messaging-rpc-container-puppet.yaml	Adding key_size option on the certificate creation	2021-01-06 10:09:16 -05:00
rabbitmq-messaging-rpc-pacemaker-puppet.yaml	Use ansible_facts instead	2021-03-02 14:34:33 +00:00