openbao seems to hang using postgres #676

jmls · 2024-11-05T16:51:00Z

jmls
Nov 5, 2024

I am trying to get an openbao server to run using postgres. I am using an image built by myself - just a make dev, followed by some copies of scripts etc so nothing spectacular

if I start the server "normall" (ie bao server) using the following config

bao server -config=/openbao/config/bao.conf

where bao.conf is

storage "postgresql" {
  table = "vault_kv_store"
  path    = "vault/"
}

listener "tcp" {
  address = "0.0.0.0:8200"
  tls_disable = true
}

api_addr = "http://0.0.0.0:8200"
plugin_directory = "/openbao/plugins"
log_requests_level = "debug"
log_level = "debug"

I get the following in the console

==> OpenBao server configuration:

Administrative Namespace: 
             Api Address: http://0.0.0.0:8200
                     Cgo: disabled
         Cluster Address: https://0.0.0.0:8201
   Environment Variables: BAO_PG_CONNECTION_URL, HOME, HOSTNAME, PATH, PWD, SECUREABLE_DB_URL, SHLVL, TERM, VAULT_ADDR, VAULT_DISABLE_MLOCK
              Go Version: go1.23.2
              Listener 1: tcp (addr: "0.0.0.0:8200", cluster address: "0.0.0.0:8201", max_request_duration: "1m30s", max_request_size: "33554432", tls: "disabled")
               Log Level: debug
           Recovery Mode: false
                 Storage: postgresql (HA disabled)
                 Version: OpenBao v2.0.0-HEAD, built 2024-10-17T18:23:21Z
             Version Sha: f0c7ba32c664a186859743866b115150a8f7507c+CHANGES

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

2024-11-05T16:48:56.266Z [INFO]  proxy environment: http_proxy="" https_proxy="" no_proxy=""
2024-11-05T16:48:56.283Z [DEBUG] core: set config: sanitized config="{\"administrative_namespace_path\":\"\",\"api_addr\":\"http://0.0.0.0:8200\",\"cache_size\":0,\"cluster_addr\":\"\",\"cluster_cipher_suites\":\"\",\"cluster_name\":\"\",\"default_lease_ttl\":0,\"default_max_request_duration\":0,\"detect_deadlocks\":\"\",\"disable_cache\":false,\"disable_clustering\":false,\"disable_indexing\":false,\"disable_performance_standby\":false,\"disable_printable_check\":false,\"disable_sealwrap\":false,\"disable_sentinel_trace\":false,\"enable_response_header_hostname\":false,\"enable_response_header_raft_node_id\":false,\"enable_ui\":false,\"imprecise_lease_role_tracking\":false,\"introspection_endpoint\":false,\"listeners\":[{\"config\":{\"address\":\"0.0.0.0:8200\",\"tls_disable\":true},\"type\":\"tcp\"}],\"log_format\":\"\",\"log_level\":\"debug\",\"log_requests_level\":\"debug\",\"max_lease_ttl\":0,\"pid_file\":\"\",\"plugin_directory\":\"/openbao/plugins\",\"plugin_file_permissions\":0,\"plugin_file_uid\":0,\"raw_storage_endpoint\":false,\"seals\":[{\"disabled\":false,\"type\":\"shamir\"}],\"storage\":{\"cluster_addr\":\"\",\"disable_clustering\":false,\"redirect_addr\":\"http://0.0.0.0:8200\",\"type\":\"postgresql\"}}"
2024-11-05T16:48:56.283Z [DEBUG] storage.cache: creating LRU cache: size=0
2024-11-05T16:48:56.284Z [INFO]  core: Initializing version history cache for core
2024-11-05T16:48:56.284Z [DEBUG] cluster listener addresses synthesized: cluster_addresses=[0.0.0.0:8201]
2024-11-05T16:48:56.285Z [DEBUG] would have sent systemd notification (systemd not present): notification=READY=1

and there it stays - no further info, nothing. No errors,

If I start a dev server, it all works just peachy

