You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue has already been observed and mentioned in #16844. Since it's kind of separate, I think it's useful to outline and track this in a new issue.
Since #16845 got merged single-node/dev setups of Consul don't work with systemd
out of the box any more. When running systemctl start consul systemd is just stuck and times out. Consul appears to start fine, but just systemd does not know that.
Online docs mention that the NOTIFY_SOCKET is only notified when a LAN join is completed and join or retry_join is set. Single node setups don't have that usually. Maybe it is related to that.
Overview of the Issue
This issue has already been observed and mentioned in #16844. Since it's kind of separate, I think it's useful to outline and track this in a new issue.
Since #16845 got merged single-node/dev setups of Consul don't work with systemd
out of the box any more. When running
systemctl start consul
systemd is just stuck and times out. Consul appears to start fine, but just systemd does not know that.Online docs mention that the NOTIFY_SOCKET is only notified when a LAN join is completed and
join
orretry_join
is set. Single node setups don't have that usually. Maybe it is related to that.Workaround
systemctl edit consul
Reproduction Steps
Consul info for both Client and Server
Consul info
Output from 'consul info' command here
HCL config
Operating system and Environment details
Log Fragments
Consul log
SystemD Log
The text was updated successfully, but these errors were encountered: