Backup and restore errors (KOTS)
Replicated has documented the following scenarios.
Error message | Reason | Workaround |
|---|---|---|
Error executing hook | When a cluster is restarted, some pods might be in a Shutdown state, meaning they were likely replaced by new pods. | Delete the pods that are in a Shutdown state: kubectl delete pods/<pod-name> |
Connect is not reachable after a restore even when pods are ready | If you restored a cluster on a new server with a different host name than the original, and updated the Host Name field in the KOTS Admin Console and deployed it, the httpproxy resource for nginx might not have been updated. | Delete the httproxy resource for nginx and redeploy it: kubectl delete httpproxy/nginx |