am I missing some config ?

cipherboy · 2024-11-05T17:30:58Z

cipherboy
Nov 5, 2024
Maintainer

@jmls I think your instance is good to go. You haven't initialized the server yet, so the next step is to run bao operator init...

Reproduction

The path in the following config stanza is unrecognized, though ignored:

storage "postgresql" {
  table = "vault_kv_store"
  path    = "vault/" ### UNRECOGNIZED
}

not sure what you were intending with that...? It isn't present here: https://openbao.org/docs/configuration/storage/postgresql/

Also, how are you specifying connection_url? via BAO_PG_CONNECTION_URL or VAULT_PG_CONNECTION_URL?

I ran my PostgreSQL server via:

$ podman run --replace -p 5432:5432 --name openbao-postgres -e POSTGRES_PASSWORD=Secret123 -e POSTGRES_USER=openbao  postgres

and then using:

$ bao version
OpenBao v2.0.0-HEAD ('55966d9960d800032217fc6f3de61d2207b48a01'), built 2024-11-04T21:58:59Z

(i.e., latest main commit)

I see the same thing you do:

$ BAO_PG_CONNECTION_URL=postgres://openbao:Secret123@localhost:5432/postgres bao server -config=bao.conf
==> OpenBao server configuration:

Administrative Namespace: 
             Api Address: http://0.0.0.0:8200
                     Cgo: disabled
         Cluster Address: https://0.0.0.0:8201
   Environment Variables: BAO_PG_CONNECTION_URL, COLORTERM, DBUS_SESSION_BUS_ADDRESS, DEBUGINFOD_URLS, DESKTOP_SESSION, DISPLAY, DOCKER_HOST, EDITOR, GDMSESSION, GDM_LANG, GIT_EDITOR, GNOME_SETUP_DISPLAY, GNOME_TERMINAL_SCREEN, GNOME_TERMINAL_SERVICE, HISTCONTROL, HISTIGNORE, HISTSIZE, HOME, HOSTNAME, LANG, LESSOPEN, LOGNAME, LS_COLORS, MAIL, MEMORY_PRESSURE_WATCH, MEMORY_PRESSURE_WRITE, MOZ_GMP_PATH, PATH, PWD, P_HOST, P_USER, QT_IM_MODULE, SESSION_MANAGER, SHELL, SHLVL, SSH_ASKPASS, SSH_AUTH_SOCK, SYSTEMD_EXEC_PID, TERM, USER, USERNAME, VIRT_ADDR, VISUAL, VTE_VERSION, WAYLAND_DISPLAY, XAUTHORITY, XDG_CURRENT_DESKTOP, XDG_DATA_DIRS, XDG_MENU_PREFIX, XDG_RUNTIME_DIR, XDG_SESSION_CLASS, XDG_SESSION_DESKTOP, XDG_SESSION_TYPE, XMODIFIERS, _
              Go Version: go1.23.2
              Listener 1: tcp (addr: "0.0.0.0:8200", cluster address: "0.0.0.0:8201", max_request_duration: "1m30s", max_request_size: "33554432", tls: "disabled")
               Log Level: debug
           Recovery Mode: false
                 Storage: postgresql (HA disabled)
                 Version: OpenBao v2.0.0-HEAD, built 2024-11-04T21:58:59Z
             Version Sha: 55966d9960d800032217fc6f3de61d2207b48a01

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

