- **status**: unassigned --> not-reproducible
- **assigned_to**: Nagendra Kumar
- **Milestone**: future --> never
- **Comment**:
Fixed now.
---
** [tickets:#396] amfnd crashed when SaAmfCompCsType is not defined for SU**
**Status:** not-reproducible
**Milestone:** never
**Created:** Fri May 31, 2013 05:16 AM UTC by Nagendra Kumar
**Last Updated:** Fri May 31, 2013 05:16 AM UTC
**Owner:** Nagendra Kumar
Migrated from http://devel.opensaf.org/ticket/2603
Setup: 1 controller
changeset : 3407
Model : NWayActive
Configuration : 1App, 1SG,5SUs with 2comps each, 3Sis with 2csis each.
In the configuration, if SaAmfCompCsType? class is not defined for SU4, amfd
crashed while unlock-in and unlock of the SU4.
/var/log/messages:
--------------------------------------------------------------------------------
nce State INSTANTIATING => INSTANTIATED
Mar 27 18:05:45 SLES11-SLOT-2 osafamfd[6314]: avd_new_assgn_susi: Component
type missing for SU
'safSu=NWayActiveXApp_SU_4,safSg=NWayActiveXApp_SG,safApp=NWayActiveXApp'
Mar 27 18:05:45 SLES11-SLOT-2 osafamfd[6314]: avd_new_assgn_susi: Component
type missing for CSI
'safCsi=NWayActiveXApp_csi,safSi=NWayActiveXApp_SI3,safApp=NWayActiveXApp'
Mar 27 18:05:45 SLES11-SLOT-2 osafamfd[6314]: avd_new_assgn_susi: Component
type missing for SU
'safSu=NWayActiveXApp_SU_4,safSg=NWayActiveXApp_SG,safApp=NWayActiveXApp'
Mar 27 18:05:45 SLES11-SLOT-2 osafamfd[6314]: avd_new_assgn_susi: Component
type missing for CSI
'safCsi=NWayActiveXApp_csi1,safSi=NWayActiveXApp_SI3,safApp=NWayActiveXApp'
Mar 27 18:05:45 SLES11-SLOT-2 osafamfnd[6324]: Assigning
'safSi=NWayActiveXApp_SI3,safApp=NWayActiveXApp' ACTIVE to
'safSu=NWayActiveXApp_SU_4,safSg=NWayActiveXApp_SG,safApp=NWayActiveXApp'
Mar 27 18:05:45 SLES11-SLOT-2 kernel: osafamfnd[6324]: segfault at 21c ip
0808c4ae sp bfdd1dd0 error 4 in osafamfnd[8048000+5f000]
Gdb output:
--------------------------------------------------------------------------------
(gdb) bt
#0 0x0808c4ae in assign_si_to_su (si=0x80ca0c8, su=0x80c7a80, single_csi=1) at
avnd_susm.c:460
#1 0x0808c9fb in avnd_su_si_assign (cb=0x80aa9a0, su=0x80c7a80, si=0x80ca0c8)
at avnd_susm.c:612
#2 0x0808c087 in avnd_su_si_msg_prc (cb=0x80aa9a0, su=0x80c7a80,
info=0x80c405c) at avnd_susm.c:352
#3 0x0808a8b4 in avnd_evt_avd_info_su_si_assign_evh (cb=0x80aa9a0,
evt=0x80b8030) at avnd_su.c:284
#4 0x08087f98 in avnd_evt_process (evt=0x80b8030) at avnd_proc.c:279
#5 0x08087da3 in avnd_main_process () at avnd_proc.c:220
#6 0x0804ff61 in main (argc=Cannot access memory at address 0x2
) at amfnd_main.c:45
(gdb) bt full
#0 0x0808c4ae in assign_si_to_su (si=0x80ca0c8, su=0x80c7a80, single_csi=1) at
avnd_susm.c:460
rank = 134914036
rc = 1
curr_csi = (AVND_COMP_CSI_REC *) 0x0
FUNCTION = "assign_si_to_su"
#1 0x0808c9fb in avnd_su_si_assign (cb=0x80aa9a0, su=0x80c7a80, si=0x80ca0c8)
at avnd_susm.c:612
rc = 1
rank = 1
curr_si = (AVND_SU_SI_REC *) 0x80a9ff4
curr_csi = (AVND_COMP_CSI_REC *) 0x1
FUNCTION = "avnd_su_si_assign"
#2 0x0808c087 in avnd_su_si_msg_prc (cb=0x80aa9a0, su=0x80c7a80,
info=0x80c405c) at avnd_susm.c:352
si = (AVND_SU_SI_REC *) 0x80ca0c8
rc = 1
csi = (AVND_COMP_CSI_REC *) 0x0
FUNCTION = "avnd_su_si_msg_prc"
#3 0x0808a8b4 in avnd_evt_avd_info_su_si_assign_evh (cb=0x80aa9a0,
evt=0x80b8030) at avnd_su.c:284
info = (AVSV_D2N_INFO_SU_SI_ASSIGN_MSG_INFO *) 0x80c405c
siq = (AVND_SU_SIQ_REC *) 0x0
su = (AVND_SU *) 0x80c7a80
rc = 1
FUNCTION = "avnd_evt_avd_info_su_si_assign_evh"
#4 0x08087f98 in avnd_evt_process (evt=0x80b8030) at avnd_proc.c:279
cb = (AVND_CB *) 0x80aa9a0
rc = 1
FUNCTION = "avnd_evt_process"
#5 0x08087da3 in avnd_main_process () at avnd_proc.c:220
ret = 1
mbx_fd = {raise_obj = 11, rmv_obj = 12}
fds = {{fd = 12, events = 1, revents = 1}, {fd = 16, events = 1, revents = 0},
{fd = 14, events = 1, revents = 0}, {
fd = -1076027400, events = -405, revents = 2052}}
nfds = 3
evt = (AVND_EVT *) 0x80b8030
FUNCTION = "avnd_main_process"
#6 0x0804ff61 in main (argc=Cannot access memory at address 0x2
Changed 14 months ago by hafe ¶
I think 2603, 2120 & 2083 are the same problem. AMFD allows invalid (or?)
configuration to come into the model and amfnd gets into problems. It is
obvious from the logs:
Mar 27 18:05:45 SLES11-SLOT-2 osafamfd[6314]: avd_new_assgn_susi: Component
type missing for SU
'safSu=NWayActiveXApp_SU_4,safSg=NWayActiveXApp_SG,safApp=NWayActiveXApp'
After logging what is missing the function could just return an error code I
guess instead of sending a message to amfnd which then will crash.
Changed 14 months ago by hafe ¶
■priority changed from critical to major
2120 & 2083 are not critical. This is not stopping anyone from using opensaf
---
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.------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
