To edit a setting (and have your edit survive reboots), make the setting as shown below. Settings you change in this manner will survive reboots and soft restarts but they will not survive upgrades.
- Login as root into queen and use a text editor to open the file, /home/beehive/config/procmgmtConfigs/coordinator.cfg
-
Find the “queenExec” section, which looks like:
"taskName": "queenExec", "nodeIps": "REPLACE_NODE_IP", "executableLocation": "/home/beehive/bin/exec/queenExec", "maxTaskRestarts": -1
-
Add the executableArgs section to the above section as shown below:
"executableArgs": "<flags in CSV format>"
For example, executableArgs for Scenario 1 (described earlier in this chapter) will look like:
"taskName": "queenExec", "nodeIps": "REPLACE_NODE_IP", "executableLocation": "/home/beehive/bin/exec/queenExec", "maxTaskRestarts": -1, "executableArgs": "--disallowPeerWithoutCertificates=false, --allowSelfSignedPeer=true,--trustedCAFileName=/home/beehive/certs/ server.pem,--sslCertificatePath=/home/beehive/certs/server.cert, --sslPrivateKeyPath=/home/beehive/certs/server.key,--sslFileType=1"
- Soft restart and activate the cluster.
You cannot configure the SSL flags on the queen to persist after Aster Database upgrades. The above coordinator.cfg file will be overwritten the next time you upgrade. Before every upgrade, make a copy of your configuration changes and reapply them after the upgrade. This step is part of the documented upgrade procedure.