rabbitmq's crash.log gets rotated twice

Bug #1941698 reported by Michele Baldessari
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
Medium
Michele Baldessari

Bug Description

The log file `/var/log/containers/rabbitmq/log/crash.log` is 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.

Changed in tripleo:
status: Triaged → In Progress
Revision history for this message
Michele Baldessari (michele) wrote :
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-heat-templates (master)

Reviewed: https://review.opendev.org/c/openstack/tripleo-heat-templates/+/755134
Committed: https://opendev.org/openstack/tripleo-heat-templates/commit/236f14fe89b1699fab4f3b8dd1e222a0a670d3da
Submitter: "Zuul (22348)"
Branch: master

commit 236f14fe89b1699fab4f3b8dd1e222a0a670d3da
Author: Michele Baldessari <email address hidden>
Date: Tue Sep 29 23:44:03 2020 +0200

    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.

    Closes-Bug: #1941698

    Change-Id: Ibfef67aac7730accbffbb3973b9087dfd15dcef4

Changed in tripleo:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-heat-templates (stable/wallaby)

Fix proposed to branch: stable/wallaby
Review: https://review.opendev.org/c/openstack/tripleo-heat-templates/+/806216

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-heat-templates (stable/wallaby)

Reviewed: https://review.opendev.org/c/openstack/tripleo-heat-templates/+/806216
Committed: https://opendev.org/openstack/tripleo-heat-templates/commit/d56266bc75b3f60581a1d042f52bbc5ce5baefc1
Submitter: "Zuul (22348)"
Branch: stable/wallaby

commit d56266bc75b3f60581a1d042f52bbc5ce5baefc1
Author: Michele Baldessari <email address hidden>
Date: Tue Sep 29 23:44:03 2020 +0200

    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.

    Closes-Bug: #1941698

    Change-Id: Ibfef67aac7730accbffbb3973b9087dfd15dcef4
    (cherry picked from commit 236f14fe89b1699fab4f3b8dd1e222a0a670d3da)

tags: added: in-stable-wallaby
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-heat-templates (stable/victoria)

Fix proposed to branch: stable/victoria
Review: https://review.opendev.org/c/openstack/tripleo-heat-templates/+/806638

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-heat-templates (stable/victoria)

Reviewed: https://review.opendev.org/c/openstack/tripleo-heat-templates/+/806638
Committed: https://opendev.org/openstack/tripleo-heat-templates/commit/9ae8a06837c5459dae768ee0eafc66135b266ad1
Submitter: "Zuul (22348)"
Branch: stable/victoria

commit 9ae8a06837c5459dae768ee0eafc66135b266ad1
Author: Michele Baldessari <email address hidden>
Date: Tue Sep 29 23:44:03 2020 +0200

    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 236f14fe89b1699fab4f3b8dd1e222a0a670d3da)

tags: added: in-stable-victoria
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-heat-templates (stable/ussuri)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-heat-templates (stable/train)

Reviewed: https://review.opendev.org/c/openstack/tripleo-heat-templates/+/785941
Committed: https://opendev.org/openstack/tripleo-heat-templates/commit/944518b8b96d3c25fd145cc13569f78aae2c7351
Submitter: "Zuul (22348)"
Branch: stable/train

commit 944518b8b96d3c25fd145cc13569f78aae2c7351
Author: Michele Baldessari <email address hidden>
Date: Tue Sep 29 23:44:03 2020 +0200

    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 236f14fe89b1699fab4f3b8dd1e222a0a670d3da)
    (cherry picked from commit 9ae8a06837c5459dae768ee0eafc66135b266ad1)

tags: added: in-stable-train
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-heat-templates (stable/ussuri)

Reviewed: https://review.opendev.org/c/openstack/tripleo-heat-templates/+/806705
Committed: https://opendev.org/openstack/tripleo-heat-templates/commit/f17f2ee2351f10292531c0cf2362dbd0d003f09f
Submitter: "Zuul (22348)"
Branch: stable/ussuri

commit f17f2ee2351f10292531c0cf2362dbd0d003f09f
Author: Michele Baldessari <email address hidden>
Date: Tue Sep 29 23:44:03 2020 +0200

    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 236f14fe89b1699fab4f3b8dd1e222a0a670d3da)
    (cherry picked from commit 9ae8a06837c5459dae768ee0eafc66135b266ad1)

tags: added: in-stable-ussuri
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-heat-templates 15.1.0

This issue was fixed in the openstack/tripleo-heat-templates 15.1.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-heat-templates 12.4.6

This issue was fixed in the openstack/tripleo-heat-templates 12.4.6 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-heat-templates 13.6.0

This issue was fixed in the openstack/tripleo-heat-templates 13.6.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-heat-templates train-eol

This issue was fixed in the openstack/tripleo-heat-templates train-eol release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.