Description of problem: Missing /var/log/btmp in rabbitmq container causes unnecessary logs in /var/log/secure. ~~~ su:pam_lastlog(su:session): unable to open /var/log/btmp: No such file or directory ~~~ The message is written in every su option for rabbitmq user. It makes /var/log/secure larger and hard to read useful logs. Version-Release number of selected component (if applicable): Current openstack-triple-heat-templates. How reproducible: Always. Steps to Reproduce: 1. Deploy RHOSP13 2. Login controller nodes. 3. Check /var/log/secure Actual results: The following log is written to /var/log/secure in every su for rabbitmq. ~~~ su:pam_lastlog(su:session): unable to open /var/log/btmp: No such file or directory ~~~ Expected results: The log should not be written. Additional info: A simple solution for this is touch /var/log/btmp file in the container or create an empty file on the host directory, /var/log/pacemaker/bundles/rabbitmq-bundle-0
Merged upstream on queens
Hello Hervé, Thank you for your work on this bugzilla. Could you proceed the backport into RHOSP13 tree? If we can fix it at RHOSP13z4, many of our customer will be happy. Best Regards, Keigo Noha
Hello Keigo, Sure. Best Regards, Hervé Beraud
[heat-admin@controller-0 ~]$ sudo docker exec -it rabbitmq-bundle-docker-0 /bin/bash ()[root@controller-0 /]# ls /var/log/btmp /var/log/btmp
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:0068