2024-11-05T12:28:05.792-0500 [INFO]  proxy environment: http_proxy="" https_proxy="" no_proxy=""
2024-11-05T12:28:05.844-0500 [DEBUG] core: set config: sanitized config="{\"administrative_namespace_path\":\"\",\"api_addr\":\"http://0.0.0.0:8200\",\"cache_size\":0,\"cluster_addr\":\"\",\"cluster_cipher_suites\":\"\",\"cluster_name\":\"\",\"default_lease_ttl\":0,\"default_max_request_duration\":0,\"detect_deadlocks\":\"\",\"disable_cache\":false,\"disable_clustering\":false,\"disable_indexing\":false,\"disable_performance_standby\":false,\"disable_printable_check\":false,\"disable_sealwrap\":false,\"disable_sentinel_trace\":false,\"enable_response_header_hostname\":false,\"enable_response_header_raft_node_id\":false,\"enable_ui\":false,\"imprecise_lease_role_tracking\":false,\"introspection_endpoint\":false,\"listeners\":[{\"config\":{\"address\":\"0.0.0.0:8200\",\"tls_disable\":true},\"type\":\"tcp\"}],\"log_format\":\"\",\"log_level\":\"debug\",\"log_requests_level\":\"debug\",\"max_lease_ttl\":0,\"pid_file\":\"\",\"plugin_directory\":\"/openbao/plugins\",\"plugin_file_permissions\":0,\"plugin_file_uid\":0,\"raw_storage_endpoint\":false,\"seals\":[{\"disabled\":false,\"type\":\"shamir\"}],\"storage\":{\"cluster_addr\":\"\",\"disable_clustering\":false,\"redirect_addr\":\"http://0.0.0.0:8200\",\"type\":\"postgresql\"}}"
2024-11-05T12:28:05.844-0500 [DEBUG] storage.cache: creating LRU cache: size=0
2024-11-05T12:28:05.845-0500 [INFO]  core: Initializing version history cache for core
2024-11-05T12:28:05.846-0500 [DEBUG] cluster listener addresses synthesized: cluster_addresses=[0.0.0.0:8201]
2024-11-05T12:28:05.847-0500 [DEBUG] would have sent systemd notification (systemd not present): notification=READY=1

I can then operator init:

$ BAO_ADDR=http://localhost:8200
$ bao status
Key                Value
---                -----
Seal Type          shamir
Initialized        false
Sealed             true
Total Shares       0
Threshold          0
Unseal Progress    0/0
Unseal Nonce       n/a
Version            2.0.0-HEAD
Build Date         2024-11-04T21:58:59Z
Storage Type       postgresql
HA Enabled         false
[ascheel@cipherboy-precision 14]$ bao operator init
Unseal Key 1: XIVarTrwf+rRoXubbrXgMz6QtcAiko5Aullj2QAb/vco
Unseal Key 2: vrR4P5keWrabUyi/9K91Ig870ulDDZNEi/4zufkLrKgq
Unseal Key 3: OvMEbIajka9l0FYOmJmXOT+0qNo3RTCcOBamg2i2THXf
Unseal Key 4: MaJyEmQ0of6Rs34qMPaWwdS/v5GCgWVq9Yqn36zxVIVx
Unseal Key 5: WXMAHyDjWBYtevrCmvKGRLTeQ7PyjvnXQW5uhkSyGT1q

Initial Root Token: s.LeHHDmICSoAk2gtGug1Cw6Sa

Vault initialized with 5 key shares and a key threshold of 3. Please securely
distribute the key shares printed above. When the Vault is re-sealed,
restarted, or stopped, you must supply at least 3 of these keys to unseal it
before it can start servicing requests.

Vault does not store the generated root key. Without at least 3 keys to
reconstruct the root key, Vault will remain permanently sealed!

It is possible to generate new unseal keys, provided you have a quorum of
existing unseal keys shares. See "bao operator rekey" for more information.

and unseal and mount PKI:

