When attempting to backup a database to a DD Boost server, the backup fails with the error message "The system hostname key is missing from the lockbox". A complete error log is displayed below:
[root@mdw ~]# /bin/su - gpadmin -c "/usr/local/greenplum-db/bin/gpcrondump -x testdb --ddboost -z -a" > /home/gpadmin/gpAdminLogs/log_cron.out 2>&1 [root@mdw ~]# cat /home/gpadmin/gpAdminLogs/log_cron.out 20140507:12:44:06:072120 gpcrondump:mdw:gpadmin-[INFO]:-Starting gpcrondump with args: -x testdb --ddboost -z -a 20140507:12:44:06:072120 gpcrondump:mdw:gpadmin-[INFO]:-Bypassing disk space checks due to DDBoost parameters 20140507:12:44:06:072120 gpcrondump:mdw:gpadmin-[INFO]:-DDBoost command /usr/local/greenplum-db/./bin/gpddboost --show-config returned error: cmd had rc=255 completed=True halted=False stdout='' stderr='20140507:12:44:06|ddboost-[DEBUG]:-Libraries were loaded successfully 20140507:12:44:06|ddboost-[INFO]:-opening LB on /home/gpadmin/DDBOOST_CONFIG 20140507:12:44:06|ddboost-[ERROR]:-The system hostname key is missing from the lockbox. 20140507:12:44:06|ddboost-[ERROR]:-Parsing DDBoost login credentials failed ' 20140507:12:44:06:072120 gpcrondump:mdw:gpadmin-[CRITICAL]:-gpcrondump failed. (Reason='DD Boost: Unknown Error') exiting...
This error is caused by changes made on the hosts after the initial DD Boost configuration has been created.
The changes can include server replacement, new hostname, etc.
The DD Boost configuration is pointing to the old hostname. The DD Boost needs to be reconfigured.
Note: When this failure occurs, gpcrondump and gpdbrestore produce a similar error message. The instructions below can be applied to both gpcrondump and gpdbrestore.
1. Remove the old existing configuration:
gpcrondump --ddboost-config-remove
2. Reconfigure the DD Boost using the following command:
gpcrondump --ddboost-host <DDboost-hostname> --ddboost-user <DDboost-username> --ddboost-backupdir <DDboost-directory>