Skip to content

Tags: ansible-collections/ansible-consul

Tags

v3.0.1

Unverified

This commit is not signed, but one or more authors requires that any commit attributed to them is signed.
Retry restarting service on Windows

In some cases, Windows' ability to restart a service is faster than
consul's ability to shut down cleanly. In such cases, these lines can be
seen in the consul log:

[INFO]  agent.client: shutting down client
[ERROR] agent: Error starting agent: error="Failed to start Consul
client: Failed to start lan serf: Failed to create memberlist: Could not
set up network transport: failed to obtain an address: Failed to start
TCP listener on "10.50.0.45" port 8301: listen tcp 10.50.0.45:8301:
bind: Only one usage of each socket address (protocol/network
address/port) is normally permitted."
[INFO]  agent: Exit code: code=1

The log timestamps also show that all three messages occur at the exact
same time, indicating that there is likely a race condition here.
Usually, a second retry one second later should provide enough time to
beat the race condition, but for good measure, we'll retry up to three
times just to be safe.

v3.0.0

Unverified

This commit is not signed, but one or more authors requires that any commit attributed to them is signed.
fix(doc): fix the defaut value of consul_data_path in README

v2.6.1

Unverified

This commit is not signed, but one or more authors requires that any commit attributed to them is signed.
Changelog

v2.6.0

Consul v1.7.0 and more

v2.5.4

Merge branch 'devel'

v2.5.3

Consul v1.6.2

v2.5.1

CHANGELOG++

v2.5.0

Consul v1.6.0

v2.4.5

Consul v1.5.3 and more