You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 25, 2023. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
After restarting the trustbloc pods, orb-3-kms service has been running for a while with the following errors:
Pod restart seems to have resolved the issue.
Kubernetes can do this automatically if the service reports such failure with its health-check endpoint.
The text was updated successfully, but these errors were encountered: