Red Hat Bugzilla – Bug 609978
cman_tool man page needs better documentation for config upgrade procedure and requirements
Last modified: 2016-04-26 09:53:42 EDT
Description of problem:
ccs_tool update is no longer an option.
Reading through man cman_tool I found 'version' parameter might be a good choice...
[root@marathon-01 ~]# cman_tool version -r 14
Error: Unable to initialize the crypto subsystem.
cman_tool: ccs_sync failed.
If you have distributed the config file yourself, try re-running with -S
cman_tool does not provide any -S option (at least not in manpage)
[root@marathon-01 ~]# cman_tool version -S
6.2.0 config 13
Does nothing, does not complain...?
It might be for ccs_sync then...
[root@marathon-01 ~]# man ccs_sync
No manual entry for ccs_sync
[root@marathon-01 ~]# ccs_sync -h
Usage: ccs_sync [options] [<host0> [... <hostN>]]
-f <cluster_conf> Path to the cluster.conf file to propagate.
-c <NSS certificate DB> Path to your cacert.pem file.
-i Increment the configuration version before propagating.
-h Print this help dialog.
-p <port number> Connect to ricci on the specified port.
-w Exit with failure status if any warnings are issued.
-v Print version information.
So where is the -S?
and how shall I update the config file?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. see above
I'm kind of lost in cluster.conf update procedure.
I'll be guided through manpages and reasonable error messages, no undocumented options.
filed ccs_sync man page request as Bug 610042.
It's better to just use 'cman_tool version -r <x>' instead of calling ccs_sync directly.
Commit to STABLE3:
Author: Christine Caulfield <email@example.com>
Date: Mon Jul 5 15:03:36 2010 +0100
cman: Mention cman_tool version -S in man page
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.