Guest

Preview Tool

Cisco Bug: CSCuw39671 - easOrch cores during emergency alert message delivery

Last Modified

Oct 01, 2015

Products (1)

  • Headend System Releases

Known Affected Releases

dncs-7.0.0.12p2

Description (partial)

Symptom:
Customer was sending various EAMs during an EAS test and easOrch cored which resulted in the lack of delivery of EAMs to all hubs.  The process ran for nearly a week and a half before the core and generated the following appcrash signature:
App_crash debugging report
Program: EASOrch
Process ID: 12425
Thread ID: 1
Received signal: 6

Application Debugging Data
--------------------------

> /usr/bin/pstack 12425
12425:  /dvs/dncs/bin/EASOrch
-----------------  lwp# 1 / thread# 1  --------------------
 fb79c955 _lwp_kill (1, 6) + 15
 fb743893 raise    (6) + 1f
 fbad6069 umem_do_abort (0, fbaf6000, 8045b94, fbad7e66, fbae35ac, fbafab90) + 25
 fbad6199 umem_err_recoverable (fbae35ac, fbafab90, 84bbe14, fbae35b8) + 46
 fbad7e66 process_free (84bbe14, 1, 0, 8045be8, fb875c8a, 84bbe14) + 82
 fbad7f0c free     (84bbe14, fc5e9258, 8045c08, fb875c72) + 15
 fb875c8a __1c2k6Fpv_v_ (84bbe14, 82001cc, 81f51cc, fba93afe) + 26
 fba93b18 __1cHRWSlistEpeel6FpnIRWPSlink__pv_ (84bbe14, 84bbe10, 8000000, fc695c9d) + 24
 fc6962d0 __1cOApiDefaultBaseW_processQdDueuedRequests6M_v_ (84bbde0, 84f1940, 85df560, fd1bd9c5) + 644
 fd1bee02 __1cKApiHandler4nOQdDpskManagerApi_nVQdDPSK_MANAGER_SEND_MSG_ncECaller_DNCS_QdDPSK_MANAGER_PROG_DNCS_QdDPSK_MANAGER_PROG_VER_nHXaction_nIFunctor24CrknJRPC_Xport_Cpn0D___n0D__J_callback6M2rk3_v_ (84a9720, 8046250, 8046260, fc5e9258) + 144e
 fd1bbd50 __1cRMemberTranslator24nKApiHandler4nOQdDpskManagerApi_nVQdDPSK_MANAGER_SEND_MSG_ncECaller_DNCS_QdDPSK_MANAGER_PROG_DNCS_QdDPSK_MANAGER_PROG_VER_nHXaction_nIFunctor24CrknJRPC_Xport_Cpn0D___n0D___C2Crk3_Fthunk6FrknLFunctorBase_26_v_ (82ce400, 8046250, 8046260, fd1c3046) + 28
 fd1c31ee __1cRLocRemoteFunctor24nJRPC_Xport_nHXaction__Hinvoke26MpnLRPC_SvcCall_rknIStreamed_5_v_ (82ce3d8, 85cdbf0, 8376128, 83768b8) + 1b6
 fc69e312 __1cQLocRemoteFunctorHInvoke26FpnLRPC_SvcCall_LrknIStreamed_5_v_ (85cdbf0, 3, 8376128, 83768b8) + 2be
 fc69f666 __1cKcheckQdDueue6F_v_ (0, fbd02a40, fb800000, 8046458, fb789900, fb440040) + e2
 fc6a0f6d __1cVLocRemoteFunctorTimerNtimerCallback6MpnFTimer__v_ (fc7545e8, fc75460c, 80, 2d) + 19
 fc700405 __1cFTimerHtimeout6F_v_ (80465c0, fc5a3438, 80465c0, fc5c53f6, 804668c, fc591d9c) + 681
 fc6b627e __1cHMonitorMprocessEvent6M_v_ (82acf48, fc72aa64, 8046828, fc6b63d0) + c76
 fc6b6398 __1cHMonitorJ_mainLoop6M_v_ (82acf48, 81fe1cc, 81d5a08, fc6b62bc) + bc
 fc6b62d3 __1cHMonitorImainLoop6M_v_ (82acf48, 81d5a38, 8046938, 81584b1) + 23
 081584ba main     (1, 8046964, 804696c, 8081b38) + 2e6
 08081c6d _start   (1, 8046ccc, 0, 8046ce2, 8046cfa, 8046d0f) + 7d

Conditions:
The customer was using Canadian EAS via an ECS 2.0 and an EC 7.0.0.12p2.  The issue could not be reproduced by the customer.
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.