Bug 1163671
| Summary: | [RFE] Default corosync configuration should log to file | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jan Friesse <jfriesse> | ||||
| Component: | pcs | Assignee: | Tomas Jelinek <tojeline> | ||||
| Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 7.0 | CC: | cluster-maint, mlisik, rsteiger, tojeline | ||||
| Target Milestone: | rc | Keywords: | FutureFeature | ||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | pcs-0.9.141-1.el7 | Doc Type: | Enhancement | ||||
| Doc Text: |
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.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-11-19 09:33:30 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | 1225441 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
Created attachment 1041644 [details]
proposed fix
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: