Red Hat Bugzilla – Bug 967497
corosync start error messages are not logged
Last modified: 2014-06-17 20:31:28 EDT
Description of problem:
I have a corosync with existing but empty /etc/corosync/corosync.conf (which
happened unintentionally). Starting corosync using "systemctl start corosync"
gives you no error output -- it only says that it has failed . Looking into
/var/log/messages  gives you the same non-specific information about why the
failure happened. To find the real problem you must run corosync on commandline
with -f to see that some error message .
I believe that error output should be visible in /var/log/messages
Version-Release number of selected component (if applicable):
How reproducible: always
Steps to Reproduce:
1. have empty /etc/corosync/corosync.conf
2. run "systemctl start corosync"
Actual results: no error messages
Expected results: error message in /var/log/messages
# systemctl status corosync
corosync.service - Corosync Cluster Engine
Loaded: loaded (/usr/lib/systemd/system/corosync.service; enabled)
Active: failed (Result: exit-code) since Mon 2013-05-27 08:21:13 EDT
May 27 08:21:02 virt-062 systemd: Starting Corosync Cluster Engine...
May 27 08:21:13 virt-062 corosync: [62B blob data]
May 27 08:21:13 virt-062 systemd: corosync.service: control process exited, code=exited status=1
May 27 08:21:13 virt-062 systemd: Failed to start Corosync Cluster Engine.
May 27 08:21:13 virt-062 systemd: MESSAGE=Unit corosync.service entered failed state.
# grep corosync /var/log/messages
May 27 05:34:04 virt-062 corosync: Starting Corosync Cluster Engine (corosync): [FAILED]#015[ OK ]
May 27 05:34:04 virt-062 systemd: corosync.service: control process exited, code=exited status=1
May 27 05:34:04 virt-062 systemd: MESSAGE=Unit corosync.service entered failed state.11
# corosync -f
notice [MAIN ] Corosync Cluster Engine ('2.3.0'): started and ready to provide service.
info [MAIN ] Corosync built-in features: dbus rdma systemd xmlconf snmp pie relro bindnow
error [MAIN ] Could not open /etc/corosync/authkey: No such file or directory
error [MAIN ] Corosync Cluster Engine exiting with status 8 at main.c:1166.
Created attachment 763402 [details]
Proposed patch - Output parse errors to syslog
Yes, I can agree. Systemd behaves differently then old init, where output to stderr was visible on terminal. Systemd hides everything and status display something from journald. Proposed patch should solve problem.
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.