Server start command: /usr/bin/vault server -config=/etc/vault/config.json
2022-11-04T09:38:56.700-0400 [ERROR] core: failed to retry join raft cluster: retry=2s err="failed to get raft challenge"
2022-11-04T09:38:58.701-0400 [INFO] core: security barrier not initialized
2022-11-04T09:38:58.711-0400 [INFO] core: attempting to join possible raft leader node: leader_addr=https://ottvault1.test.example.com:8443
2022-11-04T09:38:58.724-0400 [ERROR] core: failed to get raft challenge: leader_addr=https://ottvault1.test.example.com:8443
| error during raft bootstrap init call: Error making API request.
| URL: PUT https://ottvault1.test.example.com:8443/v1/sys/storage/raft/bootstrap/challenge
| Code: 503. Errors:
| * Vault is sealed
Error upon trying to initialize: [QA] ottvault1:~ # export VAULT_ADDR='https://ottvault1.test.example.com:8443
[QA] ottvault1:~ # vault operator init
Error initializing: Error making API request.
URL: PUT https://ottvault1.test.example.com:8443/v1/sys/init
Code: 400. Errors:
* could not start clustered storage: HeartbeatTimeout is too low
I’m simply trying to start a single node cluster for now for testing and experimentation purposes.
Reducing my config to the above allows it to start.
Currently trying to pinpoint which configuration element is causing the issue, but it’s not exactly obvious because none of them appear to be related to “HeartbeatTimeout” at the surface. Of course, this configuration is not ideal, and not production quality.
performance_multiplier(integer: 0) - An integer multiplier used by servers to scale key Raft timing parameters. Tuning this affects the time it takes Vault to detect leader failures and to perform leader elections, at the expense of requiring more network and CPU resources for better performance. Omitting this value or setting it to 0 uses default timing described below. Lower values are used to tighten timing and increase sensitivity while higher values relax timings and reduce sensitivity.
By default, Vault will use a lower-performance timing that’s suitable for minimal Vault servers, currently equivalent to setting this to a value of 5 (this default may be changed in future versions of Vault, depending if the target minimum server profile changes). Setting this to a value of 1 will configure Raft to its highest-performance mode and is recommended for production Vault servers. The maximum allowed value is 10.
So would this be a bug, or incorrect documentation?