90 days. Unlimited cores. Zero commitment | The VMware Exit built for service
Learn More
Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Consul Service Cannot Start: "bind_addr cannot be empty

Problem

  • A host is failing to converge on the pf9-ha-slave role.

  • The following warnings are present in /var/log/pf9/pf9-ha.log.

ha-manager WARNING Consul service stopped. Retrying... ha-manager WARNING sudo service pf9-consul status returned non-zero code

  • In /var/log/pf9/pf9-consul.log, the following error may also be observed.

==> bind_addr cannot be empty

Environment

  • Platform9 Managed OpenStack - All Versions

  • AZ with High Availability Enabled

Cause

The Cluster IP field which corresponds to the bind_addr for Consul is empty for the corresponding host in Clarity UI.

Screen_Shot_2019-09-06_at_12.42.58_PM.png
Screen_Shot_2019-09-06_at_12.42.58_PM.png

Resolution

  1. Set the Cluster IP to an IP which is accessible by other hosts which are part of the same host aggregate, associated with the AZ for which High Availability is enabled.

PreviousUnable to Attach Floating IP to Instance: "External Network Not Reachable from SubnetNextBoot From Volume Instance Fails to Spawn: "Block Device Mapping is Invalid

Last updated