The assert at 08:19:53 has nothing todo with the CCB. This is the periodic warm 
sync where amfd just checks the counters of async updates. So the problem is 
introduced at 08:18:58 and _detected_ at 08:19:53

And the extracts from the core dump looks like:

~~~~~~
#3 0x0000000000411acc in avsv_decode_warm_sync_rsp (cb=0x69b9a0, 
    dec=<value optimized out>) at avd_ckpt_dec.c:3163 
        status = 2 
        updt_cnt = <value optimized out> 
        dec_updt_cnt = {cb_updt = 3, node_updt = 483, app_updt = 15, 
          sg_updt = 87, su_updt = 153, si_updt = 69, sg_su_oprlist_updt = 37, 
          sg_admin_si_updt = 0, siass_updt = 37, comp_updt = 493, 
          csi_updt = 0, compcstype_updt = 0, si_trans_updt = 0} 
        ederror = 4294901760 
        __FUNCTION__ = "avsv_decode_warm_sync_rsp" 

(gdb) print cb->async_updt_cnt 
$2 = {cb_updt = 3, node_updt = 483, app_updt = 15, sg_updt = 87, 
  su_updt = 153, si_updt = 69, sg_su_oprlist_updt = 37, sg_admin_si_updt = 0, 
  siass_updt = 37, comp_updt = 492, csi_updt = 0, compcstype_updt = 0, 
  si_trans_updt = 0} 

~~~~~~

so here you can see that the comp_updt is one less than expected which was 
introcuded at 08:18:58


---

** [tickets:#761] osafamfd[15184]: avd_ckpt_dec.c:3163: 
avsv_decode_warm_sync_rsp: Assertion '0' failed. **

**Status:** unassigned
**Created:** Fri Jan 31, 2014 10:20 AM UTC by Hans Feldt
**Last Updated:** Fri Jan 31, 2014 11:51 AM UTC
**Owner:** nobody

Jan 30 08:18:58 notice sc-2 osafimmnd[15044]: Ccb 214 COMMITTED (SMFSERVICE)
Jan 30 08:18:58 err sc-2 osafamfd[15184]: avsv_decode_ckpt_comp_oper_state: 
comp not found, safComp=XXX-CompType-1,safSu=XXX-SuType-1,safSg=
Jan 30 08:18:58 notice sc-2 osafimmnd[15044]: Ccb 215 COMMITTED (SMFSERVICE)
<snip>
Jan 30 08:19:53 err sc2 osafamfd[15184]: avd_ckpt_dec.c:3163: 
avsv_decode_warm_sync_rsp: Assertion '0' failed.

CCB 214 creates "safComp=XXX-CompType-1,safSu=XXX-SuType-1,safSg=..." which can 
be seen in system stream:

1158 08:18:58 01/30/2014 NO safApp=safAmfService "CCB 214 Created 
safComp=XXX-CompType-1,safSu=XXX-SuType-1,safSg=


This seems to be a timing/race problem and a similar one is reported and fixed 
in: http://devel.opensaf.org/ticket/2337

The same type of solution can be applied for comp. At least as a quick bugfix. 
A different long term should be discussed because the current applier usage is 
obviously not working out well for AMF.



---

Sent from sourceforge.net because [email protected] is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
WatchGuard Dimension instantly turns raw network data into actionable 
security intelligence. It gives you real-time visual feedback on key
security issues and trends.  Skip the complicated setup - simply import
a virtual appliance and go from zero to informed in seconds.
http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to