Red Hat Bugzilla – Bug 587526
ccs_sync SIGABRTs when called with non-existing cluster node
Last modified: 2016-04-26 10:43:24 EDT
Description of problem:
If ccs_sync is called with wrong parameters, it dies screeming with SIGABRT and dumps core.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. run a bogus ccs_sync command, like "ccs_sync foo"
2. There is no cluster node "foo". See the process die screaming
Warning: foo is not listed as a node in /etc/cluster/cluster.conf
*** glibc detected *** ccs_sync: double free or corruption (top): 0x0000000001039710 ***
======= Backtrace: =========
======= Memory map: ========
Aborted (core dumped)
Should just echo the error message and die with no further noise.
have only tested on x86_64
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
[root@ask-03 ~]# ccs_sync blah
Error: blah is not listed as a node in /etc/cluster/cluster.conf
Created attachment 414975 [details]
Patch to fix bz
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.