During the start-up process for Vault you may see entries in the journald logs relating to 'Unknown lvalue' entries. Examples include:
/usr/lib/systemd/system/vault.service:7 Unknown lvalue 'StartLimitIntervalSec' in section 'Unit'
/usr/lib/systemd/system/vault.service:29: Unknown lvalue 'StartLimitIntervalSec' in section 'Service'
/usr/lib/systemd/system/vault.service:8 Unknown lvalue 'StartLimitBurst' in section 'Unit'
- HashiCorp provide systemd service files with distribution specific packages of Vault (rpm, deb etc) that aim to maintain compatibility across many OS versions and systemd releases.
- Placement and presence of configuration variables in systemd service files has evolved over time, as a result customers may see warnings logged when using the default configurations.
Changes are not required with the messages able to be safely ignored, however if you wish to prevent the message being logged there are two options:
- Confirm the systemd version in use on the system running Vault, establish whether the configuration variable mentioned in the log is supported, and if so, move it to the [Unit] or [Service] stanza appropriate for your system.
- If unsupported, or unrequired, consider commenting out or removing the configuration variable.
- After making changes to the systemd service file the daemon should be reloaded using the systemctl daemon-reload command. After the next restart of Vault the logs can be examined to confirm the warning is no longer logged.