Guest

Preview Tool

Cisco Bug: CSCvh99413 - consul-template could not connect to syslog service at start

Last Modified

Apr 13, 2019

Products (1)

  • Cisco Content Delivery Engine Series

Known Affected Releases

3.14(8) 3.18(2) 3.19(0)

Description (partial)

Symptom:
The 'monit' daemon is supposed to restart consul-template, but failed to do so. Using a process 'name' match instead of a pidfile match may work better. We did see a case where the process id in the pidfile was not running, but monit still failed to restart consul-template ? just changing the monitrc might not fix this.

The end result was client errors.

Conditions:
This could occur during startup.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.