+++ This bug was initially created as a clone of Bug #1210906 +++ Description of problem: We frequently get SOS reports where we'd like to see the status of mariadb-galera running under pacemaker, and current installer configurations log this status in the file /var/log/mysqld.log; however, this file is not present. While there is a /var/log/mariadb/mariadb.log that we are already getting, this is typically only populated during the initial server configuration phase; the actual galera bootstrapping / clustering ends up in /var/log/mysqld.log since Mariadb is run under Pacemaker OCF resource agents for the full run, instead of via systemd which is only during setup. ...SNIP... --- Additional comment from Pavel Moravec on 2015-04-17 11:51:42 EDT --- Upstream issue: https://github.com/sosreport/sos/issues/554 --- Additional comment from Pavel Moravec on 2015-05-31 08:01:28 EDT --- Committed to upstream as https://github.com/sosreport/sos/commit/f8ab86cbd2302812cd9160bec4478cb4f84e1442
adding blocker flag for OSP 7 GA as this will make our lives a lot easier for bug report if this makes it in.
[root@overcloud-controller-2 tmp]# ll sosreport-overcloud-controller-2.localdomain-20150719070722/var/log/mysqld.log -rw-r-----. 1 mysql mysql 19557 Jul 19 04:51 sosreport-overcloud-controller-2.localdomain-20150719070722/var/log/mysqld.log sos-3.2-16.el7ost.2.noarch
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/RHEA-2015:1548