Cisco Bug: CSCuo85999 - earsRemote constantly coring on RF+IP 55-1 RNCS fl22.214.171.124
Jun 22, 2020
- Headend System Releases
Known Affected Releases
Symptom: The earsRemote process is constantly coring on an RF+IP 55-1 RNCS. Observed on fl126.96.36.199. Native EAS support is disabled on the ISDS associated with the RNCS. Over time the /disk2/ file system fills up with earsRemote core files. Potential start of the constant core state, from the /var/log/dncsLog file: May 15 11:39:56 jklionn APPCRASH: [ID 702911 local7.error] earsRemote 29975 received signal 11 on thread 5: info to /dvs/lionn/tmp/corefiles/earsRemote/appcrash.coreinfo.earsRemote.29975.20140515113956 May 15 11:40:01 jklionn lionnInitd: [ID 518134 local7.info] 05/15/2014 11:40:01.446|589/12|SYSLOG|libdncsInit:DncsProcessStatusMgr.C(469)|Program earsRemote(117), pid has exited. May 15 11:40:01 jklionn lionnInitd: [ID 486315 local7.error] 05/15/2014 11:40:01.583|589/14|ERROR|libdncsInit:Proc.C(420)|proc::startProcess(), max attempts reached, earsRemote 99/99 process going to error state. May 15 12:00:04 jklionn manage_dncsLog: [ID 702911 local7.error] Removed unused lock: earsRemote (14928) @ Thu May 15 11:30:00 2014 May 15 12:00:04 jklionn manage_dncsLog: [ID 702911 local7.error] Removed unused lock: earsRemote (16060) @ Thu May 15 11:30:08 2014 Conditions: Default state of the RNCS with Native EAS support disabled on the ISDS.
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