$ bao operator unseal 'XIVarTrwf+rRoXubbrXgMz6QtcAiko5Aullj2QAb/vco'
Key                Value
---                -----
Seal Type          shamir
Initialized        true
Sealed             true
Total Shares       5
Threshold          3
Unseal Progress    1/3
Unseal Nonce       0ed5e924-2f35-781a-79a0-ab1d9a69e9b4
Version            2.0.0-HEAD
Build Date         2024-11-04T21:58:59Z
Storage Type       postgresql
HA Enabled         false
$ bao operator unseal 'vrR4P5keWrabUyi/9K91Ig870ulDDZNEi/4zufkLrKgq'
Key                Value
---                -----
Seal Type          shamir
Initialized        true
Sealed             true
Total Shares       5
Threshold          3
Unseal Progress    2/3
Unseal Nonce       0ed5e924-2f35-781a-79a0-ab1d9a69e9b4
Version            2.0.0-HEAD
Build Date         2024-11-04T21:58:59Z
Storage Type       postgresql
HA Enabled         false
$ bao operator unseal 'OvMEbIajka9l0FYOmJmXOT+0qNo3RTCcOBamg2i2THXf'
Key             Value
---             -----
Seal Type       shamir
Initialized     true
Sealed          false
Total Shares    5
Threshold       3
Version         2.0.0-HEAD
Build Date      2024-11-04T21:58:59Z
Storage Type    postgresql
Cluster Name    vault-cluster-f3f7e7cc
Cluster ID      44512945-386c-f042-47c1-b43e880009cb
HA Enabled      false
$ export BAO_TOKEN=s.LeHHDmICSoAk2gtGug1Cw6Sa
$ bao secrets enable pki
Success! Enabled the pki secrets engine at: pki/

and see more server logs:

2024-11-05T12:28:20.008-0500 [INFO]  core: security barrier not initialized
2024-11-05T12:28:20.008-0500 [INFO]  core: seal configuration missing, not initialized
2024-11-05T12:28:20.008-0500 [DEBUG] core: completed_request: start_time=2024-11-05T12:28:20-05:00 duration=3ms client_id="" client_address=127.0.0.1:45408 status_code=200 request_path=/v1/sys/seal-status request_method=GET
2024-11-05T12:28:20.009-0500 [DEBUG] core: completed_request: start_time=2024-11-05T12:28:20-05:00 duration=0ms client_id="" client_address=127.0.0.1:45408 status_code=200 request_path=/v1/sys/leader request_method=GET
2024-11-05T12:28:23.102-0500 [INFO]  core: security barrier not initialized
2024-11-05T12:28:23.103-0500 [INFO]  core: seal configuration missing, not initialized
2024-11-05T12:28:23.103-0500 [DEBUG] core: completed_request: start_time=2024-11-05T12:28:23-05:00 duration=1ms client_id="" client_address=127.0.0.1:36936 status_code=200 request_path=/v1/sys/seal-status request_method=GET
2024-11-05T12:28:23.104-0500 [INFO]  core: security barrier not initialized
2024-11-05T12:28:23.122-0500 [INFO]  core: security barrier initialized: stored=1 shares=5 threshold=3
2024-11-05T12:28:23.125-0500 [DEBUG] core: cluster name not found/set, generating new
2024-11-05T12:28:23.125-0500 [DEBUG] core: cluster name set: name=vault-cluster-f3f7e7cc
2024-11-05T12:28:23.125-0500 [DEBUG] core: cluster ID not found, generating new
2024-11-05T12:28:23.125-0500 [DEBUG] core: cluster ID set: id=44512945-386c-f042-47c1-b43e880009cb
2024-11-05T12:28:23.126-0500 [INFO]  core: post-unseal setup starting
2024-11-05T12:28:23.126-0500 [DEBUG] core: clearing forwarding clients
2024-11-05T12:28:23.126-0500 [DEBUG] core: done clearing forwarding clients
2024-11-05T12:28:23.126-0500 [DEBUG] core: persisting feature flags
2024-11-05T12:28:23.138-0500 [INFO]  core: loaded wrapping token key
2024-11-05T12:28:23.138-0500 [INFO]  core: upgrading plugin information: plugins=[]
2024-11-05T12:28:23.138-0500 [INFO]  core: successfully setup plugin catalog: plugin-directory=/openbao/plugins
2024-11-05T12:28:23.139-0500 [INFO]  core: no mounts; adding default mount table
2024-11-05T12:28:23.144-0500 [INFO]  core: successfully mounted: type=cubbyhole version="v2.0.0+builtin.bao" path=cubbyhole/ namespace="ID: root. Path: "
2024-11-05T12:28:23.144-0500 [INFO]  core: successfully mounted: type=system version="v2.0.0+builtin.bao" path=sys/ namespace="ID: root. Path: "
2024-11-05T12:28:23.145-0500 [INFO]  core: successfully mounted: type=identity version="v2.0.0+builtin.bao" path=identity/ namespace="ID: root. Path: "
2024-11-05T12:28:23.155-0500 [INFO]  core: successfully mounted: type=token version="v2.0.0+builtin.bao" path=token/ namespace="ID: root. Path: "
2024-11-05T12:28:23.157-0500 [INFO]  rollback: Starting the rollback manager with 256 workers
2024-11-05T12:28:23.157-0500 [INFO]  rollback: starting rollback manager
2024-11-05T12:28:23.157-0500 [INFO]  core: restoring leases
2024-11-05T12:28:23.157-0500 [DEBUG] expiration: collecting leases
2024-11-05T12:28:23.159-0500 [DEBUG] expiration: leases collected: num_existing=0
2024-11-05T12:28:23.159-0500 [INFO]  expiration: lease restore complete
2024-11-05T12:28:23.160-0500 [DEBUG] identity: loading entities
2024-11-05T12:28:23.160-0500 [DEBUG] identity: entities collected: num_existing=0
2024-11-05T12:28:23.160-0500 [INFO]  identity: entities restored
2024-11-05T12:28:23.160-0500 [DEBUG] identity: identity loading groups
2024-11-05T12:28:23.161-0500 [DEBUG] identity: groups collected: num_existing=0
2024-11-05T12:28:23.161-0500 [INFO]  identity: groups restored
2024-11-05T12:28:23.161-0500 [DEBUG] identity: identity loading OIDC clients
2024-11-05T12:28:23.161-0500 [INFO]  core: usage gauge collection is disabled
2024-11-05T12:28:23.162-0500 [INFO]  core: Recorded vault version: vault version=2.0.0 upgrade time="2024-11-05 17:28:23.161633263 +0000 UTC" build date=2024-11-04T21:58:59Z
2024-11-05T12:28:23.164-0500 [DEBUG] secrets.identity.identity_9bd538d1: wrote OIDC default provider
2024-11-05T12:28:23.165-0500 [DEBUG] secrets.identity.identity_9bd538d1: wrote OIDC default key
2024-11-05T12:28:23.166-0500 [DEBUG] secrets.identity.identity_9bd538d1: wrote OIDC allow_all assignment
2024-11-05T12:28:23.166-0500 [INFO]  core: post-unseal setup complete
2024-11-05T12:28:23.170-0500 [INFO]  core: root token generated
2024-11-05T12:28:23.170-0500 [INFO]  core: pre-seal teardown starting
2024-11-05T12:28:23.170-0500 [DEBUG] expiration: stop triggered
2024-11-05T12:28:23.170-0500 [DEBUG] expiration: finished stopping
2024-11-05T12:28:23.170-0500 [INFO]  rollback: stopping rollback manager
2024-11-05T12:28:23.170-0500 [INFO]  core: pre-seal teardown complete
2024-11-05T12:28:23.170-0500 [DEBUG] core: completed_request: start_time=2024-11-05T12:28:23-05:00 duration=67ms client_id="" client_address=127.0.0.1:36936 status_code=200 request_path=/v1/sys/init request_method=PUT
2024-11-05T12:29:49.067-0500 [DEBUG] core: completed_request: start_time=2024-11-05T12:29:49-05:00 duration=0ms client_id="" client_address=127.0.0.1:49644 status_code=503 request_path=/v1/sys/mounts/pki request_method=POST
2024-11-05T12:29:57.493-0500 [DEBUG] core: unseal key supplied: migrate=false
2024-11-05T12:29:57.495-0500 [DEBUG] core: cannot unseal, not enough keys: keys=1 threshold=3 nonce=0ed5e924-2f35-781a-79a0-ab1d9a69e9b4
2024-11-05T12:29:57.495-0500 [DEBUG] core: completed_request: start_time=2024-11-05T12:29:57-05:00 duration=1ms client_id="" client_address=127.0.0.1:50468 status_code=200 request_path=/v1/sys/unseal request_method=PUT
2024-11-05T12:29:57.495-0500 [DEBUG] core: completed_request: start_time=2024-11-05T12:29:57-05:00 duration=0ms client_id="" client_address=127.0.0.1:50468 status_code=200 request_path=/v1/sys/leader request_method=GET
2024-11-05T12:30:02.066-0500 [DEBUG] core: unseal key supplied: migrate=false
2024-11-05T12:30:02.066-0500 [DEBUG] core: cannot unseal, not enough keys: keys=2 threshold=3 nonce=0ed5e924-2f35-781a-79a0-ab1d9a69e9b4
2024-11-05T12:30:02.066-0500 [DEBUG] core: completed_request: start_time=2024-11-05T12:30:02-05:00 duration=0ms client_id="" client_address=127.0.0.1:57926 status_code=200 request_path=/v1/sys/unseal request_method=PUT
2024-11-05T12:30:02.066-0500 [DEBUG] core: completed_request: start_time=2024-11-05T12:30:02-05:00 duration=0ms client_id="" client_address=127.0.0.1:57926 status_code=200 request_path=/v1/sys/leader request_method=GET
2024-11-05T12:30:05.758-0500 [DEBUG] core: unseal key supplied: migrate=false
2024-11-05T12:30:05.759-0500 [DEBUG] core: starting cluster listeners
2024-11-05T12:30:05.759-0500 [INFO]  core.cluster-listener.tcp: starting listener: listener_address=0.0.0.0:8201
2024-11-05T12:30:05.759-0500 [INFO]  core.cluster-listener: serving cluster requests: cluster_listen_address=[::]:8201
2024-11-05T12:30:05.759-0500 [INFO]  core: post-unseal setup starting
2024-11-05T12:30:05.760-0500 [DEBUG] core: clearing forwarding clients
2024-11-05T12:30:05.760-0500 [DEBUG] core: done clearing forwarding clients
2024-11-05T12:30:05.760-0500 [DEBUG] core: persisting feature flags
2024-11-05T12:30:05.770-0500 [INFO]  core: loaded wrapping token key
2024-11-05T12:30:05.770-0500 [INFO]  core: upgrading plugin information: plugins=[]
2024-11-05T12:30:05.770-0500 [INFO]  core: successfully setup plugin catalog: plugin-directory=/openbao/plugins
2024-11-05T12:30:05.771-0500 [INFO]  core: successfully mounted: type=system version="v2.0.0+builtin.bao" path=sys/ namespace="ID: root. Path: "
2024-11-05T12:30:05.772-0500 [INFO]  core: successfully mounted: type=identity version="v2.0.0+builtin.bao" path=identity/ namespace="ID: root. Path: "
2024-11-05T12:30:05.772-0500 [INFO]  core: successfully mounted: type=cubbyhole version="v2.0.0+builtin.bao" path=cubbyhole/ namespace="ID: root. Path: "
2024-11-05T12:30:05.775-0500 [INFO]  core: successfully mounted: type=token version="v2.0.0+builtin.bao" path=token/ namespace="ID: root. Path: "
2024-11-05T12:30:05.776-0500 [INFO]  rollback: Starting the rollback manager with 256 workers
2024-11-05T12:30:05.776-0500 [INFO]  rollback: starting rollback manager
2024-11-05T12:30:05.776-0500 [INFO]  core: restoring leases
2024-11-05T12:30:05.776-0500 [DEBUG] expiration: collecting leases
2024-11-05T12:30:05.776-0500 [DEBUG] expiration: leases collected: num_existing=0
2024-11-05T12:30:05.777-0500 [INFO]  expiration: lease restore complete
2024-11-05T12:30:05.777-0500 [DEBUG] identity: loading entities
2024-11-05T12:30:05.777-0500 [DEBUG] identity: entities collected: num_existing=0
2024-11-05T12:30:05.777-0500 [INFO]  identity: entities restored
2024-11-05T12:30:05.777-0500 [DEBUG] identity: identity loading groups
2024-11-05T12:30:05.777-0500 [DEBUG] identity: groups collected: num_existing=0
2024-11-05T12:30:05.777-0500 [INFO]  identity: groups restored
2024-11-05T12:30:05.777-0500 [DEBUG] identity: identity loading OIDC clients
2024-11-05T12:30:05.778-0500 [DEBUG] core: request forwarding setup function
2024-11-05T12:30:05.778-0500 [DEBUG] core: clearing forwarding clients
2024-11-05T12:30:05.778-0500 [DEBUG] core: done clearing forwarding clients
2024-11-05T12:30:05.778-0500 [DEBUG] core: request forwarding not setup
2024-11-05T12:30:05.778-0500 [DEBUG] core: leaving request forwarding setup function
2024-11-05T12:30:05.778-0500 [INFO]  core: usage gauge collection is disabled
2024-11-05T12:30:05.779-0500 [INFO]  core: post-unseal setup complete
2024-11-05T12:30:05.779-0500 [INFO]  core: vault is unsealed
2024-11-05T12:30:05.779-0500 [DEBUG] core: completed_request: start_time=2024-11-05T12:30:05-05:00 duration=21ms client_id="" client_address=127.0.0.1:57930 status_code=200 request_path=/v1/sys/unseal request_method=PUT
2024-11-05T12:30:05.780-0500 [DEBUG] core: completed_request: start_time=2024-11-05T12:30:05-05:00 duration=0ms client_id="" client_address=127.0.0.1:57930 status_code=200 request_path=/v1/sys/leader request_method=GET
2024-11-05T12:30:08.464-0500 [INFO]  secrets.pki.pki_e59a9a1e: 9da7d60a-01b1-31c9-909d-3b8f5a1470a8: succeeded in migrating to issuer storage version 2
2024-11-05T12:30:08.464-0500 [DEBUG] secrets.pki.pki_e59a9a1e: Loading existing challenge validations on disk
2024-11-05T12:30:08.464-0500 [INFO]  core: successful mount: namespace="" path=pki/ type=pki version=""
2024-11-05T12:30:08.464-0500 [DEBUG] core: completed_request: start_time=2024-11-05T12:30:08-05:00 duration=15ms client_id=0DHqvq2D77kL2/JTPSZkTMJbkFVmUu0TzMi0jiXcFy8= client_address=127.0.0.1:57936 status_code=204 request_path=/v1/sys/mounts/pki request_method=POST
2024-11-05T12:30:08.465-0500 [DEBUG] secrets.pki.pki_e59a9a1e: Starting ACME challenge validation engine

...so I think everything should be working fine?

2 replies

jmls Nov 5, 2024
Author

and I am such an idiot ... I was investigating a bug report from a customer deploying a new system - and focused on their assertion that the system crashes out and the log does not show anything.

I didn't stop to think that it may be the customers fault by not running the init / unseal process

I beg forgiveness. It's been a long long day

cipherboy Nov 5, 2024
Maintainer

@jmls Absolutely no worries! Glad this resolved it, happy to see testing for this backend.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

OpenBao

openbao seems to hang using postgres #676

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 1 comment 2 replies

{{title}}

{{title}}

{{title}}

Select a reply

OpenBao

openbao seems to hang using postgres #676

jmls Nov 5, 2024

Replies: 1 comment · 2 replies

cipherboy Nov 5, 2024 Maintainer

jmls Nov 5, 2024 Author

cipherboy Nov 5, 2024 Maintainer

jmls
Nov 5, 2024

Replies: 1 comment 2 replies

cipherboy
Nov 5, 2024
Maintainer

jmls Nov 5, 2024
Author

cipherboy Nov 5, 2024
Maintainer