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.

Description of problem:
multiple corosync processes can be started, which results in havoc on the local node.

Version-Release number of selected component (if applicable):
corosync-1.2.3-20.el6

How reproducible:
100%

Steps to Reproduce:
1. corosync -f &
2. corosync -f
3.
  
Actual results:
Second corosync invocation starts, resulting in bad behavior.

Expected results:
Second corosync should not start, instead printing an appropriate error to the logs.

Additional info:

Created attachment 440756 [details]
patch honza submitted to address rfe

Created attachment 440757 [details]
revision 3026 - second part of patch to address problem

$ service cman start
$ cd /etc/corosync; cp corosync.conf.example corosync.conf
$ corosync -f ; echo $?
18

Mar  9 10:44:18 z4 corosync[26988]:   [MAIN  ] Another Corosync instance is already running.

Behaves as expected, maybe some error message printed would be useful.

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0764.html