Cisco Bug: CSCuq05597 - CRIT messages stacktrace should be renamed to something less alarming
Jun 16, 2015
- Cisco Application Policy Infrastructure Controller (APIC)
Known Affected Releases
Symptom: Some syslog error messages may produce a list of memory addresses to indicate which path through the source code was followed to get to that error. Along with those memory addresses is a references to a "Stack trace" and a CRIT message which has the connotation that a process may have unexpectedly restarted. Conditions: This occurs if a severe or critical error occurs but no process has unexpectedly restarted.
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)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases