-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consul fails to start with Unix syslog delivery error #1610
Comments
👍 Same here |
Need to think about the right solution for this one - maybe just a brief waiting period with a backoff? |
I'm starting to see this too on several systems. Are there any work-arounds? |
Interestingly, even when I roll back to 0.5.2, I still have the same issue. I even tried force-leaving the node and purging the data directory. |
Hit this problem with 0.6.3 today. Consul stop/start recovered it ubuntu 14.04 |
Hitting this with 0.6.3. rsyslog is actually running on port 514. Reproduced on CentOS 7.2 |
present in 0.6.4 also. got to a spot where this was occurring every time a host was rebooted. worked around with aggressive respawn in upstart |
Same problem with 0.6.3. restart rsyslog and then restart consul make it work |
Just hit this one today - running Centos 7.2, Rsyslog 8.10 and Consul .7. Had to restart to enable an option, and it wouldn't restart with the message: ==> Syslog setup failed: Unix syslog delivery error My systemd file already tries to auto-restart it quickly, but it does not matter. I have one node now that I cannot get to run consul. Suggestions? |
Can this bug please get some attention? It's really annoying. |
Fixed with #2455 |
Seeing this error occasionally starting consul:
This is with consul 0.6.1.
The text was updated successfully, but these errors were encountered: