This bug was initially created as a copy of Bug #1679878 I am copying this bug because: We need a dedicated BZ for openstack-tripleo-heat-templates package Description of problem: In recent RHOSP13, we execute rotation for the logs from applications running inside container in default. ~~~ /var/log/containers/*/*log /var/log/containers/*/*/*log /var/log/containers/*/*err { daily rotate 14 maxage 14 minsize 1 maxsize 10M missingok notifempty copytrunate delaycompress compress sharedscripts postrotate /usr/bin/find /var/log/containers -type f \ \( -mtime +14 -or \ -atime +14 -or \ -ctime +14 \) -exec rm -f {} \;; endscript } ~~~ According to the configuration, all logs which does not have any records for 14 days are purged. Mysql running inside container rarely generates logs, and this causes the problem that its log get purged but mysqld process keep opening the deleted file as it never gets SIGHUP from logrotate. How reproducible: - Deploy overcloud with default logrotate configuration Steps to Reproduce: 1. Deploy overcloud with small LogrotateRotatte and LogrotatePurgeAfterDays 2. Wait until the specified day pass 3. See the opened log file by the following command - $ sudo lsof -p `sudo pidof mysqld` 2>/dev/null | grep log Actual results: The process keep opening the deleted log file Expected results: The process should open the exsiting log file Additional info:
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0939