Vault shutdown triggered - Reason

[Chintan Patel]

Hello,

I'm using vault with consul backend. Sometimes vault gets shutdown automatically. Here are the logs from vault.

[INFO ] physical/consul: Shutting down consul backend
==> Vault shutdown triggered
[INFO ] core: acquired lock, enabling active operation
[WARN ] physical/consul: Concurrent state change notify dropped
[INFO ] core: post-unseal setup starting
[INFO ] core: loaded wrapping token key
[INFO ] core: successfully mounted backend: type=generic path=secret/
[INFO ] core: successfully mounted backend: type=cubbyhole path=cubbyhole/
[INFO ] core: successfully mounted backend: type=system path=sys/
[INFO ] rollback: starting rollback manager
[INFO ] expiration: restoring leases
[INFO ] expire: leases restored: restored_lease_count=1
[WARN ] core: stopping active operation
[INFO ] core/startClusterListener: starting listener: listener_address=0.0.0.0:8201
[INFO ] core/startClusterListener: serving cluster requests: cluster_listen_address=[::]:8201
[INFO ] core: post-unseal setup complete
[INFO ] core/startClusterListener: shutting down listeners
[WARN ] physical/consul: Concurrent state change notify dropped
[INFO ] core: pre-seal teardown starting
[INFO ] core/stopClusterListener: stopping listeners
[INFO ] core/startClusterListener: listeners successfully shut down
[INFO ] core/stopClusterListener: success
[INFO ] rollback: stopping rollback manager
[INFO ] core: pre-seal teardown complete
[INFO ] core: vault is sealed
[WARN ] physical/consul: Concurrent sealed state change notify dropped

I want to know which event triggers vault shutdown. 

Thanks in advance. :)

[Jeff Mitchell]

Hi Chintan,

Shutdown is triggered (in a way that will print out that message) if Vault receives a SIGINT or SIGTERM.

Best,

Jeff

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/hashicorp/vault/issues
IRC: #vault-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Vault" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vault-tool+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vault-tool/c42bbe37-89df-4b25-b06c-a841934251db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Chintan Patel]

Hello Jeff,

Is there any possibilities that consul sent SIGINT or SIGTERM to vault in my case ?

To unsubscribe from this group and stop receiving emails from it, send an email to vault-tool+...@googlegroups.com.