Skip to content
This repository has been archived by the owner on Aug 25, 2023. It is now read-only.

KMS should fail the health-check on DB communication failures #193

Open
project-administrator opened this issue Jun 2, 2021 · 0 comments

Comments

@project-administrator
Copy link

After restarting the trustbloc pods, orb-3-kms service has been running for a while with the following errors:

 [kms-rest] 2021/05/31 09:07:00 UTC - startcmd.startKmsService -> INFO Starting KMS on host 0.0.0.0:8081
 [kms/restapi] 2021/05/31 13:51:05 UTC - operation.(*Operation).writeErrorResponse -> ERROR Failed to resolve a keystore: resolve keystore: get keystore data: failure while scanning row: Not Found: Database does not exist.
 [kms/restapi] 2021/05/31 13:51:05 UTC - operation.(*Operation).writeErrorResponse -> ERROR Failed to resolve a keystore: resolve keystore: get keystore data: failure while scanning row: Not Found: Database does not exist.
 [kms/restapi] 2021/05/31 13:51:05 UTC - operation.(*Operation).writeErrorResponse -> ERROR Failed to resolve a keystore: resolve keystore: get keystore data: failure while scanning row: Not Found: Database does not exist.
...

Pod restart seems to have resolved the issue.
Kubernetes can do this automatically if the service reports such failure with its health-check endpoint.

@aholovko aholovko moved this to Todo in TrustBloc Orb Jan 5, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
No open projects
Status: No status
Development

No branches or pull requests

1 participant