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)
This commit is contained in:
Michele Baldessari 2020-09-29 23:44:03 +02:00
parent 04650a1681
commit 944518b8b9
1 changed files with 2 additions and 0 deletions

View File

@ -169,6 +169,8 @@ outputs:
passwords:
- {get_param: RabbitCookie}
- {get_param: [DefaultPasswords, rabbit_cookie]}
rabbitmq::config_additional_variables:
lager: '[{crash_log_count, 0}, { crash_log_date, ""}, { crash_log_size, 0 }]'
# NOTE: bind IP is found in hiera replacing the network name with the
# local node IP for the given network; replacement examples
# (eg. for internal_api):