Guest

Preview Tool

Cisco Bug: CSCus12280 - syslog-ng fails to start after upgrade to XC2.4.1

Last Modified

Jun 08, 2015

Products (2)

  • Cisco TelePresence Conductor
  • Cisco TelePresence Conductor Model

Known Affected Releases

XC2.4.1

Description (partial)

Symptom:
Reported behaviours include "Invalid Cookie" reports when trying to connect to the admin GUI and loss of service on the system. Also, system log files do not get updated and /tmp directory gains syslogd_startup.lst file. /tmp directory may be 100% full.

Conditions:
This issue affects Conductor software versions greater that XC2.3. (I.e. XC2.4 and above.) It will manifest on upgrade to affected versions as well as re-starts if the conditions are met.

If the system is re-started and the name configured in one of the Remote syslog server fields in the Logging setting cannot be resolved, i.e.:
 - The FQDN is garbage
 - The DNS service is not replying

Then the syslog service will not start. In turn, this impacts the internal logging service and causes /tmp directory to fill up which can cause other services to fail.
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.