Bug 626962

Summary: [RFE] don't allow multiple corosync processes to start on same system.
Product: Red Hat Enterprise Linux 6 Reporter: Steven Dake <sdake>
Component: corosyncAssignee: Jan Friesse <jfriesse>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: low Docs Contact:
Priority: low    
Version: 6.0CC: cluster-maint, jkortus, snagar
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: corosync-1.2.3-23.el6 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-19 14:24:07 UTC Type: ---
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:    
Bug Blocks: 655920    
Attachments:
Description Flags
patch honza submitted to address rfe
none
revision 3026 - second part of patch to address problem none

Description Steven Dake 2010-08-24 18:41:02 UTC 
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:
Comment 2 Steven Dake 2010-08-24 20:09:07 UTC 
Created attachment 440756 [details]
patch honza submitted to address rfe
Comment 3 Steven Dake 2010-08-24 20:11:24 UTC 
Created attachment 440757 [details]
revision 3026 - second part of patch to address problem
Comment 5 Jaroslav Kortus 2011-03-09 16:48:31 UTC 
$ 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.
Comment 6 errata-xmlrpc 2011-05-19 14:24:07 UTC 
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