Vault executing as background daemon

Vault
1

Hi,

I’m a newbie to Vault.
When I try to start the server, it always run as a background process.

$ vault server -config=/home/ubuntu/vault/config/config.hcl
==> Vault server configuration:

Administrative Namespace:
             Api Address: http://43.2xx.63.1xx:8200
                     Cgo: disabled
         Cluster Address: https://43.2xx.63.1xx:8201
   Environment Variables: DBUS_SESSION_BUS_ADDRESS, DISPLAY, GOTRACEBACK, HOME, LANG, LESSCLOSE, LESSOPEN, LOGNAME, LS_COLORS, MOTD_SHOWN, PATH, PWD, SHELL, SHLVL, SSH_CLIENT, SSH_CONNECTION, SSH_TTY, TERM, USER, VAULT_ADDR, VAULT_TOKEN, XDG_DATA_DIRS, XDG_RUNTIME_DIR, XDG_SESSION_CLASS, XDG_SESSION_ID, XDG_SESSION_TYPE, _
              Go Version: go1.21.9
              Listener 1: tcp (addr: "0.0.0.0:8200", cluster address: "0.0.0.0:8201", disable_request_limiter: "false", max_request_duration: "1m30s", max_request_size: "33554432", tls: "disabled")
               Log Level:
                   Mlock: supported: true, enabled: true
           Recovery Mode: false
                 Storage: file
                 Version: Vault v1.16.2, built 2024-04-22T16:25:54Z
             Version Sha: c6e4c2d4dc3b0d57791881b087c026e2f75a87cb

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

2024-05-01T00:52:18.564Z [INFO]  proxy environment: http_proxy="" https_proxy="" no_proxy=""
2024-05-01T00:52:18.564Z [INFO]  incrementing seal generation: generation=1
2024-05-01T00:52:18.674Z [INFO]  core: Initializing version history cache for core
2024-05-01T00:52:18.674Z [INFO]  events: Starting event system

And I can see this process is still alive even when I exit the terminal.

With ps axf, it gives

  62215 ?        SLl    0:00 vault server -config=/home/ubuntu/vault/config/config.hcl`

Does vault server application always run as background daemon even without running nohup?

Thanks!

2

I am able to reproduce this using the macOS native terminal app. It would appear as part of closing the terminal, the macOS terminal is not sending a SIGHUP to the running process. I get this if I close the terminal window with the red x button, or mac+q. You can see ps is a bit confused as the ? is there in place of the terminal session ID.

If I compare that with my preferred terminal (Tabby) it verifies I want to terminate the running Vault process and doesn’t allow me to close the terminal without terminating the process.

I can’t find anything recent on the macOS terminal app not sending SIGHUP to running processes, but think this is more of a terminal app issue than Vault issue.