API tools faq
paste
Guest User

vault.log

a guest
Apr 11th, 2019
40
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 9.57 KB | None | 0 0
raw download clone embed print report
  1. ==> Vault server configuration:
  2.  
  3.  
  4.  
  5. Api Address: http://127.0.0.1:8200
  6.  
  7. Cgo: disabled
  8.  
  9. Cluster Address: https://127.0.0.1:8201
  10.  
  11. 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")
  12.  
  13. Log Level: trace
  14.  
  15. Mlock: supported: false, enabled: false
  16.  
  17. Storage: inmem
  18.  
  19. Version: Vault v1.1.0
  20.  
  21. Version Sha: 36aa8c8dd1936e10ebd7a4c1d412ae0e6f7900bd
  22.  
  23.  
  24.  
  25. WARNING! dev mode is enabled! In this mode, Vault runs entirely in-memory
  26.  
  27. and starts unsealed with a single unseal key. The root token is already
  28.  
  29. authenticated to the CLI, so you can immediately begin using Vault.
  30.  
  31.  
  32.  
  33. You may need to set the following environment variable:
  34.  
  35.  
  36.  
  37. PowerShell:
  38.  
  39. $env:VAULT_ADDR="http://127.0.0.1:8200"
  40.  
  41. cmd.exe:
  42.  
  43. set VAULT_ADDR=http://127.0.0.1:8200
  44.  
  45.  
  46.  
  47. The unseal key and root token are displayed below in case you want to
  48.  
  49. seal/unseal the Vault or re-authenticate.
  50.  
  51.  
  52.  
  53. Unseal Key: rbyRF8AZHWEPbG/kQkS617kXAsX9pZZ61PPvAgIlfRU=
  54.  
  55. Root Token: s.soYEl69kYDqJbgsJq5RZE8Of
  56.  
  57.  
  58.  
  59. Development mode should NOT be used in production installations!
  60.  
  61.  
  62.  
  63. ==> Vault server started! Log data will stream in below:
  64.  
  65.  
  66.  
  67. 2019-04-11T12:51:17.837+0300 [DEBUG] storage.cache: creating LRU cache: size=0
  68.  
  69. 2019-04-11T12:51:17.877+0300 [DEBUG] cluster listener addresses synthesized: cluster_addresses=[127.0.0.1:8201]
  70.  
  71. 2019-04-11T12:51:17.901+0300 [INFO] core: security barrier not initialized
  72.  
  73. 2019-04-11T12:51:17.901+0300 [INFO] core: security barrier initialized: shares=1 threshold=1
  74.  
  75. 2019-04-11T12:51:17.901+0300 [DEBUG] core: cluster name not found/set, generating new
  76.  
  77. 2019-04-11T12:51:17.901+0300 [DEBUG] core: cluster name set: name=vault-cluster-514d8fb1
  78.  
  79. 2019-04-11T12:51:17.901+0300 [DEBUG] core: cluster ID not found, generating new
  80.  
  81. 2019-04-11T12:51:17.901+0300 [DEBUG] core: cluster ID set: id=f25ba256-b307-3a37-36a5-85faba8ab13c
  82.  
  83. 2019-04-11T12:51:17.901+0300 [INFO] core: post-unseal setup starting
  84.  
  85. 2019-04-11T12:51:17.901+0300 [DEBUG] core: clearing forwarding clients
  86.  
  87. 2019-04-11T12:51:17.901+0300 [DEBUG] core: done clearing forwarding clients
  88.  
  89. 2019-04-11T12:51:17.915+0300 [INFO] core: loaded wrapping token key
  90.  
  91. 2019-04-11T12:51:17.915+0300 [INFO] core: upgrading plugin information: plugins=[]
  92.  
  93. 2019-04-11T12:51:17.915+0300 [INFO] core: successfully setup plugin catalog: plugin-directory=C:\Users\domain.user\Documents\vault\bin
  94.  
  95. 2019-04-11T12:51:17.915+0300 [INFO] core: no mounts; adding default mount table
  96.  
  97. 2019-04-11T12:51:17.916+0300 [INFO] core: successfully mounted backend: type=cubbyhole path=cubbyhole/
  98.  
  99. 2019-04-11T12:51:17.917+0300 [INFO] core: successfully mounted backend: type=system path=sys/
  100.  
  101. 2019-04-11T12:51:17.917+0300 [INFO] core: successfully mounted backend: type=identity path=identity/
  102.  
  103. 2019-04-11T12:51:17.919+0300 [INFO] core: successfully enabled credential backend: type=token path=token/
  104.  
  105. 2019-04-11T12:51:17.919+0300 [INFO] rollback: starting rollback manager
  106.  
  107. 2019-04-11T12:51:17.919+0300 [INFO] core: restoring leases
  108.  
  109. 2019-04-11T12:51:17.919+0300 [DEBUG] expiration: collecting leases
  110.  
  111. 2019-04-11T12:51:17.919+0300 [DEBUG] expiration: leases collected: num_existing=0
  112.  
  113. 2019-04-11T12:51:17.919+0300 [DEBUG] identity: loading entities
  114.  
  115. 2019-04-11T12:51:17.919+0300 [INFO] expiration: lease restore complete
  116.  
  117. 2019-04-11T12:51:17.919+0300 [DEBUG] identity: entities collected: num_existing=0
  118.  
  119. 2019-04-11T12:51:17.920+0300 [INFO] identity: entities restored
  120.  
  121. 2019-04-11T12:51:17.920+0300 [DEBUG] identity: identity loading groups
  122.  
  123. 2019-04-11T12:51:17.920+0300 [DEBUG] identity: groups collected: num_existing=0
  124.  
  125. 2019-04-11T12:51:17.920+0300 [INFO] identity: groups restored
  126.  
  127. 2019-04-11T12:51:17.920+0300 [INFO] core: post-unseal setup complete
  128.  
  129. 2019-04-11T12:51:17.920+0300 [INFO] core: root token generated
  130.  
  131. 2019-04-11T12:51:17.920+0300 [INFO] core: pre-seal teardown starting
  132.  
  133. 2019-04-11T12:51:17.920+0300 [DEBUG] expiration: stop triggered
  134.  
  135. 2019-04-11T12:51:17.920+0300 [DEBUG] expiration: finished stopping
  136.  
  137. 2019-04-11T12:51:17.920+0300 [INFO] rollback: stopping rollback manager
  138.  
  139. 2019-04-11T12:51:17.921+0300 [INFO] core: pre-seal teardown complete
  140.  
  141. 2019-04-11T12:51:17.921+0300 [INFO] core: vault is unsealed
  142.  
  143. 2019-04-11T12:51:17.921+0300 [DEBUG] core: starting cluster listeners
  144.  
  145. 2019-04-11T12:51:17.921+0300 [INFO] core.cluster-listener: starting listener: listener_address=127.0.0.1:8201
  146.  
  147. 2019-04-11T12:51:17.921+0300 [INFO] core: post-unseal setup starting
  148.  
  149. 2019-04-11T12:51:17.921+0300 [DEBUG] core: clearing forwarding clients
  150.  
  151. 2019-04-11T12:51:17.921+0300 [DEBUG] core: done clearing forwarding clients
  152.  
  153. 2019-04-11T12:51:17.921+0300 [INFO] core: loaded wrapping token key
  154.  
  155. 2019-04-11T12:51:17.921+0300 [INFO] core: upgrading plugin information: plugins=[]
  156.  
  157. 2019-04-11T12:51:17.921+0300 [INFO] core: successfully setup plugin catalog: plugin-directory=C:\Users\domain.user\Documents\vault\bin
  158.  
  159. 2019-04-11T12:51:17.921+0300 [INFO] core.cluster-listener: serving cluster requests: cluster_listen_address=127.0.0.1:8201
  160.  
  161. 2019-04-11T12:51:17.921+0300 [INFO] core: successfully mounted backend: type=system path=sys/
  162.  
  163. 2019-04-11T12:51:17.922+0300 [INFO] core: successfully mounted backend: type=identity path=identity/
  164.  
  165. 2019-04-11T12:51:17.922+0300 [INFO] core: successfully mounted backend: type=cubbyhole path=cubbyhole/
  166.  
  167. 2019-04-11T12:51:17.923+0300 [INFO] core: successfully enabled credential backend: type=token path=token/
  168.  
  169. 2019-04-11T12:51:17.923+0300 [INFO] core: restoring leases
  170.  
  171. 2019-04-11T12:51:17.923+0300 [INFO] rollback: starting rollback manager
  172.  
  173. 2019-04-11T12:51:17.923+0300 [DEBUG] expiration: collecting leases
  174.  
  175. 2019-04-11T12:51:17.923+0300 [DEBUG] identity: loading entities
  176.  
  177. 2019-04-11T12:51:17.923+0300 [DEBUG] expiration: leases collected: num_existing=0
  178.  
  179. 2019-04-11T12:51:17.923+0300 [DEBUG] identity: entities collected: num_existing=0
  180.  
  181. 2019-04-11T12:51:17.923+0300 [INFO] identity: entities restored
  182.  
  183. 2019-04-11T12:51:17.923+0300 [DEBUG] identity: identity loading groups
  184.  
  185. 2019-04-11T12:51:17.923+0300 [INFO] expiration: lease restore complete
  186.  
  187. 2019-04-11T12:51:17.923+0300 [DEBUG] identity: groups collected: num_existing=0
  188.  
  189. 2019-04-11T12:51:17.923+0300 [INFO] identity: groups restored
  190.  
  191. 2019-04-11T12:51:17.923+0300 [DEBUG] core: cluster listener setup function
  192.  
  193. 2019-04-11T12:51:17.923+0300 [DEBUG] core: clearing forwarding clients
  194.  
  195. 2019-04-11T12:51:17.923+0300 [DEBUG] core: done clearing forwarding clients
  196.  
  197. 2019-04-11T12:51:17.923+0300 [DEBUG] core: leaving cluster listener setup function
  198.  
  199. 2019-04-11T12:51:17.923+0300 [INFO] core: post-unseal setup complete
  200.  
  201. 2019-04-11T12:51:17.932+0300 [INFO] core: successful mount: namespace= path=secret/ type=kv
  202.  
  203. 2019-04-11T12:51:17.942+0300 [INFO] secrets.kv.kv_fa6f1222: collecting keys to upgrade
  204.  
  205. 2019-04-11T12:51:17.942+0300 [INFO] secrets.kv.kv_fa6f1222: done collecting keys: num_keys=1
  206.  
  207. 2019-04-11T12:51:17.942+0300 [DEBUG] secrets.kv.kv_fa6f1222: upgrading keys: progress=0/1
  208.  
  209. 2019-04-11T12:51:17.942+0300 [INFO] secrets.kv.kv_fa6f1222: upgrading keys finished
  210.  
  211. 2019-04-11T12:51:34.088+0300 [DEBUG] secrets.vault-pki-backend-venafi.vault-pki-backend-venafi_e1e4e910.vault-pki-backend-venafi: starting plugin: metadata=true path=C:\Users\domain.user\Documents\vault\bin\go_build_github_com_Venafi_vault_pki_backend_venafi.exe args=[C:\Users\domain.user\Documents\vault\bin\go_build_github_com_Venafi_vault_pki_backend_venafi.exe]
  212.  
  213. 2019-04-11T12:51:34.096+0300 [DEBUG] secrets.vault-pki-backend-venafi.vault-pki-backend-venafi_e1e4e910.vault-pki-backend-venafi: plugin started: metadata=true path=C:\Users\domain.user\Documents\vault\bin\go_build_github_com_Venafi_vault_pki_backend_venafi.exe pid=8668
  214.  
  215. 2019-04-11T12:51:34.096+0300 [DEBUG] secrets.vault-pki-backend-venafi.vault-pki-backend-venafi_e1e4e910.vault-pki-backend-venafi: waiting for RPC address: metadata=true path=C:\Users\domain.user\Documents\vault\bin\go_build_github_com_Venafi_vault_pki_backend_venafi.exe
  216.  
  217. 2019-04-11T12:51:34.162+0300 [DEBUG] secrets.vault-pki-backend-venafi.vault-pki-backend-venafi_e1e4e910.vault-pki-backend-venafi.go_build_github_com_Venafi_vault_pki_backend_venafi.exe: 2019/04/11 12:51:34 Starting plugin: metadata=true
  218.  
  219. 2019-04-11T12:51:34.163+0300 [DEBUG] secrets.vault-pki-backend-venafi.vault-pki-backend-venafi_e1e4e910.vault-pki-backend-venafi: using plugin: metadata=true version=4
  220.  
  221. 2019-04-11T12:51:34.163+0300 [DEBUG] secrets.vault-pki-backend-venafi.vault-pki-backend-venafi_e1e4e910.vault-pki-backend-venafi.go_build_github_com_Venafi_vault_pki_backend_venafi.exe: plugin address: metadata=true address=127.0.0.1:10000 network=tcp timestamp=2019-04-11T12:51:34.163+0300
  222.  
  223. 2019-04-11T12:51:34.167+0300 [TRACE] secrets.vault-pki-backend-venafi.vault-pki-backend-venafi_e1e4e910.vault-pki-backend-venafi: setup: transport=gRPC status=started
  224.  
  225. 2019-04-11 12:51:34.168772 I | [ERR] plugin: plugin acceptAndServe error: strconv.ParseInt: parsing "": invalid syntax
  226.  
  227. 2019-04-11T12:51:39.179+0300 [TRACE] secrets.vault-pki-backend-venafi.vault-pki-backend-venafi_e1e4e910.vault-pki-backend-venafi: setup: transport=gRPC status=finished err="rpc error: code = Unknown desc = timeout waiting for connection info" took=5.0115729s
  228.  
  229. 2019-04-11T12:51:39.179+0300 [ERROR] secrets.system.system_f6fd0e48: mount failed: path=venafi-pki/ error="rpc error: code = Unknown desc = timeout waiting for connection info"
Advertisement
Add Comment
Please, Sign In to add comment
Public Pastes
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!