Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error checking seal status: i/o timeout #100

Open
Klaudioz opened this issue Nov 29, 2021 · 0 comments
Open

Error checking seal status: i/o timeout #100

Klaudioz opened this issue Nov 29, 2021 · 0 comments

Comments

@Klaudioz
Copy link

What did you expect to happen?
Getting result to the command. In this case: vault status after finishing terraform apply

What actually happened?
Getting a timeout.

Output

Error checking seal status: Get "https://<API_ADDRESS>/v1/sys/seal-status": dial tcp <API_ADDRESS>:443: i/o timeout

Additional context
terraform apply finished OK and I've set all the env variables.

Logs:

k logs vault-0 vault
==> Vault server configuration:

  GCP KMS Crypto Key: vault-init
    GCP KMS Key Ring: vault-0606310c610082fb
     GCP KMS Project: terraform-sandbox-332920
      GCP KMS Region: us-east4
           Seal Type: gcpckms
         Api Address: https://34.150.235.40
                 Cgo: disabled
     Cluster Address: https://10.0.92.3:8201
          Listener 1: tcp (addr: "127.0.0.1:8200", cluster address: "127.0.0.1:8201", max_request_duration: "1m30s", max_request_size: "33554432", tls: "disabled")
          Listener 2: tcp (addr: "10.0.92.3:8200", cluster address: "10.0.92.3:8201", max_request_duration: "1m30s", max_request_size: "33554432", tls: "enabled")
           Log Level: warn
               Mlock: supported: true, enabled: true
             Storage: gcs (HA available)
             Version: Vault v1.2.1

==> Vault server started! Log data will stream in below:

2021-11-23T16:32:55.635Z [WARN] failed to unseal core: error="stored unseal keys are supported, but none were found"
2021-11-23T16:32:59.935Z [WARN] core: stored keys supported on init, forcing shares/threshold to 1
2021-11-23T16:33:04.599Z [WARN] core: attempted unseal with stored keys, but vault is already unsealed
2021-11-24T16:29:14.764Z [WARN] core: leadership lost, stopping active operation

k logs vault-0 vault-init

...
...
2021/11/29 15:47:47 Vault is unsealed and in standby mode.
2021/11/29 15:47:47 Next check in 10s
2021/11/29 15:47:57 Vault is unsealed and in standby mode.
2021/11/29 15:47:57 Next check in 10s
2021/11/29 15:48:07 Vault is unsealed and in standby mode.
2021/11/29 15:48:07 Next check in 10s
2021/11/29 15:48:17 Vault is unsealed and in standby mode.
2021/11/29 15:48:17 Next check in 10s

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant