[tickets] [opensaf:tickets] #981 smf: set DN maxlength depending on if extended DNs is enabled globally or not
- **Comment**: Direct use of "kMaxDnLength" constant shall be removed and shall be used only in 1 place in SMF code. Instead of checking the max allowed DN length directly against "kMaxDnLength", the value will be read from a newly introduced variable ("maxDnLength") from "smfd_cb" control block structure. A method will be implemented to read if long DNs enabled in IMM. That method will store the config in SMF control block. --- ** [tickets:#981] smf: set DN maxlength depending on if extended DNs is enabled globally or not** **Status:** assigned **Milestone:** 4.5.0 **Created:** Mon Aug 11, 2014 11:37 AM UTC by Ingvar Bergström **Last Updated:** Mon Aug 11, 2014 11:37 AM UTC **Owner:** Robert Apanowicz Instead of using kMaxDnLength directly, we should actually have a variable that is initialized to either kMaxDnLength or 255, depending on if extended DNs is enabled globally or not (which can be checked by reading the attribute longDnsAllowed in opensafImm=opensafImm,safApp=safImmService) --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.-- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1024 mds access control : imma is not able to connect to immnd after immnd restart
- **status**: unassigned --> accepted --- ** [tickets:#1024] mds access control : imma is not able to connect to immnd after immnd restart** **Status:** accepted **Milestone:** 4.5.0 **Created:** Wed Aug 27, 2014 02:28 PM UTC by Neelakanta Reddy **Last Updated:** Thu Aug 28, 2014 04:15 PM UTC **Owner:** Hans Feldt syslog: --- Aug 27 16:40:07 SLES-SLOT-1 osafamfnd[31322]: NO Restarting a component of 'safSu=SC-1,safSg=NoRed,safApp=OpenSAF' (comp restart count: 9) Aug 27 16:40:07 SLES-SLOT-1 osafamfnd[31322]: NO 'safComp=IMMND,safSu=SC-1,safSg=NoRed,safApp=OpenSAF' faulted due to 'avaDown' : Recovery is 'componentRestart' Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: Started Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: NO Persistent Back-End capability configured, Pbe file:imm.db (suffix may get added) Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: NO SERVER STATE: IMM_SERVER_ANONYMOUS --> IMM_SERVER_CLUSTER_WAITING Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: NO Fevs count adjusted to 6538 preLoadPid: 0 Aug 27 16:40:07 SLES-SLOT-1 osafimmd[31246]: NO New IMMND process is on ACTIVE Controller at 2010f Aug 27 16:40:07 SLES-SLOT-1 osafimmd[31246]: NO Extended intro from node 2010f Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: NO SERVER STATE: IMM_SERVER_CLUSTER_WAITING --> IMM_SERVER_LOADING_PENDING Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: NO SERVER STATE: IMM_SERVER_LOADING_PENDING --> IMM_SERVER_SYNC_PENDING Aug 27 16:40:07 SLES-SLOT-1 osafimmd[31246]: WA IMMND on controller (not currently coord) requests sync Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: NO NODE STATE-> IMM_NODE_ISOLATED Aug 27 16:40:07 SLES-SLOT-1 osafimmd[31246]: NO Node 2010f request sync sync-pid:2570 epoch:0 Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: NO NODE STATE-> IMM_NODE_W_AVAILABLE Aug 27 16:40:07 SLES-SLOT-1 osafimmd[31246]: NO Successfully announced sync. New ruling epoch:27 Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO SERVER STATE: IMM_SERVER_SYNC_PENDING --> IMM_SERVER_SYNC_CLIENT Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO NODE STATE-> IMM_NODE_FULLY_AVAILABLE 2460 Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO RepositoryInitModeT is SA_IMM_KEEP_REPOSITORY Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: WA IMM Access Control mode is DISABLED! Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Epoch set to 27 in ImmModel Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO SERVER STATE: IMM_SERVER_SYNC_CLIENT --> IMM SERVER READY Aug 27 16:40:08 SLES-SLOT-1 osafimmd[31246]: NO ACT: New Epoch for IMMND process at node 2010f old epoch: 0 new epoch:27 Aug 27 16:40:08 SLES-SLOT-1 osafimmd[31246]: NO ACT: New Epoch for IMMND process at node 2030f old epoch: 26 new epoch:27 Aug 27 16:40:08 SLES-SLOT-1 osafimmd[31246]: NO ACT: New Epoch for IMMND process at node 2040f old epoch: 26 new epoch:27 Aug 27 16:40:08 SLES-SLOT-1 osafimmd[31246]: NO ACT: New Epoch for IMMND process at node 2020f old epoch: 26 new epoch:27 Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 213 (safLogService) <4, 2010f> Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 214 (safClmService) <13, 2010f> Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 215 (MsgQueueService131343) <300, 2010f> Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 216 (safLckService) <302, 2010f> Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 217 (safEvtService) <303, 2010f> Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 218 (safCheckPointService) <304, 2010f> Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 219 (safSmfService) <305, 2010f> Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO PBE-OI established on other SC. Dumping incrementally to file imm.db Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 220 (safAmfService) <18, 2010f> Aug 27 16:40:12 SLES-SLOT-1 osafimmnd[2570]: WA immnd_evt_proc_imm_init: PID 0 (1556) for 2010f4073a040, MDS problem? Aug 27 16:40:12 SLES-SLOT-1 osafimmnd[2570]: WA immnd_evt_proc_imm_init: PID 0 (1556) for 2010f4073a040, MDS problem? Aug 27 16:40:12 SLES-SLOT-1 osafimmnd[2570]: WA immnd_evt_proc_imm_init: PID 0 (1556) for 2010f4073a040, MDS problem? Aug 27 16:40:12 SLES-SLOT-1 osafimmnd[2570]: WA immnd_evt_proc_imm_init: PID 0 (1556) for 2010f4073a040, MDS problem? IMMA traces: Aug 27 16:40:06.872446 imma [1556:imma_om_api.c:0151] >> saImmOmInitialize Aug 27 16:40:06.872615 imma [1556:imma_om_api.c:0177] TR OM client version A.2.14 Aug 27 16:40:06.872662 imma [1556:imma_om_api.c:0210] >> initialize_common Aug 27 16:40:06.872687 imma [1556:imma_init.c:0273] >> imma_startup: use count 1 Aug 27 16:40:06.872709 imma [1556:imma_init.c:0296] << imma_startup: use count 2 Aug 27 16:40:06.874390 imma [1556:imma_proc.c:0147] >> imma_callback_ipc_destroy Aug 27 16:40:06.875905 imma [1556:imma_init.c:0333] >> imma_shutdown: use c
[tickets] [opensaf:tickets] #1032 immomtest fails on 4.5
--- ** [tickets:#1032] immomtest fails on 4.5** **Status:** unassigned **Milestone:** 4.5.0 **Created:** Fri Aug 29, 2014 05:57 AM UTC by Hans Feldt **Last Updated:** Fri Aug 29, 2014 05:57 AM UTC **Owner:** nobody a test case check number of attributes in the imm opensaf service class which has now changed from 6 to 8 --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.-- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1032 immomtest fails on 4.5
- **Priority**: major --> minor --- ** [tickets:#1032] immomtest fails on 4.5** **Status:** unassigned **Milestone:** 4.5.0 **Created:** Fri Aug 29, 2014 05:57 AM UTC by Hans Feldt **Last Updated:** Fri Aug 29, 2014 05:57 AM UTC **Owner:** nobody a test case check number of attributes in the imm opensaf service class which has now changed from 6 to 8 --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.-- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1031 PLM: active controller HE resets itself when first instantiating its EE
- **status**: accepted --> review --- ** [tickets:#1031] PLM: active controller HE resets itself when first instantiating its EE** **Status:** review **Milestone:** 4.5.0 **Created:** Thu Aug 28, 2014 07:32 PM UTC by Alex Jones **Last Updated:** Thu Aug 28, 2014 07:32 PM UTC **Owner:** Alex Jones plms_ee_instantiate() resets the HE to which the EE belongs. But, this function is only called if there are dependencies on the HE. It is never called if there are no dependencies. If the active controller blade (modeled as an HE) has HE dependencies (some other FRUs on the board), this blade/HE will only be brought in-service when the other HEs on which it depends are brought in-service. At this point, plms_ee_instantiate() is called and the controller ends up resetting itself. This is not good! plms_ent_enable() is called in plms_move_dep_ent_to_insvc(). This function, plms_ent_enable(), is not called if there are no dependencies, and hardware is not inserted into the chassis. If the hardware is already present, and there are no dependencies, plms_ent_enable() is not called, which means plms_ee_instantiate is not called. If the active controller blade/HE does not depend on any other HEs, plms_ee_instantiate is never called, and so the blade can never reset itself. In plms_ee_instantiate() we probably need to check whether or not we are about to reset ourself, and not do it. We can safely assume that the EE is already running (since our code is executing!), and that plmcd will communicate with PLMS to set the EE states. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.-- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1031 PLM: active controller HE resets itself when first instantiating its EE
--- ** [tickets:#1031] PLM: active controller HE resets itself when first instantiating its EE** **Status:** accepted **Milestone:** 4.5.0 **Created:** Thu Aug 28, 2014 07:32 PM UTC by Alex Jones **Last Updated:** Thu Aug 28, 2014 07:32 PM UTC **Owner:** Alex Jones plms_ee_instantiate() resets the HE to which the EE belongs. But, this function is only called if there are dependencies on the HE. It is never called if there are no dependencies. If the active controller blade (modeled as an HE) has HE dependencies (some other FRUs on the board), this blade/HE will only be brought in-service when the other HEs on which it depends are brought in-service. At this point, plms_ee_instantiate() is called and the controller ends up resetting itself. This is not good! plms_ent_enable() is called in plms_move_dep_ent_to_insvc(). This function, plms_ent_enable(), is not called if there are no dependencies, and hardware is not inserted into the chassis. If the hardware is already present, and there are no dependencies, plms_ent_enable() is not called, which means plms_ee_instantiate is not called. If the active controller blade/HE does not depend on any other HEs, plms_ee_instantiate is never called, and so the blade can never reset itself. In plms_ee_instantiate() we probably need to check whether or not we are about to reset ourself, and not do it. We can safely assume that the EE is already running (since our code is executing!), and that plmcd will communicate with PLMS to set the EE states. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.-- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1024 mds access control : imma is not able to connect to immnd after immnd restart
Also to make immomtest work again: diff --git a/tests/immsv/management/test_saImmOmAccessorGet_2.c b/tests/immsv/management/test_saImmOmAccessorGet_2.c --- a/tests/immsv/management/test_saImmOmAccessorGet_2.c +++ b/tests/immsv/management/test_saImmOmAccessorGet_2.c @@ -133,7 +133,7 @@ void saImmOmAccessorGet_2_04(void) rc = saImmOmAccessorGet_2(accessorHandle, &objectName, accessorGetConfigAttrsToken, &attributes); /* Verify the number of config attributes */ cnt = print_SaImmAttrValuesT_2(attributes); -assert(cnt == 6); +assert(cnt == 8); test_validate(rc, SA_AIS_OK); safassert(saImmOmFinalize(immOmHandle), SA_AIS_OK); } --- ** [tickets:#1024] mds access control : imma is not able to connect to immnd after immnd restart** **Status:** unassigned **Milestone:** 4.5.0 **Created:** Wed Aug 27, 2014 02:28 PM UTC by Neelakanta Reddy **Last Updated:** Thu Aug 28, 2014 04:14 PM UTC **Owner:** Hans Feldt syslog: --- Aug 27 16:40:07 SLES-SLOT-1 osafamfnd[31322]: NO Restarting a component of 'safSu=SC-1,safSg=NoRed,safApp=OpenSAF' (comp restart count: 9) Aug 27 16:40:07 SLES-SLOT-1 osafamfnd[31322]: NO 'safComp=IMMND,safSu=SC-1,safSg=NoRed,safApp=OpenSAF' faulted due to 'avaDown' : Recovery is 'componentRestart' Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: Started Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: NO Persistent Back-End capability configured, Pbe file:imm.db (suffix may get added) Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: NO SERVER STATE: IMM_SERVER_ANONYMOUS --> IMM_SERVER_CLUSTER_WAITING Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: NO Fevs count adjusted to 6538 preLoadPid: 0 Aug 27 16:40:07 SLES-SLOT-1 osafimmd[31246]: NO New IMMND process is on ACTIVE Controller at 2010f Aug 27 16:40:07 SLES-SLOT-1 osafimmd[31246]: NO Extended intro from node 2010f Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: NO SERVER STATE: IMM_SERVER_CLUSTER_WAITING --> IMM_SERVER_LOADING_PENDING Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: NO SERVER STATE: IMM_SERVER_LOADING_PENDING --> IMM_SERVER_SYNC_PENDING Aug 27 16:40:07 SLES-SLOT-1 osafimmd[31246]: WA IMMND on controller (not currently coord) requests sync Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: NO NODE STATE-> IMM_NODE_ISOLATED Aug 27 16:40:07 SLES-SLOT-1 osafimmd[31246]: NO Node 2010f request sync sync-pid:2570 epoch:0 Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: NO NODE STATE-> IMM_NODE_W_AVAILABLE Aug 27 16:40:07 SLES-SLOT-1 osafimmd[31246]: NO Successfully announced sync. New ruling epoch:27 Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO SERVER STATE: IMM_SERVER_SYNC_PENDING --> IMM_SERVER_SYNC_CLIENT Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO NODE STATE-> IMM_NODE_FULLY_AVAILABLE 2460 Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO RepositoryInitModeT is SA_IMM_KEEP_REPOSITORY Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: WA IMM Access Control mode is DISABLED! Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Epoch set to 27 in ImmModel Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO SERVER STATE: IMM_SERVER_SYNC_CLIENT --> IMM SERVER READY Aug 27 16:40:08 SLES-SLOT-1 osafimmd[31246]: NO ACT: New Epoch for IMMND process at node 2010f old epoch: 0 new epoch:27 Aug 27 16:40:08 SLES-SLOT-1 osafimmd[31246]: NO ACT: New Epoch for IMMND process at node 2030f old epoch: 26 new epoch:27 Aug 27 16:40:08 SLES-SLOT-1 osafimmd[31246]: NO ACT: New Epoch for IMMND process at node 2040f old epoch: 26 new epoch:27 Aug 27 16:40:08 SLES-SLOT-1 osafimmd[31246]: NO ACT: New Epoch for IMMND process at node 2020f old epoch: 26 new epoch:27 Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 213 (safLogService) <4, 2010f> Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 214 (safClmService) <13, 2010f> Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 215 (MsgQueueService131343) <300, 2010f> Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 216 (safLckService) <302, 2010f> Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 217 (safEvtService) <303, 2010f> Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 218 (safCheckPointService) <304, 2010f> Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 219 (safSmfService) <305, 2010f> Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO PBE-OI established on other SC. Dumping incrementally to file imm.db Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 220 (safAmfService) <18, 2010f> Aug 27 16:40:12 SLES-SLOT-1 osafimmnd[2570]: WA immnd_evt_proc_imm_init: PID 0 (1556) for 2010f4073a040, MDS problem? Aug 27 16:40:12 SLES-SLOT-1 osafimmnd[2570]: WA immnd_evt_proc_imm_init: PID 0 (1556) for 2010f4073a040, MDS problem? Aug 27 16:40:12 SLES-SLOT-1 osafimmnd[2570]: WA immnd_evt_proc_imm_init: PID 0 (1556) for 2010f4073a040, MDS problem? Aug 27 16:40:12 SLES-SLOT-1 osafimmnd[2570]: WA immnd_evt_proc_imm_
[tickets] [opensaf:tickets] #1024 mds access control : imma is not able to connect to immnd after immnd restart
Please try these patches Attachment: imma-1024 (4.0 kB; application/octet-stream) mds-1024 (6.3 kB; application/octet-stream) --- ** [tickets:#1024] mds access control : imma is not able to connect to immnd after immnd restart** **Status:** unassigned **Milestone:** 4.5.0 **Created:** Wed Aug 27, 2014 02:28 PM UTC by Neelakanta Reddy **Last Updated:** Thu Aug 28, 2014 02:14 PM UTC **Owner:** Hans Feldt syslog: --- Aug 27 16:40:07 SLES-SLOT-1 osafamfnd[31322]: NO Restarting a component of 'safSu=SC-1,safSg=NoRed,safApp=OpenSAF' (comp restart count: 9) Aug 27 16:40:07 SLES-SLOT-1 osafamfnd[31322]: NO 'safComp=IMMND,safSu=SC-1,safSg=NoRed,safApp=OpenSAF' faulted due to 'avaDown' : Recovery is 'componentRestart' Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: Started Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: NO Persistent Back-End capability configured, Pbe file:imm.db (suffix may get added) Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: NO SERVER STATE: IMM_SERVER_ANONYMOUS --> IMM_SERVER_CLUSTER_WAITING Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: NO Fevs count adjusted to 6538 preLoadPid: 0 Aug 27 16:40:07 SLES-SLOT-1 osafimmd[31246]: NO New IMMND process is on ACTIVE Controller at 2010f Aug 27 16:40:07 SLES-SLOT-1 osafimmd[31246]: NO Extended intro from node 2010f Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: NO SERVER STATE: IMM_SERVER_CLUSTER_WAITING --> IMM_SERVER_LOADING_PENDING Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: NO SERVER STATE: IMM_SERVER_LOADING_PENDING --> IMM_SERVER_SYNC_PENDING Aug 27 16:40:07 SLES-SLOT-1 osafimmd[31246]: WA IMMND on controller (not currently coord) requests sync Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: NO NODE STATE-> IMM_NODE_ISOLATED Aug 27 16:40:07 SLES-SLOT-1 osafimmd[31246]: NO Node 2010f request sync sync-pid:2570 epoch:0 Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: NO NODE STATE-> IMM_NODE_W_AVAILABLE Aug 27 16:40:07 SLES-SLOT-1 osafimmd[31246]: NO Successfully announced sync. New ruling epoch:27 Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO SERVER STATE: IMM_SERVER_SYNC_PENDING --> IMM_SERVER_SYNC_CLIENT Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO NODE STATE-> IMM_NODE_FULLY_AVAILABLE 2460 Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO RepositoryInitModeT is SA_IMM_KEEP_REPOSITORY Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: WA IMM Access Control mode is DISABLED! Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Epoch set to 27 in ImmModel Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO SERVER STATE: IMM_SERVER_SYNC_CLIENT --> IMM SERVER READY Aug 27 16:40:08 SLES-SLOT-1 osafimmd[31246]: NO ACT: New Epoch for IMMND process at node 2010f old epoch: 0 new epoch:27 Aug 27 16:40:08 SLES-SLOT-1 osafimmd[31246]: NO ACT: New Epoch for IMMND process at node 2030f old epoch: 26 new epoch:27 Aug 27 16:40:08 SLES-SLOT-1 osafimmd[31246]: NO ACT: New Epoch for IMMND process at node 2040f old epoch: 26 new epoch:27 Aug 27 16:40:08 SLES-SLOT-1 osafimmd[31246]: NO ACT: New Epoch for IMMND process at node 2020f old epoch: 26 new epoch:27 Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 213 (safLogService) <4, 2010f> Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 214 (safClmService) <13, 2010f> Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 215 (MsgQueueService131343) <300, 2010f> Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 216 (safLckService) <302, 2010f> Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 217 (safEvtService) <303, 2010f> Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 218 (safCheckPointService) <304, 2010f> Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 219 (safSmfService) <305, 2010f> Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO PBE-OI established on other SC. Dumping incrementally to file imm.db Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 220 (safAmfService) <18, 2010f> Aug 27 16:40:12 SLES-SLOT-1 osafimmnd[2570]: WA immnd_evt_proc_imm_init: PID 0 (1556) for 2010f4073a040, MDS problem? Aug 27 16:40:12 SLES-SLOT-1 osafimmnd[2570]: WA immnd_evt_proc_imm_init: PID 0 (1556) for 2010f4073a040, MDS problem? Aug 27 16:40:12 SLES-SLOT-1 osafimmnd[2570]: WA immnd_evt_proc_imm_init: PID 0 (1556) for 2010f4073a040, MDS problem? Aug 27 16:40:12 SLES-SLOT-1 osafimmnd[2570]: WA immnd_evt_proc_imm_init: PID 0 (1556) for 2010f4073a040, MDS problem? IMMA traces: Aug 27 16:40:06.872446 imma [1556:imma_om_api.c:0151] >> saImmOmInitialize Aug 27 16:40:06.872615 imma [1556:imma_om_api.c:0177] TR OM client version A.2.14 Aug 27 16:40:06.872662 imma [1556:imma_om_api.c:0210] >> initialize_common Aug 27 16:40:06.872687 imma [1556:imma_init.c:0273] >> imma_startup: use count 1 Aug 27 16:40:06.872709 imma [1556:imma_init.c:0296] << imma_startup: use count 2 Aug 27 16:40:06.874390 imma [1556:imma_proc.c:0147] >> imma_ca
[tickets] [opensaf:tickets] #1030 PLM: support dynamic changing of saPlmDependency attribute
--- ** [tickets:#1030] PLM: support dynamic changing of saPlmDependency attribute** **Status:** accepted **Milestone:** 4.6.FC **Created:** Thu Aug 28, 2014 03:37 PM UTC by Alex Jones **Last Updated:** Thu Aug 28, 2014 03:37 PM UTC **Owner:** Alex Jones Some hardware has a variable number of FRUs which can only be discovered at runtime. For example, suppose the hardware is a board with with multiple DSPs. The board is a FRU modeled as an HE, and the DSPs are also FRUs modeled as HEs. The DSP FRUs can range in number from 1-9. We want to be able to have the HE for the board depend on the DSP HEs on the board, so that if one DSP goes out of service, the board goes out of service. We need to support setting saPlmDependency attributes at runtime to handle configurations such as this. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.-- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #961 Imm: IMMND get restarted when opensafImmSyncBatchSize is modified when PBE is enabled
- **status**: review --> fixed - **Comment**: changeset: 5678:140afff1ad54 tag: tip parent: 5674:16ac76d90d44 user:Neelakanta Reddy date:Thu Aug 28 20:45:59 2014 +0530 summary: imm:corrected memory corruption problem when ccberrorstring is used in modify/create callback[#961] changeset: 5677:a4f4ea3de510 branch: opensaf-4.5.x parent: 5673:d0d52318ae9d user:Neelakanta Reddy date:Thu Aug 28 20:45:59 2014 +0530 summary: imm:corrected memory corruption problem when ccberrorstring is used in modify/create callback[#961] changeset: 5676:b4323e5bb190 branch: opensaf-4.4.x parent: 5665:f1e758139695 user:Neelakanta Reddy date:Thu Aug 28 20:45:59 2014 +0530 summary: imm:corrected memory corruption problem when ccberrorstring is used in modify/create callback[#961] changeset: 5675:a63c4a3e8635 branch: opensaf-4.3.x parent: 5652:4d5464122620 user:Neelakanta Reddy date:Thu Aug 28 20:45:59 2014 +0530 summary: imm:corrected memory corruption problem when ccberrorstring is used in modify/create callback[#961] --- ** [tickets:#961] Imm: IMMND get restarted when opensafImmSyncBatchSize is modified when PBE is enabled** **Status:** fixed **Milestone:** 4.3.3 **Created:** Wed Jul 16, 2014 07:18 AM UTC by Neelakanta Reddy **Last Updated:** Wed Aug 27, 2014 12:11 PM UTC **Owner:** Neelakanta Reddy Description of the ticket: 1. Opensaf is installed with 5465 changeset. 2. cluster services are started with PBE enable. 3. try to modify opensafImmSyncBatchSize immcfg -a opensafImmSyncBatchSize=547 opensafImm=opensafImm,safApp=safImmService IMMND get restarted: Jul 16 12:47:51 Slot-4 osafimmpbed: NO PBE will not allow modifications to object opensafImm=opensafImm,safApp=safImmService Jul 16 12:47:51 Slot-4 osafimmpbed: NO PBE will not allow modifications to object opensafImm=opensafImm,safApp=safImmService Jul 16 12:47:51 Slot-4 osafimmnd[28075]: WA immsv_evt_enc_inline_text: Length missmatch from source line:1093 (86 3882979160 'PBE will not allow modifications to object opensafImm=opensafImm,safApp=safImmService') Jul 16 12:47:51 Slot-4 osafimmnd[28075]: immsv_evt.c:1093: immsv_evt_enc_attrName: Assertion 'immsv_evt_enc_inline_text(__LINE__, o_ub, os)' failed. Jul 16 12:47:51 Slot-4 osafimmpbed: WA PBE lost contact with parent IMMND - Exiting Jul 16 12:47:51 Slot-4 osafamfnd[28169]: NO Restarting a component of 'safSu=SC-1,safSg=NoRed,safApp=OpenSAF' (comp restart count: 1) Jul 16 12:47:51 Slot-4 osafamfnd[28169]: NO 'safComp=IMMND,safSu=SC-1,safSg=NoRed,safApp=OpenSAF' faulted due to 'avaDown' : Recovery is 'componentRestart' --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.-- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1025 osafamfd crashed during restart failure
I meant to say "not sure". --- ** [tickets:#1025] osafamfd crashed during restart failure ** **Status:** unassigned **Milestone:** 4.3.3 **Created:** Wed Aug 27, 2014 05:31 PM UTC by KANG-SEN LU **Last Updated:** Thu Aug 28, 2014 03:02 PM UTC **Owner:** nobody We are running opensaf 4.4.0. Here is a gdb stack trace of osafamfd crash: == (gdb) bt 0 0x7f457067f425 in __GI_raise (sig=) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 1 0x7f4570682b8b in __GI_abort () at abort.c:91 2 0x7f4572105f21 in __osafassert_fail ( __file=0x448498 "/home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/di.cc", line=569, func=0x4488b0 "avnd_di_susi_resp_send", __assertion=0x44837a "m_AVND_SU_IS_ASSIGN_PEND(su)") at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/libs/core/leap/sysf_def.c:278 3 0x00427a42 in avnd_di_susi_resp_send (cb=cb@entry=0x65e4a0 <_avnd_cb>, su=su@entry=0x2444980, si=si@entry=0x2439720) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/di.cc:569 4 0x00438c21 in avnd_su_pres_st_chng_prc (final_st=SA_AMF_PRESENCE_INSTANTIATION_FAILED, prv_st=SA_AMF_PRESENCE_INSTANTIATED, su=0x2444980, cb=0x65e4a0 <_avnd_cb>) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/susm.cc:1608 5 avnd_su_pres_fsm_run (cb=cb@entry=0x65e4a0 <_avnd_cb>, su=0x2444980, comp=comp@entry=0x2444bb0, ev=) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/susm.cc:1394 6 0x004188b3 in avnd_comp_clc_st_chng_prc (cb=cb@entry=0x65e4a0 <_avnd_cb>, comp=comp@entry=0x2444bb0, prv_st=prv_st@entry=SA_AMF_PRESENCE_RESTARTING, final_st=final_st@entry=SA_AMF_PRESENCE_INSTANTIATION_FAILED) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/clc.cc:1298 7 0x0041a512 in avnd_comp_clc_fsm_run (cb=cb@entry=0x65e4a0 <_avnd_cb>, comp=comp@entry=0x2444bb0, ev=) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/clc.cc:862 8 0x0041aa39 in avnd_evt_clc_resp_evh (cb=0x65e4a0 <_avnd_cb>, evt=0x7f45640008c0) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/clc.cc:416 9 0x0042c23c in avnd_evt_process (evt=0x7f45640008c0) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/main.cc:678 10 avnd_main_process () at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/main.cc:619 11 0x00405328 in main (argc=1, argv=0x7fff7bcfc988) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/main.cc:178 (gdb) --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.-- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1025 osafamfd crashed during restart failure
I am sure what is "PI" vs "NPI". How do I find that info for you? --- ** [tickets:#1025] osafamfd crashed during restart failure ** **Status:** unassigned **Milestone:** 4.3.3 **Created:** Wed Aug 27, 2014 05:31 PM UTC by KANG-SEN LU **Last Updated:** Thu Aug 28, 2014 03:01 PM UTC **Owner:** nobody We are running opensaf 4.4.0. Here is a gdb stack trace of osafamfd crash: == (gdb) bt 0 0x7f457067f425 in __GI_raise (sig=) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 1 0x7f4570682b8b in __GI_abort () at abort.c:91 2 0x7f4572105f21 in __osafassert_fail ( __file=0x448498 "/home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/di.cc", line=569, func=0x4488b0 "avnd_di_susi_resp_send", __assertion=0x44837a "m_AVND_SU_IS_ASSIGN_PEND(su)") at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/libs/core/leap/sysf_def.c:278 3 0x00427a42 in avnd_di_susi_resp_send (cb=cb@entry=0x65e4a0 <_avnd_cb>, su=su@entry=0x2444980, si=si@entry=0x2439720) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/di.cc:569 4 0x00438c21 in avnd_su_pres_st_chng_prc (final_st=SA_AMF_PRESENCE_INSTANTIATION_FAILED, prv_st=SA_AMF_PRESENCE_INSTANTIATED, su=0x2444980, cb=0x65e4a0 <_avnd_cb>) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/susm.cc:1608 5 avnd_su_pres_fsm_run (cb=cb@entry=0x65e4a0 <_avnd_cb>, su=0x2444980, comp=comp@entry=0x2444bb0, ev=) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/susm.cc:1394 6 0x004188b3 in avnd_comp_clc_st_chng_prc (cb=cb@entry=0x65e4a0 <_avnd_cb>, comp=comp@entry=0x2444bb0, prv_st=prv_st@entry=SA_AMF_PRESENCE_RESTARTING, final_st=final_st@entry=SA_AMF_PRESENCE_INSTANTIATION_FAILED) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/clc.cc:1298 7 0x0041a512 in avnd_comp_clc_fsm_run (cb=cb@entry=0x65e4a0 <_avnd_cb>, comp=comp@entry=0x2444bb0, ev=) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/clc.cc:862 8 0x0041aa39 in avnd_evt_clc_resp_evh (cb=0x65e4a0 <_avnd_cb>, evt=0x7f45640008c0) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/clc.cc:416 9 0x0042c23c in avnd_evt_process (evt=0x7f45640008c0) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/main.cc:678 10 avnd_main_process () at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/main.cc:619 11 0x00405328 in main (argc=1, argv=0x7fff7bcfc988) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/main.cc:178 (gdb) --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.-- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1025 osafamfd crashed during restart failure
Thanks for the information. Is this Su a PI or NPI SU? --- ** [tickets:#1025] osafamfd crashed during restart failure ** **Status:** unassigned **Milestone:** 4.3.3 **Created:** Wed Aug 27, 2014 05:31 PM UTC by KANG-SEN LU **Last Updated:** Thu Aug 28, 2014 02:52 PM UTC **Owner:** nobody We are running opensaf 4.4.0. Here is a gdb stack trace of osafamfd crash: == (gdb) bt 0 0x7f457067f425 in __GI_raise (sig=) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 1 0x7f4570682b8b in __GI_abort () at abort.c:91 2 0x7f4572105f21 in __osafassert_fail ( __file=0x448498 "/home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/di.cc", line=569, func=0x4488b0 "avnd_di_susi_resp_send", __assertion=0x44837a "m_AVND_SU_IS_ASSIGN_PEND(su)") at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/libs/core/leap/sysf_def.c:278 3 0x00427a42 in avnd_di_susi_resp_send (cb=cb@entry=0x65e4a0 <_avnd_cb>, su=su@entry=0x2444980, si=si@entry=0x2439720) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/di.cc:569 4 0x00438c21 in avnd_su_pres_st_chng_prc (final_st=SA_AMF_PRESENCE_INSTANTIATION_FAILED, prv_st=SA_AMF_PRESENCE_INSTANTIATED, su=0x2444980, cb=0x65e4a0 <_avnd_cb>) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/susm.cc:1608 5 avnd_su_pres_fsm_run (cb=cb@entry=0x65e4a0 <_avnd_cb>, su=0x2444980, comp=comp@entry=0x2444bb0, ev=) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/susm.cc:1394 6 0x004188b3 in avnd_comp_clc_st_chng_prc (cb=cb@entry=0x65e4a0 <_avnd_cb>, comp=comp@entry=0x2444bb0, prv_st=prv_st@entry=SA_AMF_PRESENCE_RESTARTING, final_st=final_st@entry=SA_AMF_PRESENCE_INSTANTIATION_FAILED) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/clc.cc:1298 7 0x0041a512 in avnd_comp_clc_fsm_run (cb=cb@entry=0x65e4a0 <_avnd_cb>, comp=comp@entry=0x2444bb0, ev=) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/clc.cc:862 8 0x0041aa39 in avnd_evt_clc_resp_evh (cb=0x65e4a0 <_avnd_cb>, evt=0x7f45640008c0) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/clc.cc:416 9 0x0042c23c in avnd_evt_process (evt=0x7f45640008c0) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/main.cc:678 10 avnd_main_process () at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/main.cc:619 11 0x00405328 in main (argc=1, argv=0x7fff7bcfc988) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/main.cc:178 (gdb) --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.-- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1025 osafamfd crashed during restart failure
This osafamfd crash has been observed in our lab several times. It could be triggered easily. We have some applications started by opensaf. If one application failed, and opensaf tries to resatrt it. But the applucation failed to restart, the osafamfd always crash by the same assert di.cc line 569. Here is the syslog: Aug 27 13:34:00 slot4-MW984 osafamfnd[22493]: NO 'safComp=ZookeeperSector_PL-4,safSu=ZookeeperSectorSU_PL-4,safSg=ZookeeperSectorSG,safApp=ZookeeperSectorApp' faulted due to 'passiveMonitorFailed' : Recovery is 'componentRestart' Aug 27 13:34:00 slot4-MW984 zookeeper_sector_clean: Cleanup for CompName: safComp=ZookeeperSector_PL-4,safSu=ZookeeperSectorSU_PL-4,safSg=ZookeeperSectorSG,safApp=ZookeeperSectorApp Aug 27 13:34:00 slot4-MW984 charon: 02[KNL] 169.254.91.248 disappeared from bond0 Aug 27 13:34:01 slot4-MW984 CRON[26217]: (root) CMD (/usr/share/platform-config/atca/update-ssh-keys) Aug 27 13:34:05 slot4-MW984 zookeeper_sector_clean: Cleanup Complete for CompName: safComp=ZookeeperSector_PL-4,safSu=ZookeeperSectorSU_PL-4,safSg=ZookeeperSectorSG,safApp=ZookeeperSectorApp Aug 27 13:34:05 slot4-MW984 zookeeper_sector_inst: copying zkCleanup.movik.sector.sh to /usr/share/zookeeper/bin Aug 27 13:34:05 slot4-MW984 zookeeper_sector_inst: zkId=2 Aug 27 13:34:05 slot4-MW984 zookeeper_sector_inst: using myId 2 Aug 27 13:34:05 slot4-MW984 zookeeper_sector_inst: executing script for type sector interface bond0:2 Aug 27 13:34:05 slot4-MW984 zookeeper_sector_inst: performing zkCleanup of /var/lib/zookeeper/movik.sector/ Aug 27 13:34:05 slot4-MW984 zookeeper_sector_inst: MVK_ZK_IP_BASE = 169.254.91.247 Aug 27 13:34:05 slot4-MW984 zookeeper_sector_inst: MVK_ZK_IP_MASK = 255.255.255.0 Aug 27 13:34:05 slot4-MW984 zookeeper_sector_inst: MVK_ZK_IP_CNT = 3 Aug 27 13:34:05 slot4-MW984 zookeeper_sector_inst: MVK_ZK_EXT_PORT = 2889 Aug 27 13:34:05 slot4-MW984 zookeeper_sector_inst: MVK_ZK_INT_PORT = 3889 Aug 27 13:34:05 slot4-MW984 zookeeper_sector_inst: MY_IP = 169.254.91.248 Aug 27 13:34:05 slot4-MW984 charon: 02[KNL] 169.254.91.248 appeared on bond0 Aug 27 13:34:05 slot4-MW984 charon: 02[KNL] 169.254.91.248 disappeared from bond0 Aug 27 13:34:05 slot4-MW984 charon: 02[KNL] 169.254.91.248 appeared on bond0 Aug 27 13:34:05 slot4-MW984 zookeeper_sector_inst: copying zookeeper_environment.movik.sector to /etc/zookeeper/conf Aug 27 13:34:05 slot4-MW984 zookeeper_sector_inst: copying zkServer.sh to /usr/share/zookeeper/bin Aug 27 13:34:05 slot4-MW984 zookeeper_sector_inst: overwriting /etc/zookeeper/conf/conf.movik.sector/zoo.movik.sector.cfg Aug 27 13:34:05 slot4-MW984 zookeeper_sector_inst: touching file /var/run/zookeeper.movik.sector/zookeeper_server.pid Aug 27 13:34:05 slot4-MW984 zookeeper_sector_inst: \nserver.1=169.254.91.247:2889:3889\nserver.2=169.254.91.248:2889:3889\nserver.3=169.254.91.249:2889:3889\n Aug 27 13:34:05 slot4-MW984 zookeeper_sector_inst: Instantiating CompName: safComp=ZookeeperSector_PL-4,safSu=ZookeeperSectorSU_PL-4,safSg=ZookeeperSectorSG,safApp=ZookeeperSectorApp Aug 27 13:34:06 slot4-MW984 zookeeper_sector_inst: COMP_PID_MAP_FILE=/var/run/zookeeper.movik.sector/zookeeper_server.pid, PID=26336 Aug 27 13:34:06 slot4-MW984 amfpm: saAmfPmStart FAILED 12 Aug 27 13:34:06 slot4-MW984 osafamfnd[22493]: NO Instantiation of 'safComp=ZookeeperSector_PL-4,safSu=ZookeeperSectorSU_PL-4,safSg=ZookeeperSectorSG,safApp=ZookeeperSectorApp' failed Aug 27 13:34:06 slot4-MW984 osafamfnd[22493]: NO Reason:'Exec of script success, but script exits with non-zero status' Aug 27 13:34:06 slot4-MW984 osafamfnd[22493]: NO Exit code: 1 Aug 27 13:34:06 slot4-MW984 zookeeper_sector_clean: Cleanup for CompName: safComp=ZookeeperSector_PL-4,safSu=ZookeeperSectorSU_PL-4,safSg=ZookeeperSectorSG,safApp=ZookeeperSectorApp Aug 27 13:34:06 slot4-MW984 charon: 02[KNL] 169.254.91.248 disappeared from bond0 Aug 27 13:34:11 slot4-MW984 zookeeper_sector_clean: Cleanup Complete for CompName: safComp=ZookeeperSector_PL-4,safSu=ZookeeperSectorSU_PL-4,safSg=ZookeeperSectorSG,safApp=ZookeeperSectorApp Aug 27 13:34:17 slot4-MW984 zookeeper_sector_clean: Cleanup Complete for CompName: safComp=ZookeeperSector_PL-4,safSu=ZookeeperSectorSU_PL-4,safSg=ZookeeperSectorSG,safApp=ZookeeperSectorApp Aug 27 13:34:17 slot4-MW984 osafamfnd[22493]: WA 'safComp=ZookeeperSector_PL-4,safSu=ZookeeperSectorSU_PL-4,safSg=ZookeeperSectorSG,safApp=ZookeeperSectorApp' Presence State RESTARTING => INSTANTIATION_FAILED Aug 27 13:34:17 slot4-MW984 osafamfnd[22493]: NO Component Failover trigerred for 'safSu=ZookeeperSectorSU_PL-4,safSg=ZookeeperSectorSG,safApp=ZookeeperSectorApp': Failed component: 'safComp=ZookeeperSector_PL-4,safSu=ZookeeperSectorSU_PL-4,safSg=ZookeeperSectorSG,safApp=ZookeeperSectorApp' Aug 27 13:34:17 slot4-MW984 osafamfnd[22493]: NO 'safSu=ZookeeperSectorSU_PL-4,safSg=ZookeeperSectorSG,safApp=ZookeeperSectorApp' Presence State INSTANTIATED => INSTANTIATION_FAILED Aug 27 13:34:17 slot4-MW984
[tickets] [opensaf:tickets] #1025 osafamfd crashed during restart failure
- **Comment**: Can you please update the test steps to reproduce the problem. --- ** [tickets:#1025] osafamfd crashed during restart failure ** **Status:** unassigned **Milestone:** 4.3.3 **Created:** Wed Aug 27, 2014 05:31 PM UTC by KANG-SEN LU **Last Updated:** Thu Aug 28, 2014 12:01 PM UTC **Owner:** nobody We are running opensaf 4.4.0. Here is a gdb stack trace of osafamfd crash: == (gdb) bt 0 0x7f457067f425 in __GI_raise (sig=) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 1 0x7f4570682b8b in __GI_abort () at abort.c:91 2 0x7f4572105f21 in __osafassert_fail ( __file=0x448498 "/home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/di.cc", line=569, func=0x4488b0 "avnd_di_susi_resp_send", __assertion=0x44837a "m_AVND_SU_IS_ASSIGN_PEND(su)") at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/libs/core/leap/sysf_def.c:278 3 0x00427a42 in avnd_di_susi_resp_send (cb=cb@entry=0x65e4a0 <_avnd_cb>, su=su@entry=0x2444980, si=si@entry=0x2439720) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/di.cc:569 4 0x00438c21 in avnd_su_pres_st_chng_prc (final_st=SA_AMF_PRESENCE_INSTANTIATION_FAILED, prv_st=SA_AMF_PRESENCE_INSTANTIATED, su=0x2444980, cb=0x65e4a0 <_avnd_cb>) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/susm.cc:1608 5 avnd_su_pres_fsm_run (cb=cb@entry=0x65e4a0 <_avnd_cb>, su=0x2444980, comp=comp@entry=0x2444bb0, ev=) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/susm.cc:1394 6 0x004188b3 in avnd_comp_clc_st_chng_prc (cb=cb@entry=0x65e4a0 <_avnd_cb>, comp=comp@entry=0x2444bb0, prv_st=prv_st@entry=SA_AMF_PRESENCE_RESTARTING, final_st=final_st@entry=SA_AMF_PRESENCE_INSTANTIATION_FAILED) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/clc.cc:1298 7 0x0041a512 in avnd_comp_clc_fsm_run (cb=cb@entry=0x65e4a0 <_avnd_cb>, comp=comp@entry=0x2444bb0, ev=) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/clc.cc:862 8 0x0041aa39 in avnd_evt_clc_resp_evh (cb=0x65e4a0 <_avnd_cb>, evt=0x7f45640008c0) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/clc.cc:416 9 0x0042c23c in avnd_evt_process (evt=0x7f45640008c0) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/main.cc:678 10 avnd_main_process () at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/main.cc:619 11 0x00405328 in main (argc=1, argv=0x7fff7bcfc988) at /home/ksenlu/sandbox/klu_main/cae/extern/opensaf4/opensaf- 4.4.0/osaf/services/saf/amf/amfnd/main.cc:178 (gdb) --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.-- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1022 AMF: no response to SI lock when payload is rebooted
- **Milestone**: future --> 4.3.3 --- ** [tickets:#1022] AMF: no response to SI lock when payload is rebooted** **Status:** assigned **Milestone:** 4.3.3 **Created:** Wed Aug 27, 2014 10:31 AM UTC by Hans Feldt **Last Updated:** Thu Aug 28, 2014 02:44 PM UTC **Owner:** Nagendra Kumar Test case that used to work before with 4.4 Do SI lock active test app does not respond reboot the node where active test app is hosted => No admin op response (timeout) --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.-- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1022 AMF: no response to SI lock when payload is rebooted
- **status**: unassigned --> assigned - **assigned_to**: Nagendra Kumar --- ** [tickets:#1022] AMF: no response to SI lock when payload is rebooted** **Status:** assigned **Milestone:** future **Created:** Wed Aug 27, 2014 10:31 AM UTC by Hans Feldt **Last Updated:** Wed Aug 27, 2014 10:31 AM UTC **Owner:** Nagendra Kumar Test case that used to work before with 4.4 Do SI lock active test app does not respond reboot the node where active test app is hosted => No admin op response (timeout) --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.-- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1021 AMF: no response to SI shutdown when overridden by SI lock
- **status**: unassigned --> assigned - **assigned_to**: Nagendra Kumar - **Milestone**: future --> 4.3.3 --- ** [tickets:#1021] AMF: no response to SI shutdown when overridden by SI lock** **Status:** assigned **Milestone:** 4.3.3 **Created:** Wed Aug 27, 2014 09:42 AM UTC by Hans Feldt **Last Updated:** Wed Aug 27, 2014 11:24 AM UTC **Owner:** Nagendra Kumar A previously working testcase no longer works. An SI in SHUTTING-DOWN admin state is LOCKED. The first SHUTDOWN admin operation never gets responded. Reason is likely that only one IMM invocation ID is stored internally in amfd. The LOCK operation overwrites the SHUTDOWN invocation ID and thereby it gets lost. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.-- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1024 mds access control : imma is not able to connect to immnd after immnd restart
Added new logs with MDS_LOG_LEVEL=5 Attachment: 1024_new1.tgz (1.6 MB; application/x-compressed-tar) --- ** [tickets:#1024] mds access control : imma is not able to connect to immnd after immnd restart** **Status:** unassigned **Milestone:** 4.5.0 **Created:** Wed Aug 27, 2014 02:28 PM UTC by Neelakanta Reddy **Last Updated:** Wed Aug 27, 2014 05:13 PM UTC **Owner:** Hans Feldt syslog: --- Aug 27 16:40:07 SLES-SLOT-1 osafamfnd[31322]: NO Restarting a component of 'safSu=SC-1,safSg=NoRed,safApp=OpenSAF' (comp restart count: 9) Aug 27 16:40:07 SLES-SLOT-1 osafamfnd[31322]: NO 'safComp=IMMND,safSu=SC-1,safSg=NoRed,safApp=OpenSAF' faulted due to 'avaDown' : Recovery is 'componentRestart' Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: Started Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: NO Persistent Back-End capability configured, Pbe file:imm.db (suffix may get added) Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: NO SERVER STATE: IMM_SERVER_ANONYMOUS --> IMM_SERVER_CLUSTER_WAITING Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: NO Fevs count adjusted to 6538 preLoadPid: 0 Aug 27 16:40:07 SLES-SLOT-1 osafimmd[31246]: NO New IMMND process is on ACTIVE Controller at 2010f Aug 27 16:40:07 SLES-SLOT-1 osafimmd[31246]: NO Extended intro from node 2010f Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: NO SERVER STATE: IMM_SERVER_CLUSTER_WAITING --> IMM_SERVER_LOADING_PENDING Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: NO SERVER STATE: IMM_SERVER_LOADING_PENDING --> IMM_SERVER_SYNC_PENDING Aug 27 16:40:07 SLES-SLOT-1 osafimmd[31246]: WA IMMND on controller (not currently coord) requests sync Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: NO NODE STATE-> IMM_NODE_ISOLATED Aug 27 16:40:07 SLES-SLOT-1 osafimmd[31246]: NO Node 2010f request sync sync-pid:2570 epoch:0 Aug 27 16:40:07 SLES-SLOT-1 osafimmnd[2570]: NO NODE STATE-> IMM_NODE_W_AVAILABLE Aug 27 16:40:07 SLES-SLOT-1 osafimmd[31246]: NO Successfully announced sync. New ruling epoch:27 Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO SERVER STATE: IMM_SERVER_SYNC_PENDING --> IMM_SERVER_SYNC_CLIENT Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO NODE STATE-> IMM_NODE_FULLY_AVAILABLE 2460 Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO RepositoryInitModeT is SA_IMM_KEEP_REPOSITORY Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: WA IMM Access Control mode is DISABLED! Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Epoch set to 27 in ImmModel Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO SERVER STATE: IMM_SERVER_SYNC_CLIENT --> IMM SERVER READY Aug 27 16:40:08 SLES-SLOT-1 osafimmd[31246]: NO ACT: New Epoch for IMMND process at node 2010f old epoch: 0 new epoch:27 Aug 27 16:40:08 SLES-SLOT-1 osafimmd[31246]: NO ACT: New Epoch for IMMND process at node 2030f old epoch: 26 new epoch:27 Aug 27 16:40:08 SLES-SLOT-1 osafimmd[31246]: NO ACT: New Epoch for IMMND process at node 2040f old epoch: 26 new epoch:27 Aug 27 16:40:08 SLES-SLOT-1 osafimmd[31246]: NO ACT: New Epoch for IMMND process at node 2020f old epoch: 26 new epoch:27 Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 213 (safLogService) <4, 2010f> Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 214 (safClmService) <13, 2010f> Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 215 (MsgQueueService131343) <300, 2010f> Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 216 (safLckService) <302, 2010f> Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 217 (safEvtService) <303, 2010f> Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 218 (safCheckPointService) <304, 2010f> Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 219 (safSmfService) <305, 2010f> Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO PBE-OI established on other SC. Dumping incrementally to file imm.db Aug 27 16:40:08 SLES-SLOT-1 osafimmnd[2570]: NO Implementer connected: 220 (safAmfService) <18, 2010f> Aug 27 16:40:12 SLES-SLOT-1 osafimmnd[2570]: WA immnd_evt_proc_imm_init: PID 0 (1556) for 2010f4073a040, MDS problem? Aug 27 16:40:12 SLES-SLOT-1 osafimmnd[2570]: WA immnd_evt_proc_imm_init: PID 0 (1556) for 2010f4073a040, MDS problem? Aug 27 16:40:12 SLES-SLOT-1 osafimmnd[2570]: WA immnd_evt_proc_imm_init: PID 0 (1556) for 2010f4073a040, MDS problem? Aug 27 16:40:12 SLES-SLOT-1 osafimmnd[2570]: WA immnd_evt_proc_imm_init: PID 0 (1556) for 2010f4073a040, MDS problem? IMMA traces: Aug 27 16:40:06.872446 imma [1556:imma_om_api.c:0151] >> saImmOmInitialize Aug 27 16:40:06.872615 imma [1556:imma_om_api.c:0177] TR OM client version A.2.14 Aug 27 16:40:06.872662 imma [1556:imma_om_api.c:0210] >> initialize_common Aug 27 16:40:06.872687 imma [1556:imma_init.c:0273] >> imma_startup: use count 1 Aug 27 16:40:06.872709 imma [1556:imma_init.c:0296] << imma_startup: use count 2 Aug 27 16:40:06.874390 imma [1556:imma_proc.c:0147] >> imma_callback_ipc_destroy Aug 27 1
[tickets] [opensaf:tickets] #1027 LOG: Incorrectly detects the log service configuration object is invalid
- **status**: accepted --> fixed - **Comment**: changeset: 5674:16ac76d90d44 tag: tip parent: 5672:85de318d629f user:Lennart Lund date:Thu Aug 28 15:23:32 2014 +0200 summary: log: Fix incorrect detection of log conf obj invalid [#1027] rev: 16ac76d90d4424e379706461a65b0977c5f9e704 changeset: 5673:d0d52318ae9d branch: opensaf-4.5.x parent: 5671:d5daab61f065 user:Lennart Lund date:Thu Aug 28 15:23:32 2014 +0200 summary: log: Fix incorrect detection of log conf obj invalid [#1027] rev: d0d52318ae9d4f6c70a8981f4ccf09d4ab210657 --- ** [tickets:#1027] LOG: Incorrectly detects the log service configuration object is invalid** **Status:** fixed **Milestone:** 4.5.0 **Created:** Thu Aug 28, 2014 06:02 AM UTC by David Byrne **Last Updated:** Thu Aug 28, 2014 11:45 AM UTC **Owner:** elunlen log service logs "No or invalid log service configuration object" when the configuration object is valid. The configuration is then read from environ_var Invalid test for failure of read_logsv_config_obj() if (read_logsv_config_obj()) { --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.-- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1027 LOG: Incorrectly detects the log service configuration object is invalid
- **status**: unassigned --> accepted --- ** [tickets:#1027] LOG: Incorrectly detects the log service configuration object is invalid** **Status:** accepted **Milestone:** 4.5.0 **Created:** Thu Aug 28, 2014 06:02 AM UTC by David Byrne **Last Updated:** Thu Aug 28, 2014 07:55 AM UTC **Owner:** elunlen log service logs "No or invalid log service configuration object" when the configuration object is valid. The configuration is then read from environ_var Invalid test for failure of read_logsv_config_obj() if (read_logsv_config_obj()) { --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.-- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1029 base: osaf_secutil.h does not compile with LSB compiler
--- ** [tickets:#1029] base: osaf_secutil.h does not compile with LSB compiler** **Status:** accepted **Milestone:** 4.5.0 **Created:** Thu Aug 28, 2014 10:18 AM UTC by Anders Widell **Last Updated:** Thu Aug 28, 2014 10:18 AM UTC **Owner:** Anders Widell The new file osaf_secutil.h does not compile with an LSB compiler, due to the errors below: cc1: warnings being treated as errors In file included from osaf_secutil.c:47: include/osaf_secutil.h:58: error: 'struct ucred' declared inside parameter list include/osaf_secutil.h:58: error: its scope is only this definition or declaration, which is probably not what you want osaf_secutil.c: In function 'handle_new_connection': osaf_secutil.c:61: error: storage size of 'client_cred' isn't known osaf_secutil.c:62: error: invalid application of 'sizeof' to incomplete type 'struct ucred' osaf_secutil.c:68: error: implicit declaration of function 'strerror' osaf_secutil.c:68: error: format '%s' expects type 'char *', but argument 5 has type 'int' osaf_secutil.c:73: error: 'SO_PEERCRED' undeclared (first use in this function) osaf_secutil.c:73: error: (Each undeclared identifier is reported only once osaf_secutil.c:73: error: for each function it appears in.) osaf_secutil.c:74: error: format '%s' expects type 'char *', but argument 5 has type 'int' osaf_secutil.c:61: error: unused variable 'client_cred' osaf_secutil.c: In function 'server_sock_create': osaf_secutil.c:115: error: format '%s' expects type 'char *', but argument 6 has type 'int' osaf_secutil.c:122: error: implicit declaration of function 'strcpy' osaf_secutil.c:122: error: incompatible implicit declaration of built-in function 'strcpy' osaf_secutil.c:123: error: implicit declaration of function 'strlen' osaf_secutil.c:123: error: incompatible implicit declaration of built-in function 'strlen' osaf_secutil.c:125: error: format '%s' expects type 'char *', but argument 6 has type 'int' --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.-- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1028 osaf: String pointer inside SaNameT not detected by Valgrind
--- ** [tickets:#1028] osaf: String pointer inside SaNameT not detected by Valgrind** **Status:** accepted **Milestone:** 4.5.0 **Created:** Thu Aug 28, 2014 09:56 AM UTC by Anders Widell **Last Updated:** Thu Aug 28, 2014 09:56 AM UTC **Owner:** Anders Widell The string pointer stored inside the SaNameT structure for long DNs (longer than 255 bytes) is not detected by Valgrind, since it is not stored on an aligned address. This has the effect that allocated memory may be reported as "definitely lost" rather than "still reachable" by the Valgrind memory leak detection. The fix is to store the pointer at an aligned address. It will only work when the SaNameT structure itself is stored at an aligned address (which is not guaranteed since it contains nothing larger than an 16-bit integer), but it should work in most cases anyhow. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.-- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1027 LOG: Incorrectly detects the log service configuration object is invalid
- **assigned_to**: elunlen --- ** [tickets:#1027] LOG: Incorrectly detects the log service configuration object is invalid** **Status:** unassigned **Milestone:** 4.5.0 **Created:** Thu Aug 28, 2014 06:02 AM UTC by David Byrne **Last Updated:** Thu Aug 28, 2014 06:02 AM UTC **Owner:** elunlen log service logs "No or invalid log service configuration object" when the configuration object is valid. The configuration is then read from environ_var Invalid test for failure of read_logsv_config_obj() if (read_logsv_config_obj()) { --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.-- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets