Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Feature:
When setting up a new cluster, configure corosync to log to its log file.
Reason:
Previously only logging to syslog was enabled which caused the corosync log was possibly incomplete.
Result:
Logging to a file in corosync.conf is enabled.
Description of problem:
Currently, pcs generated config file doesn't contain logging to log file and only logging to syslog is configured. This is suboptimal, because both journald and syslogd has tendency to throw out messages what makes /var/log/messages unusable.
Also there is no possibility to turn on debugging (debug or trace) using pcs.
Version-Release number of selected component (if applicable):
0.9.135
How reproducible:
100%
Steps to Reproduce:
1. generate corosync.conf using pcs
Actual results:
corosync.conf:
...
logging {
to_syslog: yes
}
...
Expected results:
...
logging {
to_logfile: yes
logfile: /var/log/cluster/corosync.log
to_syslog: yes
}
...
Additional info:
Before Fix:
[root@rh71-node1 ~]# rpm -q pcs
pcs-0.9.140-1.el7.x86_64
[root@rh71-node1:~]# pcs cluster setup --name test rh71-node1 rh71-node2
Shutting down pacemaker/corosync services...
Redirecting to /bin/systemctl stop pacemaker.service
Redirecting to /bin/systemctl stop corosync.service
Killing any remaining services...
Removing all cluster configuration files...
rh71-node1: Succeeded
rh71-node2: Succeeded
Synchronizing pcsd certificates on nodes rh71-node1, rh71-node2. pcsd needs to be restarted on the nodes in order to reload the certificates.
[root@rh71-node1:~]# grep -A5 logging /etc/corosync/corosync.conf
logging {
to_syslog: yes
}
After Fix:
[root@rh71-node1:~]# rpm -q pcs
pcs-0.9.141-1.el7.x86_64
[root@rh71-node1:~]# pcs cluster setup --name test rh71-node1 rh71-node2
Shutting down pacemaker/corosync services...
Stopping pacemaker (via systemctl): [ OK ]
Redirecting to /bin/systemctl stop corosync.service
Killing any remaining services...
Removing all cluster configuration files...
rh71-node1: Succeeded
rh71-node2: Succeeded
Synchronizing pcsd certificates on nodes rh71-node1, rh71-node2. pcsd needs to be restarted on the nodes in order to reload the certificates.
[root@rh71-node1:~]# grep -A5 logging /etc/corosync/corosync.conf
logging {
to_logfile: yes
logfile: /var/log/cluster/corosync.log
to_syslog: yes
}
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://rhn.redhat.com/errata/RHSA-2015-2290.html
Description of problem: Currently, pcs generated config file doesn't contain logging to log file and only logging to syslog is configured. This is suboptimal, because both journald and syslogd has tendency to throw out messages what makes /var/log/messages unusable. Also there is no possibility to turn on debugging (debug or trace) using pcs. Version-Release number of selected component (if applicable): 0.9.135 How reproducible: 100% Steps to Reproduce: 1. generate corosync.conf using pcs Actual results: corosync.conf: ... logging { to_syslog: yes } ... Expected results: ... logging { to_logfile: yes logfile: /var/log/cluster/corosync.log to_syslog: yes } ... Additional info: