Skip to content
This repository has been archived by the owner on Jan 25, 2023. It is now read-only.

Unknown lvalue 'StartLimitIntervalSec' in section 'Service' #171

Open
TechnicalMercenary opened this issue Dec 12, 2019 · 2 comments
Open

Comments

@TechnicalMercenary
Copy link

Using master to create a vault cluster and ran into an issue with the run-vault

`[root@ip-10-241-163-129 ec2-user]# service vault status
Redirecting to /bin/systemctl status vault.service
● vault.service - "HashiCorp Vault - A tool for managing secrets"
Loaded: loaded (/etc/systemd/system/vault.service; enabled; vendor preset: disabled)
Active: inactive (dead)
Condition: start condition failed at Thu 2019-12-12 18:35:45 UTC; 20s ago
ConditionFileNotEmpty=/opt/vault/config/default.hcl was not met
Docs: https://www.vaultproject.io/docs/

Dec 12 18:27:55 ip-10-241-163-129.systemd[1]: [/etc/systemd/system/vault.service:26] Unknown lvalue 'StartLimitIntervalSec' in section 'Service'
`
and

[/etc/systemd/system/vault.service:26] Unknown lvalue 'StartLimitIntervalSec' in section 'Service' [/usr/lib/systemd/system/irqbalance.service:12] Unknown lvalue 'ReadOnlyPaths' in section 'Service' [/usr/lib/systemd/system/irqbalance.service:13] Unknown lvalue 'ReadWritePaths' in section 'Service' [/usr/lib/systemd/system/irqbalance.service:15] Unknown lvalue 'TemporaryFileSystem' in section 'Service'

I'm using AWS Linux 2,

4.14.152-127.182.amzn2.x86_64 #1 SMP Thu Nov 14 17:32:43 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

and installing Vault 1.2.3

@TechnicalMercenary
Copy link
Author

When I fixed my issue in #172 by just adding a file. This error stopped happening.

@rahulraj2323
Copy link

@TechnicalMercenary I am getting the same error. Can you please help with what you did in order to fix it?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants