Consul service stuck in activating mode

Consul
2

Hi @mrxdane,

Welcome to the HashiCorp Forums!

It looks like the systemd unit file has been recently changed to type notify, which previously was simple.

According to the documentation, Consul would only notify systemd when a LAN join has completed.

When running under systemd on Linux, Consul notifies systemd by sending READY=1 to the $NOTIFY_SOCKET when a LAN join has completed. For this either the join or retry_join option has to be set and the service definition file has to have Type=notify set.
ref: Agents Overview | Consul | HashiCorp Developer

You can get it fixed by adding retry_join or join in the config file and setting the IP to the bind address of Consul on the host and restarting the agent. For example, in your case:

retry_join = ["{{ GetInterfaceIP \"enp0s1\" }}"]

The alternate option is to change the Unit file type to simple by editing it.

ref:

I hope this helps.