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.
Bug 967497 - corosync start error messages are not logged
Summary: corosync start error messages are not logged
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: corosync
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Jan Friesse
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-27 09:54 UTC by michal novacek
Modified: 2014-06-18 00:31 UTC (History)
2 users (show)

Fixed In Version: corosync-2.3.1-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 10:27:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Proposed patch - Output parse errors to syslog (1.31 KB, patch)
2013-06-20 10:36 UTC, Jan Friesse
no flags Details | Diff

Description michal novacek 2013-05-27 09:54:43 UTC
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 [1]. Looking into
/var/log/messages [2] 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 [3]. 

I believe that error output should be visible in /var/log/messages


Version-Release number of selected component (if applicable):
corosync-2.3.0-3.el7.x86_64

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

Additional info:

[1]
# 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[1]: Starting Corosync Cluster Engine...
May 27 08:21:13 virt-062 corosync[958]: [62B blob data]
May 27 08:21:13 virt-062 systemd[1]: corosync.service: control process exited, code=exited status=1
May 27 08:21:13 virt-062 systemd[1]: Failed to start Corosync Cluster Engine.
May 27 08:21:13 virt-062 systemd[1]: MESSAGE=Unit corosync.service entered failed state.

[2]
# grep corosync /var/log/messages
...
May 27 05:34:04 virt-062 corosync[1602]: Starting Corosync Cluster Engine (corosync): [FAILED]#015[  OK  ]
May 27 05:34:04 virt-062 systemd[1]: corosync.service: control process exited, code=exited status=1
May 27 05:34:04 virt-062 systemd[1]: MESSAGE=Unit corosync.service entered failed state.11

[3]
# 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.

Comment 2 Jan Friesse 2013-06-20 10:36:03 UTC
Created attachment 763402 [details]
Proposed patch - Output parse errors to syslog

Comment 3 Jan Friesse 2013-06-20 10:38:11 UTC
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.

Comment 6 Ludek Smid 2014-06-13 10:27:27 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.