Consul: Consul fails to start with Unix syslog delivery error

[ChrisAubuchon]

Seeing this error occasionally starting consul:

consul: ==> Syslog setup failed: Unix syslog delivery error

This is with consul 0.6.1.

[micahlmartin]

:+1: Same here

[slackpad]

Need to think about the right solution for this one - maybe just a brief waiting period with a backoff?

[looprock]

I'm starting to see this too on several systems. Are there any work-arounds?

[looprock]

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.

[evan2645]

Hit this problem with 0.6.3 today. Consul stop/start recovered it

ubuntu 14.04

[lin-zhao]

Hitting this with 0.6.3. rsyslog is actually running on port 514.

Reproduced on CentOS 7.2

[evan2645]

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

[gsy]

Same problem with 0.6.3. restart rsyslog and then restart consul make it work

[grindthemall]

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?

[falzm]

Can this bug please get some attention? It's _really_ annoying.

[kyhavlov]

Fixed with #2455