Re-running configure.sh after Configuration
If the configure.sh
script is initially run without the
-genkeys
option, the script generates a ssl_keystore
file
for use by the web server for the Control System.
Then if the configure.sh
script is re-run with the -genkeys
option, the system detects the existing
ssl_*
files and exits with an
error to prevent inadvertent deletion or reuse of the ssl_keystore
file.
NOTE
For general information on certificates, see SSL Certificates.To re-run
configure.sh
on clusters without security features enabled:
- Manually delete the
ssl_keystore
file on each node. - Run the
configure.sh -genkeys -R
command.
NOTE
The contents of the ssl_keystore
file are unique to each
node.To re-run
configure.sh
on clusters where the contents of the ssl_keystore
file are customized:
- Run the
configure.sh -genkeys -nocerts -R
command to preserve your customizations.
SSL Keys Error Message
The error message will look like the following example:
/opt/mapr/server/configure.sh
-secure -genkeys -C $CLDB_GRP -Z $ZK_GRP -RM $RM -HS
$HISTORYSERVER
<hostname1>: Configuring Hadoop-2.x at
/opt/mapr/hadoop/hadoop-2.x
<hostname1>: Done configuring Hadoop
<hostname1>: CLDB node list:
<hostname1>:7222,<hostname2>:7222,<hostname3>:7222
<hostname1>: Zookeeper node
list: <hostname1>:5181,<hostname2>:5181,<hostname3>:5181
<hostname1>: Node setup configuration: cldb fileserver
historyserver nfs nodemanager resourcemanager webserver
zookeeper
<hostname1>: Log can be found at:
/opt/mapr/logs/configure.log
<hostname1>: /opt/mapr/conf/ssl_keystore already exists
<hostname1>: ERROR: could not generate ssl keys. See log file
for more details
clush: <hostname1>: exited with exit code 1