After #146, systemd now waits for consul's notification of having joined the cluster before signaling that the service is alive. This however may occasionally result in larger waiting times and intermittent timeout failures.
The following error was observed in the terraform-aws-vault logs: Job for consul.service failed because a timeout was exceeded. See "systemctl status consul.service" and "journalctl -xe" for details.
As a remedy, this PR raises the timeout from 90s (the default) to a more reasonable 300s.
After #146, systemd now waits for consul's notification of having joined the cluster before signaling that the service is alive. This however may occasionally result in larger waiting times and intermittent timeout failures.
The following error was observed in the terraform-aws-vault logs:
Job for consul.service failed because a timeout was exceeded. See "systemctl status consul.service" and "journalctl -xe" for details.As a remedy, this PR raises the timeout from 90s (the default) to a more reasonable 300s.