vault server -dev
Jump to navigation
Jump to search
vault server -dev
==> Vault server configuration: Api Address: http://127.0.0.1:8200 Cgo: disabled Cluster Address: https://127.0.0.1:8201 Go Version: go1.17.1 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") Log Level: info Mlock: supported: false, enabled: false Recovery Mode: false Storage: inmem Version: Vault v1.8.4 Version Sha: 925bc650ad1d997e84fbb832f302a6bfe0105bbb+CHANGES ==> Vault server started! Log data will stream in below: 2021-11-24T17:41:48.205+0300 [INFO] proxy environment: http_proxy="" https_proxy="" no_proxy="" 2021-11-24T17:41:48.205+0300 [WARN] no `api_addr` value specified in config or in VAULT_API_ADDR; falling back to detection if possible, but this value should be manually set 2021-11-24T17:41:48.207+0300 [INFO] core: security barrier not initialized 2021-11-24T17:41:48.207+0300 [INFO] core: security barrier initialized: stored=1 shares=1 threshold=1 2021-11-24T17:41:48.208+0300 [INFO] core: post-unseal setup starting 2021-11-24T17:41:48.210+0300 [INFO] core: loaded wrapping token key 2021-11-24T17:41:48.210+0300 [INFO] core: successfully setup plugin catalog: plugin-directory="" 2021-11-24T17:41:48.210+0300 [INFO] core: no mounts; adding default mount table 2021-11-24T17:41:48.213+0300 [INFO] core: successfully mounted backend: type=cubbyhole path=cubbyhole/ 2021-11-24T17:41:48.214+0300 [INFO] core: successfully mounted backend: type=system path=sys/ 2021-11-24T17:41:48.215+0300 [INFO] core: successfully mounted backend: type=identity path=identity/ 2021-11-24T17:41:48.216+0300 [INFO] core: successfully enabled credential backend: type=token path=token/ 2021-11-24T17:41:48.216+0300 [INFO] rollback: starting rollback manager 2021-11-24T17:41:48.216+0300 [INFO] core: restoring leases 2021-11-24T17:41:48.218+0300 [INFO] expiration: lease restore complete 2021-11-24T17:41:48.218+0300 [INFO] identity: entities restored 2021-11-24T17:41:48.218+0300 [INFO] identity: groups restored 2021-11-24T17:41:48.218+0300 [INFO] core: post-unseal setup complete 2021-11-24T17:41:48.218+0300 [INFO] core: root token generated 2021-11-24T17:41:48.218+0300 [INFO] core: pre-seal teardown starting 2021-11-24T17:41:48.218+0300 [INFO] rollback: stopping rollback manager 2021-11-24T17:41:48.218+0300 [WARN] activity: could not list segments: error="context canceled" 2021-11-24T17:41:48.218+0300 [WARN] activity: could not load intent log: error="context canceled" 2021-11-24T17:41:48.218+0300 [INFO] core: pre-seal teardown complete 2021-11-24T17:41:48.218+0300 [INFO] core.cluster-listener.tcp: starting listener: listener_address=127.0.0.1:8201 2021-11-24T17:41:48.218+0300 [INFO] core.cluster-listener: serving cluster requests: cluster_listen_address=127.0.0.1:8201 2021-11-24T17:41:48.218+0300 [INFO] core: post-unseal setup starting 2021-11-24T17:41:48.219+0300 [INFO] core: loaded wrapping token key 2021-11-24T17:41:48.219+0300 [INFO] core: successfully setup plugin catalog: plugin-directory="" 2021-11-24T17:41:48.219+0300 [INFO] core: successfully mounted backend: type=system path=sys/ 2021-11-24T17:41:48.219+0300 [INFO] core: successfully mounted backend: type=identity path=identity/ 2021-11-24T17:41:48.219+0300 [INFO] core: successfully mounted backend: type=cubbyhole path=cubbyhole/ 2021-11-24T17:41:48.219+0300 [INFO] core: successfully enabled credential backend: type=token path=token/ 2021-11-24T17:41:48.219+0300 [INFO] rollback: starting rollback manager 2021-11-24T17:41:48.219+0300 [INFO] core: restoring leases 2021-11-24T17:41:48.219+0300 [INFO] identity: entities restored 2021-11-24T17:41:48.219+0300 [INFO] identity: groups restored 2021-11-24T17:41:48.219+0300 [INFO] core: post-unseal setup complete 2021-11-24T17:41:48.219+0300 [INFO] core: vault is unsealed 2021-11-24T17:41:48.219+0300 [INFO] expiration: lease restore complete 2021-11-24T17:41:48.221+0300 [INFO] core: successful mount: namespace="" path=secret/ type=kv 2021-11-24T17:41:48.232+0300 [INFO] secrets.kv.kv_0238206e: collecting keys to upgrade 2021-11-24T17:41:48.232+0300 [INFO] secrets.kv.kv_0238206e: done collecting keys: num_keys=1 2021-11-24T17:41:48.232+0300 [INFO] secrets.kv.kv_0238206e: upgrading keys finished WARNING! dev mode is enabled! In this mode, Vault runs entirely in-memory and starts unsealed with a single unseal key. The root token is already authenticated to the CLI, so you can immediately begin using Vault. You may need to set the following environment variable: $ export VAULT_ADDR='http://127.0.0.1:8200' The unseal key and root token are displayed below in case you want to seal/unseal the Vault or re-authenticate. Unseal Key: MnV9TaMJSeGxnRuJRGSHjCiUyScC2h7tLq6+97buqIQ= Root Token: s.rppgCJN4SbOyM0ZYPgDgl7xB Development mode should NOT be used in production installations!
Errors
vault server -dev Error parsing listener configuration. Error initializing listener of type tcp: listen tcp 127.0.0.1:8200: bind: address already in use 2022-11-30T21:16:00.905+0400 [INFO] proxy environment: http_proxy="" https_proxy="" no_proxy="" 2022-11-30T21:16:00.905+0400 [WARN] no `api_addr` value specified in config or in VAULT_API_ADDR; falling back to detection if possible, but this value should be manually set 2022-11-30T21:16:00.907+0400 [INFO] core: Initializing version history cache for core
Related
brew services stop vault vault status
See also
vault [ secrets enable | kv put | kv get | server | operator | auth | token | secrets | auth enable | status
] Vault Changelog,vault help
Advertising: