[tickets] [opensaf:tickets] #659 CLM: OpenSAF fails to compile
changeset: 4733:011a9ee6d07e tag: tip user:Mathivanan N.P.mathi.naic...@oracle.com date:Mon Dec 16 13:30:32 2013 +0530 summary: clms: fix unused variable warning [#659] [staging:011a9e] --- ** [tickets:#659] CLM: OpenSAF fails to compile** **Status:** fixed **Created:** Sun Dec 15, 2013 01:12 PM UTC by Zoran Milinkovic **Last Updated:** Sun Dec 15, 2013 01:12 PM UTC **Owner:** nobody OpenSAF fails to compile due to the latest CLM change. The problem is seen on Debian (gcc 4.7.2) and Ubuntu (gcc 4.6.3). make[7]: Entering directory `/local/scratch/emilzor/sf/opensaf-default-clmtest/osaf/services/saf/clmsv/nodeagent' CC osafclmna-main.o main.c: In function ‘clmna_mds_svc_evt’: main.c:161:11: error: variable ‘rc’ set but not used [-Werror=unused-but-set-variable] cc1: all warnings being treated as errors --- 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.-- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #294 Error escalation for a component is going from COMPONENT RESTART to SU FAILOVER without SU RESTART during si-swap operation
changeset: 71:29ec843d21ed branch: opensaf-4.2.x parent: 66:5a9e42c45624 user:praveen.malv...@oracle.com date:Mon Dec 16 14:31:56 2013 +0530 summary: amf: documentation related to suRestart recovery [#294] changeset: 72:266ae7b3dfdd branch: opensaf-4.3.x parent: 67:3196935a5155 user:praveen.malv...@oracle.com date:Mon Dec 16 14:32:47 2013 +0530 summary: amf: documentation related to suRestart recovery [#294] changeset: 73:ce8d10f283e6 tag: tip parent: 70:6053800ae647 user:praveen.malv...@oracle.com date:Mon Dec 16 14:33:22 2013 +0530 summary: amf: documentation related to suRestart recovery [#294] --- ** [tickets:#294] Error escalation for a component is going from COMPONENT RESTART to SU FAILOVER without SU RESTART during si-swap operation** **Status:** fixed **Created:** Wed May 22, 2013 11:24 AM UTC by Nagendra Kumar **Last Updated:** Fri Dec 06, 2013 07:33 AM UTC **Owner:** nobody Migrated from http://devel.opensaf.org/ticket/2557 Changeset: 3406 Configuration: 2N configuration with 2 SUs, one on PL-4 and one on PL-5. SG contains 7 SIs Each SU is having 5 Components. Component 3 of SU1 is faulty and rejects the Active assignment and its recovery policy is COMP RESTART SU1 is brought up as Standby and SU2 is brought up as Active When SI-SWAP admin operation is triggered on SI3, COMP3 goes for recovery as it does not accept the Active assignment The recovery goes from COMPONENT RESTART to SU FAILOVER without SU RESTART The following is the syslog output of PL-4: amf-adm si-swap safSi=SI3,safApp=test2nApp Mar 6 16:32:32 SLES11-SLOT-1 osafamfnd[2848]: Assigning 'safSi=SI1,safApp=test2nApp' ACTIVE to 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:32:42 SLES11-SLOT-1 osafamfnd[2848]: 'safComp=COMP3,safSu=SU1,safSg=SG,safApp=test2nApp' faulted due to 'csiSetcallbackTimeout(10)' : Recovery is 'componentRestart(2)' Mar 6 16:32:42 SLES11-SLOT-1 logger: CLC-CLI spawnd cleanup for safComp=COMP3,safSu=SU1,safSg=SG,safApp=test2nApp Mar 6 16:32:42 SLES11-SLOT-1 logger: CLC-CLI spawnd instantiate for safComp=COMP3,safSu=SU1,safSg=SG,safApp=test2nApp Mar 6 16:32:52 SLES11-SLOT-1 osafamfnd[2848]: 'safComp=COMP3,safSu=SU1,safSg=SG,safApp=test2nApp' faulted due to 'csiSetcallbackTimeout(10)' : Recovery is 'componentRestart(2)' Mar 6 16:32:52 SLES11-SLOT-1 logger: CLC-CLI spawnd cleanup for safComp=COMP3,safSu=SU1,safSg=SG,safApp=test2nApp Mar 6 16:32:52 SLES11-SLOT-1 logger: CLC-CLI spawnd instantiate for safComp=COMP3,safSu=SU1,safSg=SG,safApp=test2nApp Mar 6 16:33:02 SLES11-SLOT-1 osafamfnd[2848]: 'safComp=COMP3,safSu=SU1,safSg=SG,safApp=test2nApp' faulted due to 'csiSetcallbackTimeout(10)' : Recovery is 'suFailover(11)' Mar 6 16:33:02 SLES11-SLOT-1 osafamfnd[2848]: Assigned 'safSi=SI1,safApp=test2nApp' ACTIVE to 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:33:02 SLES11-SLOT-1 osafamfnd[2848]: 'safSu=SU1,safSg=SG,safApp=test2nApp' Presence State INSTANTIATED = TERMINATING Mar 6 16:33:02 SLES11-SLOT-1 logger: CLC-CLI spawnd cleanup for safComp=COMP3,safSu=SU1,safSg=SG,safApp=test2nApp Mar 6 16:33:02 SLES11-SLOT-1 osafamfnd[2848]: Removing 'all SIs' from 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:33:02 SLES11-SLOT-1 osafamfnd[2848]: Removed 'safSi=SI1,safApp=test2nApp' from 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:33:02 SLES11-SLOT-1 osafamfnd[2848]: Removed 'safSi=SI2,safApp=test2nApp' from 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:33:02 SLES11-SLOT-1 osafamfnd[2848]: Removed 'safSi=SI3,safApp=test2nApp' from 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:33:02 SLES11-SLOT-1 osafamfnd[2848]: Removed 'safSi=SI4,safApp=test2nApp' from 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:33:02 SLES11-SLOT-1 osafamfnd[2848]: Removed 'safSi=SI5,safApp=test2nApp' from 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:33:02 SLES11-SLOT-1 osafamfnd[2848]: Removed 'safSi=SI6,safApp=test2nApp' from 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:33:02 SLES11-SLOT-1 osafamfnd[2848]: Removed 'safSi=SI7,safApp=test2nApp' from 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:33:02 SLES11-SLOT-1 logger: CLC-CLI spawnd instantiate for safComp=COMP3,safSu=SU1,safSg=SG,safApp=test2nApp Mar 6 16:33:02 SLES11-SLOT-1 osafamfnd[2848]: 'safSu=SU1,safSg=SG,safApp=test2nApp' Presence State TERMINATING = INSTANTIATED Mar 6 16:33:02 SLES11-SLOT-1 osafamfnd[2848]: Assigning 'safSi=SI1,safApp=test2nApp' STANDBY to 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:33:02 SLES11-SLOT-1 osafamfnd[2848]: Assigning 'safSi=SI2,safApp=test2nApp' STANDBY to 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:33:03 SLES11-SLOT-1 osafamfnd[2848]: Assigning 'safSi=SI3,safApp=test2nApp' STANDBY to 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:33:03 SLES11-SLOT-1 osafamfnd[2848]: Assigning 'safSi=SI4,safApp=test2nApp' STANDBY to 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6
[tickets] [opensaf:tickets] #294 Error escalation for a component is going from COMPONENT RESTART to SU FAILOVER without SU RESTART during si-swap operation
- **assigned_to**: Praveen --- ** [tickets:#294] Error escalation for a component is going from COMPONENT RESTART to SU FAILOVER without SU RESTART during si-swap operation** **Status:** fixed **Created:** Wed May 22, 2013 11:24 AM UTC by Nagendra Kumar **Last Updated:** Mon Dec 16, 2013 09:07 AM UTC **Owner:** Praveen Migrated from http://devel.opensaf.org/ticket/2557 Changeset: 3406 Configuration: 2N configuration with 2 SUs, one on PL-4 and one on PL-5. SG contains 7 SIs Each SU is having 5 Components. Component 3 of SU1 is faulty and rejects the Active assignment and its recovery policy is COMP RESTART SU1 is brought up as Standby and SU2 is brought up as Active When SI-SWAP admin operation is triggered on SI3, COMP3 goes for recovery as it does not accept the Active assignment The recovery goes from COMPONENT RESTART to SU FAILOVER without SU RESTART The following is the syslog output of PL-4: amf-adm si-swap safSi=SI3,safApp=test2nApp Mar 6 16:32:32 SLES11-SLOT-1 osafamfnd[2848]: Assigning 'safSi=SI1,safApp=test2nApp' ACTIVE to 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:32:42 SLES11-SLOT-1 osafamfnd[2848]: 'safComp=COMP3,safSu=SU1,safSg=SG,safApp=test2nApp' faulted due to 'csiSetcallbackTimeout(10)' : Recovery is 'componentRestart(2)' Mar 6 16:32:42 SLES11-SLOT-1 logger: CLC-CLI spawnd cleanup for safComp=COMP3,safSu=SU1,safSg=SG,safApp=test2nApp Mar 6 16:32:42 SLES11-SLOT-1 logger: CLC-CLI spawnd instantiate for safComp=COMP3,safSu=SU1,safSg=SG,safApp=test2nApp Mar 6 16:32:52 SLES11-SLOT-1 osafamfnd[2848]: 'safComp=COMP3,safSu=SU1,safSg=SG,safApp=test2nApp' faulted due to 'csiSetcallbackTimeout(10)' : Recovery is 'componentRestart(2)' Mar 6 16:32:52 SLES11-SLOT-1 logger: CLC-CLI spawnd cleanup for safComp=COMP3,safSu=SU1,safSg=SG,safApp=test2nApp Mar 6 16:32:52 SLES11-SLOT-1 logger: CLC-CLI spawnd instantiate for safComp=COMP3,safSu=SU1,safSg=SG,safApp=test2nApp Mar 6 16:33:02 SLES11-SLOT-1 osafamfnd[2848]: 'safComp=COMP3,safSu=SU1,safSg=SG,safApp=test2nApp' faulted due to 'csiSetcallbackTimeout(10)' : Recovery is 'suFailover(11)' Mar 6 16:33:02 SLES11-SLOT-1 osafamfnd[2848]: Assigned 'safSi=SI1,safApp=test2nApp' ACTIVE to 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:33:02 SLES11-SLOT-1 osafamfnd[2848]: 'safSu=SU1,safSg=SG,safApp=test2nApp' Presence State INSTANTIATED = TERMINATING Mar 6 16:33:02 SLES11-SLOT-1 logger: CLC-CLI spawnd cleanup for safComp=COMP3,safSu=SU1,safSg=SG,safApp=test2nApp Mar 6 16:33:02 SLES11-SLOT-1 osafamfnd[2848]: Removing 'all SIs' from 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:33:02 SLES11-SLOT-1 osafamfnd[2848]: Removed 'safSi=SI1,safApp=test2nApp' from 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:33:02 SLES11-SLOT-1 osafamfnd[2848]: Removed 'safSi=SI2,safApp=test2nApp' from 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:33:02 SLES11-SLOT-1 osafamfnd[2848]: Removed 'safSi=SI3,safApp=test2nApp' from 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:33:02 SLES11-SLOT-1 osafamfnd[2848]: Removed 'safSi=SI4,safApp=test2nApp' from 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:33:02 SLES11-SLOT-1 osafamfnd[2848]: Removed 'safSi=SI5,safApp=test2nApp' from 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:33:02 SLES11-SLOT-1 osafamfnd[2848]: Removed 'safSi=SI6,safApp=test2nApp' from 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:33:02 SLES11-SLOT-1 osafamfnd[2848]: Removed 'safSi=SI7,safApp=test2nApp' from 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:33:02 SLES11-SLOT-1 logger: CLC-CLI spawnd instantiate for safComp=COMP3,safSu=SU1,safSg=SG,safApp=test2nApp Mar 6 16:33:02 SLES11-SLOT-1 osafamfnd[2848]: 'safSu=SU1,safSg=SG,safApp=test2nApp' Presence State TERMINATING = INSTANTIATED Mar 6 16:33:02 SLES11-SLOT-1 osafamfnd[2848]: Assigning 'safSi=SI1,safApp=test2nApp' STANDBY to 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:33:02 SLES11-SLOT-1 osafamfnd[2848]: Assigning 'safSi=SI2,safApp=test2nApp' STANDBY to 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:33:03 SLES11-SLOT-1 osafamfnd[2848]: Assigning 'safSi=SI3,safApp=test2nApp' STANDBY to 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:33:03 SLES11-SLOT-1 osafamfnd[2848]: Assigning 'safSi=SI4,safApp=test2nApp' STANDBY to 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:33:03 SLES11-SLOT-1 osafamfnd[2848]: Assigning 'safSi=SI5,safApp=test2nApp' STANDBY to 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:33:03 SLES11-SLOT-1 osafamfnd[2848]: Assigning 'safSi=SI6,safApp=test2nApp' STANDBY to 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:33:03 SLES11-SLOT-1 osafamfnd[2848]: Assigning 'safSi=SI7,safApp=test2nApp' STANDBY to 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:33:03 SLES11-SLOT-1 osafamfnd[2848]: Assigned 'safSi=SI1,safApp=test2nApp' STANDBY to 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6 16:33:03 SLES11-SLOT-1 osafamfnd[2848]: Assigned 'safSi=SI2,safApp=test2nApp' STANDBY to 'safSu=SU1,safSg=SG,safApp=test2nApp' Mar 6
[tickets] [opensaf:tickets] #49 IMM: Support reference integrity checking
- **status**: review -- fixed --- ** [tickets:#49] IMM: Support reference integrity checking** **Status:** fixed **Created:** Wed May 08, 2013 07:52 AM UTC by Anders Bjornerstedt **Last Updated:** Sun Dec 15, 2013 03:59 PM UTC **Owner:** Zoran Milinkovic Migrated from: http://devel.opensaf.org/ticket/3122 Add a new flag for object attributes, defined as follows: #define SA_IMM_ATTR_NO_DANGLING 0x0400 The SA_IMM_ATTR_NO_DANGLING attribute is only meaningful for configuration attributes of type SA_IMM_ATTR_SANAMET. Setting it for runtime attributes or configuration attributes of other types is not allowed and generates an error. The IMM service will guarantee that the value(s) of an attribute with the SA_IMM_ATTR_NO_DANGLING flag, when set, contains the distinguished name of an existing IMM object. IMM will reject attempts to set it to anything that is not the distinguished name of an existing object, and it will reject attempts to delete objects that are referenced by such an attribute. This validation is performed when the CCB is applied, which means that it will take into account all changes performed within the CCB. Optionally, it is also possible to restrict the type of objects that an attribute with the flag SA_IMM_ATTR_NO_DANGLING is allowed to reference. If the attribute name contains the colon character (ASCII value 58), then the part of the attribute name following the colon specifies the class name that referenced object must be an instance of. The IMM service will reject attempts to set the attribute to the distinguished name of an object that is not an instance of this class. - In addition, besides checking that the attribute value to be assigned is the DN of an existing object, the imm service will check that the object is persistent, i.e. either the DN of a config object or the DN of a persistent runtime object. References to non persistent runtime objects can not be allowed since a cluster restart would automatically cause such references to become dangling. (Peristent runtime objects should of course never be used, but since they *are* used heavily by services such as smfsv, it would be strange not to support referential integrity covering references to such objects. References from one PRTO to another PRTO would not be allowed according to the above rules, so this addition concerns only references from config objects to runtime objects. --- 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.-- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #49 IMM: Support reference integrity checking
default(4.4): changeset: 4734:bbb2c89c1361 user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Sun Dec 15 16:42:12 2013 +0100 summary: IMM: Add support for NO_DANGLING flag to API [#49] changeset: 4735:e0399aa51366 user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Sun Dec 15 16:42:41 2013 +0100 summary: IMM: Add support for NO_DANGLING flag to the service [#49] changeset: 4736:bb56f3cb6b11 tag: tip user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Sun Dec 15 16:43:09 2013 +0100 summary: IMMTOOLS: Add support for NO_DANGLING flag to tools [#49] --- ** [tickets:#49] IMM: Support reference integrity checking** **Status:** fixed **Created:** Wed May 08, 2013 07:52 AM UTC by Anders Bjornerstedt **Last Updated:** Sun Dec 15, 2013 03:59 PM UTC **Owner:** Zoran Milinkovic Migrated from: http://devel.opensaf.org/ticket/3122 Add a new flag for object attributes, defined as follows: #define SA_IMM_ATTR_NO_DANGLING 0x0400 The SA_IMM_ATTR_NO_DANGLING attribute is only meaningful for configuration attributes of type SA_IMM_ATTR_SANAMET. Setting it for runtime attributes or configuration attributes of other types is not allowed and generates an error. The IMM service will guarantee that the value(s) of an attribute with the SA_IMM_ATTR_NO_DANGLING flag, when set, contains the distinguished name of an existing IMM object. IMM will reject attempts to set it to anything that is not the distinguished name of an existing object, and it will reject attempts to delete objects that are referenced by such an attribute. This validation is performed when the CCB is applied, which means that it will take into account all changes performed within the CCB. Optionally, it is also possible to restrict the type of objects that an attribute with the flag SA_IMM_ATTR_NO_DANGLING is allowed to reference. If the attribute name contains the colon character (ASCII value 58), then the part of the attribute name following the colon specifies the class name that referenced object must be an instance of. The IMM service will reject attempts to set the attribute to the distinguished name of an object that is not an instance of this class. - In addition, besides checking that the attribute value to be assigned is the DN of an existing object, the imm service will check that the object is persistent, i.e. either the DN of a config object or the DN of a persistent runtime object. References to non persistent runtime objects can not be allowed since a cluster restart would automatically cause such references to become dangling. (Peristent runtime objects should of course never be used, but since they *are* used heavily by services such as smfsv, it would be strange not to support referential integrity covering references to such objects. References from one PRTO to another PRTO would not be allowed according to the above rules, so this addition concerns only references from config objects to runtime objects. --- 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.-- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #635 IMM: Update the README file to document NO_DANGLING
changeset: 4737:0caa487a99d3 tag: tip user:Anders Bjornerstedt anders.bjornerst...@ericsson.com date:Mon Dec 16 14:24:44 2013 +0100 summary: IMM: Update the README file to document NO_DANGLING [#635] --- ** [tickets:#635] IMM: Update the README file to document NO_DANGLING** **Status:** fixed **Created:** Thu Nov 21, 2013 12:34 PM UTC by Anders Bjornerstedt **Last Updated:** Tue Dec 03, 2013 01:42 PM UTC **Owner:** Anders Bjornerstedt This is related to ticket (#49) 'IMM: Support reference integrity checking. Add documentation to the osaf/services/saf/README that describes the NO_DANGLING feature. --- 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.-- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #635 IMM: Update the README file to document NO_DANGLING
- **status**: review -- fixed --- ** [tickets:#635] IMM: Update the README file to document NO_DANGLING** **Status:** fixed **Created:** Thu Nov 21, 2013 12:34 PM UTC by Anders Bjornerstedt **Last Updated:** Tue Dec 03, 2013 01:42 PM UTC **Owner:** Anders Bjornerstedt This is related to ticket (#49) 'IMM: Support reference integrity checking. Add documentation to the osaf/services/saf/README that describes the NO_DANGLING feature. --- 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.-- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #661 logsv test: Add more features to saflogtest tool
- **status**: accepted -- review --- ** [tickets:#661] logsv test: Add more features to saflogtest tool** **Status:** review **Created:** Mon Dec 16, 2013 01:41 PM UTC by elunlen **Last Updated:** Mon Dec 16, 2013 01:41 PM UTC **Owner:** elunlen Add new options making it possible to do some more tests. * Make it possible to open more than one stream at the same time. (Simplification, only appliction streams and not in combination with other streams) E.g. makes it possible to test closing several streams at once when testing finalize, client down etc. * Stop and wait so that the client don't disappear and streams stay open E.g. makes it possible to test writing to re-opened application streams * Exit without closing streams and finalize. Makes it possible to test 'client down' The enhanced option list -h or --help this help -k or --ackdo not wait for ack after write, default wait -l or --alarm write to alarm stream -n or --notification write to notification stream -y or --system write to system stream (default) -a NAME or --application=NAME write to application stream NAME Can be used more than once, more than one stream can be opened Cannot be used in combination with other streams Max 4 application streams can be created Example: saflogtest -a tst1 tst1 msg -a tst2 -a tst3 tst3 msg -b NAME or --capplication=NAME write to config application stream NAME -s SEV or --severity=SEV use severity SEV, default INFO valid severity names: emerg, alert, crit, error, warn, notice, info -i INT or --interval=INT write with interval INT us (only with --count, default 0us) -c CNT or --count=CNT write CNT number of times, -1 forever (with interval INT) -o Open log stream(s) and wait forever. Exit on any key -e Exit without closing stream(s) or finalizing after log records are written --- 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.-- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #662 AMF: relax saAmfCtSwBundle initialized requirement
--- ** [tickets:#662] AMF: relax saAmfCtSwBundle initialized requirement** **Status:** unassigned **Created:** Mon Dec 16, 2013 02:16 PM UTC by Hans Feldt **Last Updated:** Mon Dec 16, 2013 02:16 PM UTC **Owner:** nobody Requiring comptype to have a bundle value makes it harder to configure an AMF model for non SMF managed software. For example OCF resource-agents. In enhancement http://devel.opensaf.org/ticket/2452 it got possible to use absolute paths for CLC-CLI commands thus removing the need for bundle references. So this enhancement propose that when CLC CLI commands are configured with an absolute path, the bundle requirement is relaxed so that it no longer is mandatory. --- 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.-- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #662 AMF: relax saAmfCtSwBundle initialized requirement
- **status**: unassigned -- accepted - **assigned_to**: Hans Feldt --- ** [tickets:#662] AMF: relax saAmfCtSwBundle initialized requirement** **Status:** accepted **Created:** Mon Dec 16, 2013 02:16 PM UTC by Hans Feldt **Last Updated:** Mon Dec 16, 2013 02:16 PM UTC **Owner:** Hans Feldt Requiring comptype to have a bundle value makes it harder to configure an AMF model for non SMF managed software. For example OCF resource-agents. In enhancement http://devel.opensaf.org/ticket/2452 it got possible to use absolute paths for CLC-CLI commands thus removing the need for bundle references. So this enhancement propose that when CLC CLI commands are configured with an absolute path, the bundle requirement is relaxed so that it no longer is mandatory. --- 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.-- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #328 amf: amfd crashed on standby controller when two payloads are brought up with same slot id.
Detecting wrong configured nodes is not Amf job. This need to be taken care at
Cluster management levels.
---
** [tickets:#328] amf: amfd crashed on standby controller when two payloads are
brought up with same slot id.**
**Status:** unassigned
**Labels:** 4.2.0
**Created:** Fri May 24, 2013 09:43 AM UTC by Praveen
**Last Updated:** Fri May 24, 2013 09:43 AM UTC
**Owner:** nobody
Migrated from http://devel.opensaf.org/ticket/2262.
Two payloads are brought up with amf slot id,Both of them came up,but amfnd on
standby controller crashed with following bt
gdb) bt full
0 0x7fd5c29c2e6d in search (pTree=0x6b79e0, key=0x6f63d8 ) at
patricia.c:94
pNode = (NCS_PATRICIA_NODE *) 0x0
pPrevNode = (NCS_PATRICIA_NODE *) 0x6f6290
1 0x7fd5c29c30e9 in ncs_patricia_tree_add (pTree=0x6b79e0, pNode=0x6f6290)
at patricia.c:259
pSrch = (NCS_PATRICIA_NODE *) 0x7fffcae48bb0
pTmpNode = (NCS_PATRICIA_NODE *) 0x433bff
pPrevNode = (NCS_PATRICIA_NODE *) 0x7fffcae48bdc
bit = 132096
2 0x004337d9 in avd_node_add_nodeid (node=0x6f6290) at avd_node.c:42
rc = 132096
PRETTY_FUNCTION = avd_node_add_nodeid
3 0x0041a0a3 in avd_ckpt_node (cb=0x6b6b40, ckpt_node=0x7fffcae48c80,
action=NCS_MBCSV_ACT_UPDATE) at avd_ckpt_updt.c:71
rc = 1
node = (AVD_AVND *) 0x6f6290
FUNCTION = avd_ckpt_node
PRETTY_FUNCTION = avd_ckpt_node
4 0x0040d2e5 in avsv_decode_ckpt_avd_node_config (cb=0x6b6b40,
dec=0x718798) at avd_ckpt_dec.c:325
status = 1
avnd_ptr = (AVD_AVND *) 0x7fffcae48c80
dec_avnd = {tree_node_id_node = {bit = 0, left = 0x0, right = 0x0, key_info =
0x0}, tree_node_name_node = {bit = 0, left = 0x0, right = 0x0,
key_info = 0x0}, name = {length = 42, value =
safAmfNode=PL-4,safAmfCluster=myAmfCluster, '\0' repeats 213 times},
node_info = {nodeId = 132096,
nodeAddress = {family = SA_CLM_AF_INET, length = 0,
value = '\0' repeats 14 times, \n, '\0' repeats 15 times, !\000��, '\0'
repeats 29 times}, nodeName = {length = 0,
value = '\0' repeats 255 times}, executionEnvironment = {length = 0, value =
'\0' repeats 255 times}, member = SA_TRUE,
bootTimestamp = 13192663190, initialViewNumber = 9}, adest = 0,
saAmfNodeClmNode = {length = 0, value = '\0' repeats 255 times},
saAmfNodeCapacity = 0x0, saAmfNodeSuFailOverProb = 0, saAmfNodeSuFailoverMax =
0, saAmfNodeAutoRepair = SA_FALSE,
saAmfNodeFailfastOnTerminationFailure = SA_FALSE,
saAmfNodeFailfastOnInstantiationFailure = SA_FALSE, saAmfNodeAdminState =
SA_AMF_ADMIN_UNLOCKED,
saAmfNodeOperState = SA_AMF_OPERATIONAL_DISABLED, admin_node_pend_cbk =
{admin_oper = 0, invocation = 0}, su_cnt_admin_oper = 0,
node_state = AVD_AVND_STATE_ABSENT, list_of_ncs_su = 0x0, list_of_su = 0x0,
pg_csi_list = {order = 0, start_ptr = 0x0, end_ptr = 0x0, cmp_cookie = 0,
free_cookie = 0, n_nodes = 0}, type = AVSV_AVND_CARD_PAYLOAD, rcv_msg_id = 0,
snd_msg_id = 0, cluster_list_node_next = 0x0, cluster = 0x0,
clm_pend_inv = 0, clm_change_start_preceded = false, recvr_fail_sw = false}
ederror = 4294901760
FUNCTION = avsv_decode_ckpt_avd_node_config
PRETTY_FUNCTION = avsv_decode_ckpt_avd_node_config
5 0x0040cc56 in avsv_dequeue_async_update_msgs (cb=0x6b6b40,
pr_or_fr=true) at avd_chkop.c:1214
status = 1
updt_msg = (AVSV_ASYNC_UPDT_MSG_QUEUE *) 0x718790
FUNCTION = avsv_dequeue_async_update_msgs
6 0x0040b817 in avsv_mbcsv_process_dec_cb (cb=0x6b6b40,
arg=0x7fffcae492d0) at avd_chkop.c:327
status = 1
FUNCTION = avsv_mbcsv_process_dec_cb
7 0x0040b48a in avsv_mbcsv_cb (arg=0x7fffcae492d0) at avd_chkop.c:169
status = 32725
8 0x7fd5c29dba35 in ncs_mbscv_rcv_decode (peer=0x6fb320, evt=0x6f1220) at
mbcsv_act.c:393
parg = {i_op = NCS_MBCSV_CBOP_DEC, i_client_hdl = 0, i_ckpt_hdl = 4292870177,
info = {encode = {io_msg_type = NCS_MBCSV_MSG_ASYNC_UPDATE,
io_action = NCS_MBCSV_ACT_UPDATE, io_reo_type = 48, io_reo_hdl = 0, io_uba =
{start = 0x0, ub = 0x0,
bufp = 0x14 Address 0x14 out of bounds, res = 20, ttl = 0,
max = 7130592}, io_req_context = 7077892, i_peer_version = 37760},
decode = {i_msg_type = NCS_MBCSV_MSG_ASYNC_UPDATE, i_action =
NCS_MBCSV_ACT_UPDATE, i_reo_type = 48, i_uba = {start = 0x0, ub = 0x0, bufp =
0x0,
res = 0, ttl = 20, max = 20}, o_req_context = 7130592, i_peer_version = 4},
peer = {i_service = NCS_SERVICE_ID_LEAP_TMR, i_peer_version = 3},
notify = {i_uba = {start = 0x30001, ub = 0x30, bufp = 0x0, res = 0, ttl =
0, max = 0}, i_peer_version = 0, i_msg = 0x14}, error = {
i_code = NCS_MBCSV_WARM_SYNC_TMR_EXP, i_err = 3, i_arg = 0x30, i_peer_version =
0}}}
status = 2
mbc_inst = (MBCSV_REG *) 0x6ccd00
FUNCTION = ncs_mbscv_rcv_decode
9 0x7fd5c29dbbfd in ncs_mbcsv_rcv_async_update (peer=0x6fb320,
evt=0x6f1220) at mbcsv_act.c:440
—Type return to continue, or q return to quit—
FUNCTION = ncs_mbcsv_rcv_async_update
10 0x7fd5c29e3d91 in mbcsv_process_events
[tickets] [opensaf:tickets] #323 amf: Reboot of the node is not happening when amfnd is killed.
- **status**: unassigned -- not-reproducible - **assigned_to**: Nagendra Kumar --- ** [tickets:#323] amf: Reboot of the node is not happening when amfnd is killed.** **Status:** not-reproducible **Created:** Fri May 24, 2013 09:14 AM UTC by Praveen **Last Updated:** Mon Dec 09, 2013 05:11 PM UTC **Owner:** Nagendra Kumar Migrated from http://devel.opensaf.org/ticket/2195. Setup: RHEL 6.0 VM setup. The transport used is TCP. Testing is done on changeset 2775.n Scenario: == Observed that when amfnd is killed on the active controller, the node did not go for reboot. From /var/log/messages: = Sep 28 00:37:35 SLOT_1 root: killing osafamfnd from invoke_failover.sh Sep 28 00:37:35 SLOT_1 osafclmd[1528]: AMF Node Director is down, terminate this process Sep 28 00:37:35 SLOT_1 app_comp: AMF Node Director is down, terminate this process Sep 28 00:37:35 SLOT_1 osafntfd[1517]: AMF Node Director is down, terminate this process Sep 28 00:37:35 SLOT_1 osaflogd[1506]: AMF Node Director is down, terminate this process Sep 28 00:37:35 SLOT_1 osafrded[1456]: AMF Node Director is down, terminate this process Sep 28 00:37:35 SLOT_1 osaffmd[1467]: AMF Node Director is down, terminate this process Sep 28 00:37:35 SLOT_1 osafevtd[1750]: AMF Node Director is down, terminate this process Sep 28 00:37:35 SLOT_1 osafckptnd[1736]: AMF Node Director is down, terminate this process Sep 28 00:37:36 SLOT_1 osafsmfd[1720]: AMF Node Director is down, terminate this process Sep 28 00:37:36 SLOT_1 osafmsgnd[1715]: AMF Node Director is down, terminate this process Sep 28 00:37:36 SLOT_1 osaflcknd[1691]: AMF Node Director is down, terminate this process Sep 28 00:37:36 SLOT_1 osafmsgd[1688]: AMF Node Director is down, terminate this process Sep 28 00:37:36 SLOT_1 osafsmfnd[1666]: AMF Node Director is down, terminate this process Sep 28 00:37:36 SLOT_1 osafimmd[1477]: AMF Node Director is down, terminate this process Sep 28 00:37:36 SLOT_1 osaflckd[1644]: AMF Node Director is down, terminate this process Sep 28 00:37:36 SLOT_1 osafimmnd[1488]: AMF Node Director is down, terminate this process Sep 28 00:37:36 SLOT_1 osafamfwd[1618]: Rebooting OpenSAF NodeId? = 0 EE Name = No EE Mapped, Reason: AMF unexpectedly crashed Sep 28 00:37:40 SLOT_1 osafamfd[1549]: avd_mds_send: failed 2, to 13@2010f061a Sep 28 00:37:40 SLOT_1 osafamfd[1549]: avd_tmr_snd_hb_evh failed to send HB msg Sep 28 00:37:50 SLOT_1 osafamfd[1549]: avd_mds_send: failed 2, to 13@2010f061a Sep 28 00:37:50 SLOT_1 osafamfd[1549]: avd_tmr_snd_hb_evh failed to send HB msg Sep 28 00:38:00 SLOT_1 osafamfd[1549]: avd_mds_send: failed 2, to 13@2010f061a Sep 28 00:38:00 SLOT_1 osafamfd[1549]: avd_tmr_snd_hb_evh failed to send HB msg Sep 28 00:38:10 SLOT_1 osafamfd[1549]: avd_mds_send: failed 2, to 13@2010f061a Sep 28 00:38:10 SLOT_1 osafamfd[1549]: avd_tmr_snd_hb_evh failed to send HB msg Sep 28 00:38:21 SLOT_1 osafamfd[1549]: avd_mds_send: failed 2, to 13@2010f061a Sep 28 00:38:21 SLOT_1 osafamfd[1549]: avd_tmr_snd_hb_evh failed to send HB msg Sep 28 00:38:31 SLOT_1 osafamfwd[1618]: TIMEOUT receiving AMF health check request, generating core for amfnd Sep 28 00:38:31 SLOT_1 osafamfwd[1618]: Last received healthcheck cnt=51 at Wed Sep 28 00:37:31 2011 Sep 28 00:38:31 SLOT_1 osafamfwd[1618]: ordering system reboot == Amfnd, Immnd traces are of huge size and hence not attaching them. Changed 20 months ago by hafe You are running OpenSAF as the opensaf user and you haven't given the opensaf user sudo permission for the needed commands. But agree that we need to log this issue to make it clear that's the problem. Basically OpenSAF needs better logs in the opensaf_reboot script as well in the opensaf_reboot function. Changed 19 months ago by surya ■milestone changed from 4.2.0.GA to 4.2.1 Changed 19 months ago by surya ■status changed from new to closed ■resolution set to duplicate Duplicate of 2106 TICKET Changed 18 months ago by manu ■status changed from closed to reopened ■resolutionduplicate deleted ■description modified (diff) On SLES11 64bit PC setup, with changeset 3065, observed that after killing amfnd, node is not going for reboot. Changed 13 months ago by ehsjoar ■milestone changed from 4.2.1 to future_releases --- 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.-- Rapidly troubleshoot problems before they affect your business. Most IT
[tickets] [opensaf:tickets] #323 amf: Reboot of the node is not happening when amfnd is killed.
Tested on CS #4733, node reboots. --- ** [tickets:#323] amf: Reboot of the node is not happening when amfnd is killed.** **Status:** not-reproducible **Created:** Fri May 24, 2013 09:14 AM UTC by Praveen **Last Updated:** Mon Dec 09, 2013 05:11 PM UTC **Owner:** Nagendra Kumar Migrated from http://devel.opensaf.org/ticket/2195. Setup: RHEL 6.0 VM setup. The transport used is TCP. Testing is done on changeset 2775.n Scenario: == Observed that when amfnd is killed on the active controller, the node did not go for reboot. From /var/log/messages: = Sep 28 00:37:35 SLOT_1 root: killing osafamfnd from invoke_failover.sh Sep 28 00:37:35 SLOT_1 osafclmd[1528]: AMF Node Director is down, terminate this process Sep 28 00:37:35 SLOT_1 app_comp: AMF Node Director is down, terminate this process Sep 28 00:37:35 SLOT_1 osafntfd[1517]: AMF Node Director is down, terminate this process Sep 28 00:37:35 SLOT_1 osaflogd[1506]: AMF Node Director is down, terminate this process Sep 28 00:37:35 SLOT_1 osafrded[1456]: AMF Node Director is down, terminate this process Sep 28 00:37:35 SLOT_1 osaffmd[1467]: AMF Node Director is down, terminate this process Sep 28 00:37:35 SLOT_1 osafevtd[1750]: AMF Node Director is down, terminate this process Sep 28 00:37:35 SLOT_1 osafckptnd[1736]: AMF Node Director is down, terminate this process Sep 28 00:37:36 SLOT_1 osafsmfd[1720]: AMF Node Director is down, terminate this process Sep 28 00:37:36 SLOT_1 osafmsgnd[1715]: AMF Node Director is down, terminate this process Sep 28 00:37:36 SLOT_1 osaflcknd[1691]: AMF Node Director is down, terminate this process Sep 28 00:37:36 SLOT_1 osafmsgd[1688]: AMF Node Director is down, terminate this process Sep 28 00:37:36 SLOT_1 osafsmfnd[1666]: AMF Node Director is down, terminate this process Sep 28 00:37:36 SLOT_1 osafimmd[1477]: AMF Node Director is down, terminate this process Sep 28 00:37:36 SLOT_1 osaflckd[1644]: AMF Node Director is down, terminate this process Sep 28 00:37:36 SLOT_1 osafimmnd[1488]: AMF Node Director is down, terminate this process Sep 28 00:37:36 SLOT_1 osafamfwd[1618]: Rebooting OpenSAF NodeId? = 0 EE Name = No EE Mapped, Reason: AMF unexpectedly crashed Sep 28 00:37:40 SLOT_1 osafamfd[1549]: avd_mds_send: failed 2, to 13@2010f061a Sep 28 00:37:40 SLOT_1 osafamfd[1549]: avd_tmr_snd_hb_evh failed to send HB msg Sep 28 00:37:50 SLOT_1 osafamfd[1549]: avd_mds_send: failed 2, to 13@2010f061a Sep 28 00:37:50 SLOT_1 osafamfd[1549]: avd_tmr_snd_hb_evh failed to send HB msg Sep 28 00:38:00 SLOT_1 osafamfd[1549]: avd_mds_send: failed 2, to 13@2010f061a Sep 28 00:38:00 SLOT_1 osafamfd[1549]: avd_tmr_snd_hb_evh failed to send HB msg Sep 28 00:38:10 SLOT_1 osafamfd[1549]: avd_mds_send: failed 2, to 13@2010f061a Sep 28 00:38:10 SLOT_1 osafamfd[1549]: avd_tmr_snd_hb_evh failed to send HB msg Sep 28 00:38:21 SLOT_1 osafamfd[1549]: avd_mds_send: failed 2, to 13@2010f061a Sep 28 00:38:21 SLOT_1 osafamfd[1549]: avd_tmr_snd_hb_evh failed to send HB msg Sep 28 00:38:31 SLOT_1 osafamfwd[1618]: TIMEOUT receiving AMF health check request, generating core for amfnd Sep 28 00:38:31 SLOT_1 osafamfwd[1618]: Last received healthcheck cnt=51 at Wed Sep 28 00:37:31 2011 Sep 28 00:38:31 SLOT_1 osafamfwd[1618]: ordering system reboot == Amfnd, Immnd traces are of huge size and hence not attaching them. Changed 20 months ago by hafe You are running OpenSAF as the opensaf user and you haven't given the opensaf user sudo permission for the needed commands. But agree that we need to log this issue to make it clear that's the problem. Basically OpenSAF needs better logs in the opensaf_reboot script as well in the opensaf_reboot function. Changed 19 months ago by surya ■milestone changed from 4.2.0.GA to 4.2.1 Changed 19 months ago by surya ■status changed from new to closed ■resolution set to duplicate Duplicate of 2106 TICKET Changed 18 months ago by manu ■status changed from closed to reopened ■resolutionduplicate deleted ■description modified (diff) On SLES11 64bit PC setup, with changeset 3065, observed that after killing amfnd, node is not going for reboot. Changed 13 months ago by ehsjoar ■milestone changed from 4.2.1 to future_releases --- 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.-- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how
[tickets] [opensaf:tickets] #397 AMF logs are not unique
Hi Hans, We can proceed if you can provide some information related to this ticket ? --- ** [tickets:#397] AMF logs are not unique** **Status:** unassigned **Created:** Fri May 31, 2013 05:17 AM UTC by Nagendra Kumar **Last Updated:** Fri Aug 30, 2013 10:18 AM UTC **Owner:** nobody Migrated from http://devel.opensaf.org/ticket/2614 Have seen a system where amfd logs XXX' does not exist in model during initial read of configuration from IMM. And that XXX object should not AMF look for in the first place! It was of the wrong class (non AMF) --- 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.-- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #332 amf: Locking of SU causes SI assignments stuck in quiesced state.
- **status**: accepted -- not-reproducible - **Milestone**: future -- 4.4.FC --- ** [tickets:#332] amf: Locking of SU causes SI assignments stuck in quiesced state.** **Status:** not-reproducible **Created:** Fri May 24, 2013 10:01 AM UTC by Praveen **Last Updated:** Tue Dec 17, 2013 05:56 AM UTC **Owner:** Praveen Migrated from http://devel.opensaf.org/ticket/2816. changeset : 3730 model : TwoN. setup : Three node setup. configuration : 1SG,5SUs,5SIs,SU1 has 2 comps whereas SU2 to SU5 has 3comps each. 3CSIs in each SI csi-csi deps configured in SI1 and SI5 as CSI1-CSI2-CSI3 ( chain ) si-si deps configured as SI1-SI2-SI3-SI4 SaAmfCSIAttribute is set for all the CSIs. All SIs are initially in locked state and SUs are in lock-in. SU1 mapped to SC-1 SU2 mapped to SC-2 SU3-SU5 mapped to PL-3 Steps performed on payload node: 1. Bring up the model. 2. Unlock-in and unlock all the SUs 3. Unlock all the SIs. 4. Now lock the SU1 as amf-adm lock SU1 DN Step 4 will (alarm) timeout. But lock of SU1 succeeds. SU2 becomes active for all SIs. SU1's assignments remain in Quiesced state. Its console trace # amf-adm lock safSu=SU1,safSg=SGONE,safApp=TWONAPP # error - command timed out (alarm) State of SU1 : safSu=SU1,safSg=SGONE,safApp=TWONAPP saAmfSUAdminState=UNLOCKED(1) saAmfSUOperState=ENABLED(1) saAmfSUPresenceState=INSTANTIATED(3) saAmfSUReadinessState=IN-SERVICE(2) SUSI assignment states: /etc/init.d/opensafd status safSISU=safSu=SU1\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI1,safApp=TWONAPP saAmfSISUHAState=QUIESCED(3) safSISU=safSu=SU2\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI1,safApp=TWONAPP saAmfSISUHAState=ACTIVE(1) safSISU=safSu=SU1\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI2,safApp=TWONAPP saAmfSISUHAState=QUIESCED(3) safSISU=safSu=SU1\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI3,safApp=TWONAPP saAmfSISUHAState=QUIESCED(3) safSISU=safSu=SU2\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI2,safApp=TWONAPP saAmfSISUHAState=ACTIVE(1) safSISU=safSu=SU1\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI4,safApp=TWONAPP saAmfSISUHAState=QUIESCED(3) safSISU=safSu=SU2\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI3,safApp=TWONAPP saAmfSISUHAState=ACTIVE(1) safSISU=safSu=SU1\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI5,safApp=TWONAPP saAmfSISUHAState=QUIESCED(3) safSISU=safSu=SU2\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI4,safApp=TWONAPP saAmfSISUHAState=ACTIVE(1) safSISU=safSu=SU2\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI5,safApp=TWONAPP saAmfSISUHAState=ACTIVE(1) /var/log/messages of SC-1 ( standby cntrlr) Sep 21 18:01:39 SLES11-SLOT-2 osafamfnd[6166]: NO Assigning 'safSi=TWONSI5,safApp=TWONAPP' QUIESCED to 'safSu=SU1,safSg=SGONE,safApp=TWONAPP' Sep 21 18:01:39 SLES11-SLOT-2 osafamfnd[6166]: NO Assigned 'safSi=TWONSI4,safApp=TWONAPP' QUIESCED to 'safSu=SU1,safSg=SGONE,safApp=TWONAPP' Sep 21 18:01:39 SLES11-SLOT-2 osafamfnd[6166]: NO Assigned 'safSi=TWONSI5,safApp=TWONAPP' QUIESCED to 'safSu=SU1,safSg=SGONE,safApp=TWONAPP' Sep 21 18:01:39 SLES11-SLOT-2 osafamfnd[6166]: NO Assigning 'safSi=TWONSI3,safApp=TWONAPP' QUIESCED to 'safSu=SU1,safSg=SGONE,safApp=TWONAPP' Sep 21 18:01:39 SLES11-SLOT-2 osafamfnd[6166]: NO Assigned 'safSi=TWONSI3,safApp=TWONAPP' QUIESCED to 'safSu=SU1,safSg=SGONE,safApp=TWONAPP' Sep 21 18:01:39 SLES11-SLOT-2 osafamfnd[6166]: NO Assigning 'safSi=TWONSI2,safApp=TWONAPP' QUIESCED to 'safSu=SU1,safSg=SGONE,safApp=TWONAPP' Sep 21 18:01:39 SLES11-SLOT-2 osafamfnd[6166]: NO Assigned 'safSi=TWONSI2,safApp=TWONAPP' QUIESCED to 'safSu=SU1,safSg=SGONE,safApp=TWONAPP' Sep 21 18:01:39 SLES11-SLOT-2 osafamfnd[6166]: NO Assigning 'safSi=TWONSI1,safApp=TWONAPP' QUIESCED to 'safSu=SU1,safSg=SGONE,safApp=TWONAPP' Sep 21 18:01:39 SLES11-SLOT-2 osafamfnd[6166]: NO Assigned 'safSi=TWONSI1,safApp=TWONAPP' QUIESCED to 'safSu=SU1,safSg=SGONE,safApp=TWONAPP' Sep 21 18:01:39 SLES11-SLOT-2 osafamfnd[6166]: NO Removing 'all SIs' from 'safSu=SU1,safSg=SGONE,safApp=TWONAPP' /var/log/messages of SC-2( active ctrlr ) Sep 21 18:01:31 SLES11-SLOT-2 osafamfnd[17092]: NO Assigning 'safSi=TWONSI1,safApp=TWONAPP' ACTIVE to 'safSu=SU2,safSg=SGONE,safApp=TWONAPP' Sep 21 18:01:31 SLES11-SLOT-2 osafamfnd[17092]: NO Assigned 'safSi=TWONSI1,safApp=TWONAPP' ACTIVE to 'safSu=SU2,safSg=SGONE,safApp=TWONAPP' Sep 21 18:01:31 SLES11-SLOT-2 osafamfnd[17092]: NO Assigning 'safSi=TWONSI5,safApp=TWONAPP' ACTIVE to 'safSu=SU2,safSg=SGONE,safApp=TWONAPP' Sep 21 18:01:31 SLES11-SLOT-2 osafamfnd[17092]: NO Assigned 'safSi=TWONSI5,safApp=TWONAPP' ACTIVE to 'safSu=SU2,safSg=SGONE,safApp=TWONAPP' Sep 21 18:01:31 SLES11-SLOT-2 osafamfnd[17092]: NO Assigning 'safSi=TWONSI2,safApp=TWONAPP' ACTIVE to 'safSu=SU2,safSg=SGONE,safApp=TWONAPP' Sep 21 18:01:31 SLES11-SLOT-2 osafamfnd[17092]: NO Assigned 'safSi=TWONSI2,safApp=TWONAPP' ACTIVE to 'safSu=SU2,safSg=SGONE,safApp=TWONAPP' Sep 21 18:01:31 SLES11-SLOT-2
[tickets] [opensaf:tickets] #332 amf: Locking of SU causes SI assignments stuck in quiesced state.
This issue is no longer reproducible on changeset: 4737:0caa487a99d3. Attached 332.tgz contains the traces after successfully verifying it. Configuration provided by submitter was used for verification. Please reopen it if observed again. --- ** [tickets:#332] amf: Locking of SU causes SI assignments stuck in quiesced state.** **Status:** not-reproducible **Created:** Fri May 24, 2013 10:01 AM UTC by Praveen **Last Updated:** Tue Dec 17, 2013 05:56 AM UTC **Owner:** Praveen Migrated from http://devel.opensaf.org/ticket/2816. changeset : 3730 model : TwoN. setup : Three node setup. configuration : 1SG,5SUs,5SIs,SU1 has 2 comps whereas SU2 to SU5 has 3comps each. 3CSIs in each SI csi-csi deps configured in SI1 and SI5 as CSI1-CSI2-CSI3 ( chain ) si-si deps configured as SI1-SI2-SI3-SI4 SaAmfCSIAttribute is set for all the CSIs. All SIs are initially in locked state and SUs are in lock-in. SU1 mapped to SC-1 SU2 mapped to SC-2 SU3-SU5 mapped to PL-3 Steps performed on payload node: 1. Bring up the model. 2. Unlock-in and unlock all the SUs 3. Unlock all the SIs. 4. Now lock the SU1 as amf-adm lock SU1 DN Step 4 will (alarm) timeout. But lock of SU1 succeeds. SU2 becomes active for all SIs. SU1's assignments remain in Quiesced state. Its console trace # amf-adm lock safSu=SU1,safSg=SGONE,safApp=TWONAPP # error - command timed out (alarm) State of SU1 : safSu=SU1,safSg=SGONE,safApp=TWONAPP saAmfSUAdminState=UNLOCKED(1) saAmfSUOperState=ENABLED(1) saAmfSUPresenceState=INSTANTIATED(3) saAmfSUReadinessState=IN-SERVICE(2) SUSI assignment states: /etc/init.d/opensafd status safSISU=safSu=SU1\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI1,safApp=TWONAPP saAmfSISUHAState=QUIESCED(3) safSISU=safSu=SU2\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI1,safApp=TWONAPP saAmfSISUHAState=ACTIVE(1) safSISU=safSu=SU1\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI2,safApp=TWONAPP saAmfSISUHAState=QUIESCED(3) safSISU=safSu=SU1\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI3,safApp=TWONAPP saAmfSISUHAState=QUIESCED(3) safSISU=safSu=SU2\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI2,safApp=TWONAPP saAmfSISUHAState=ACTIVE(1) safSISU=safSu=SU1\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI4,safApp=TWONAPP saAmfSISUHAState=QUIESCED(3) safSISU=safSu=SU2\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI3,safApp=TWONAPP saAmfSISUHAState=ACTIVE(1) safSISU=safSu=SU1\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI5,safApp=TWONAPP saAmfSISUHAState=QUIESCED(3) safSISU=safSu=SU2\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI4,safApp=TWONAPP saAmfSISUHAState=ACTIVE(1) safSISU=safSu=SU2\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI5,safApp=TWONAPP saAmfSISUHAState=ACTIVE(1) /var/log/messages of SC-1 ( standby cntrlr) Sep 21 18:01:39 SLES11-SLOT-2 osafamfnd[6166]: NO Assigning 'safSi=TWONSI5,safApp=TWONAPP' QUIESCED to 'safSu=SU1,safSg=SGONE,safApp=TWONAPP' Sep 21 18:01:39 SLES11-SLOT-2 osafamfnd[6166]: NO Assigned 'safSi=TWONSI4,safApp=TWONAPP' QUIESCED to 'safSu=SU1,safSg=SGONE,safApp=TWONAPP' Sep 21 18:01:39 SLES11-SLOT-2 osafamfnd[6166]: NO Assigned 'safSi=TWONSI5,safApp=TWONAPP' QUIESCED to 'safSu=SU1,safSg=SGONE,safApp=TWONAPP' Sep 21 18:01:39 SLES11-SLOT-2 osafamfnd[6166]: NO Assigning 'safSi=TWONSI3,safApp=TWONAPP' QUIESCED to 'safSu=SU1,safSg=SGONE,safApp=TWONAPP' Sep 21 18:01:39 SLES11-SLOT-2 osafamfnd[6166]: NO Assigned 'safSi=TWONSI3,safApp=TWONAPP' QUIESCED to 'safSu=SU1,safSg=SGONE,safApp=TWONAPP' Sep 21 18:01:39 SLES11-SLOT-2 osafamfnd[6166]: NO Assigning 'safSi=TWONSI2,safApp=TWONAPP' QUIESCED to 'safSu=SU1,safSg=SGONE,safApp=TWONAPP' Sep 21 18:01:39 SLES11-SLOT-2 osafamfnd[6166]: NO Assigned 'safSi=TWONSI2,safApp=TWONAPP' QUIESCED to 'safSu=SU1,safSg=SGONE,safApp=TWONAPP' Sep 21 18:01:39 SLES11-SLOT-2 osafamfnd[6166]: NO Assigning 'safSi=TWONSI1,safApp=TWONAPP' QUIESCED to 'safSu=SU1,safSg=SGONE,safApp=TWONAPP' Sep 21 18:01:39 SLES11-SLOT-2 osafamfnd[6166]: NO Assigned 'safSi=TWONSI1,safApp=TWONAPP' QUIESCED to 'safSu=SU1,safSg=SGONE,safApp=TWONAPP' Sep 21 18:01:39 SLES11-SLOT-2 osafamfnd[6166]: NO Removing 'all SIs' from 'safSu=SU1,safSg=SGONE,safApp=TWONAPP' /var/log/messages of SC-2( active ctrlr ) Sep 21 18:01:31 SLES11-SLOT-2 osafamfnd[17092]: NO Assigning 'safSi=TWONSI1,safApp=TWONAPP' ACTIVE to 'safSu=SU2,safSg=SGONE,safApp=TWONAPP' Sep 21 18:01:31 SLES11-SLOT-2 osafamfnd[17092]: NO Assigned 'safSi=TWONSI1,safApp=TWONAPP' ACTIVE to 'safSu=SU2,safSg=SGONE,safApp=TWONAPP' Sep 21 18:01:31 SLES11-SLOT-2 osafamfnd[17092]: NO Assigning 'safSi=TWONSI5,safApp=TWONAPP' ACTIVE to 'safSu=SU2,safSg=SGONE,safApp=TWONAPP' Sep 21 18:01:31 SLES11-SLOT-2 osafamfnd[17092]: NO Assigned 'safSi=TWONSI5,safApp=TWONAPP' ACTIVE to 'safSu=SU2,safSg=SGONE,safApp=TWONAPP' Sep 21 18:01:31 SLES11-SLOT-2 osafamfnd[17092]: NO Assigning 'safSi=TWONSI2,safApp=TWONAPP' ACTIVE to 'safSu=SU2,safSg=SGONE,safApp=TWONAPP' Sep 21 18:01:31
[tickets] [opensaf:tickets] #362 AMF saflogs UNKNOWN...
- **status**: unassigned -- review - **assigned_to**: Nagendra Kumar - **Milestone**: future -- 4.2.5 --- ** [tickets:#362] AMF saflogs UNKNOWN...** **Status:** review **Created:** Fri May 31, 2013 03:28 AM UTC by Nagendra Kumar **Last Updated:** Thu Aug 29, 2013 11:26 AM UTC **Owner:** Nagendra Kumar Migrated from http://devel.opensaf.org/ticket/1794 AMF logs stuff like: 82 13:30:20 03/11/2011 NO safApp=safAmfService safSi=SI3,safApp=AmfDemo? assigned to safSu=SU1,safSg=AmfDemo?,safApp=AmfDemo? HA State UNKNOWN = QUIESCED 83 13:30:20 03/11/2011 NO safApp=safAmfService safSi=SI4,safApp=AmfDemo? assigned to safSu=SU1,safSg=AmfDemo?,safApp=AmfDemo? HA State UNKNOWN = QUIESCED into SAF LOG. The state isn't really unknown. It is just a matter refactoring the code. --- 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.-- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #616 latest staging does not compile
- **status**: unassigned -- accepted - **assigned_to**: Praveen - **Milestone**: future -- 4.4.FC --- ** [tickets:#616] latest staging does not compile** **Status:** accepted **Created:** Tue Nov 05, 2013 12:40 PM UTC by Sirisha Alla **Last Updated:** Tue Nov 05, 2013 12:40 PM UTC **Owner:** Praveen current default staging(cs 4585) does not compile with the following error g++ -DHAVE_CONFIG_H -I. -I../../../../.. -DSA_CLM_B01=1 -I../../../../../osaf/libs/saf/include -I../../../../../osaf/libs/core/include -I../../../../../osaf/libs/core/leap/include -I../../../../../osaf/libs/core/mds/include -I../../../../../osaf/libs/core/common/include -I../../../../../osaf/libs/common/amf/include -I../../../../../osaf/services/saf/amf/amfnd/include -I../../../../../osaf/libs/common/immsv/include -Wall -fno-strict-aliasing -Werror -fPIC -D__STDC_FORMAT_MACROS -O2 -g -m64 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -MT osafamfnd-mbcsv.o -MD -MP -MF .deps/osafamfnd-mbcsv.Tpo -c -o osafamfnd-mbcsv.o `test -f 'mbcsv.cc' || echo './'`mbcsv.cc cc1plus: warnings being treated as errors mbcsv.cc: In function ‘uint32_t avnd_evt_avd_role_change_evh(AVND_CB*, AVND_EVT*)’: mbcsv.cc:1293: error: comparison between signed and unsigned integer expressions make[8]: *** [osafamfnd-mbcsv.o] Error 1 make[8]: Leaving directory `/home/sirisha/staging_nov5th/rpms/BUILD/opensaf-4.4.M0/osaf/services/saf/amf/amfnd' make[7]: *** [all-recursive] Error 1 make[7]: Leaving directory `/home/sirisha/staging_nov5th/rpms/BUILD/opensaf-4.4.M0/osaf/services/saf/amf/amfnd' make[6]: *** [all-recursive] Error 1 make[6]: Leaving directory `/home/sirisha/staging_nov5th/rpms/BUILD/opensaf-4.4.M0/osaf/services/saf/amf' make[5]: *** [all-recursive] Error 1 make[5]: Leaving directory `/home/sirisha/staging_nov5th/rpms/BUILD/opensaf-4.4.M0/osaf/services/saf' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/home/sirisha/staging_nov5th/rpms/BUILD/opensaf-4.4.M0/osaf/services' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/sirisha/staging_nov5th/rpms/BUILD/opensaf-4.4.M0/osaf' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/sirisha/staging_nov5th/rpms/BUILD/opensaf-4.4.M0' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/sirisha/staging_nov5th/rpms/BUILD/opensaf-4.4.M0' error: Bad exit status from /home/sirisha/staging_nov5th/rpms/tmp/rpm-tmp.10997 (%build) RPM build errors: Bad exit status from /home/sirisha/staging_nov5th/rpms/tmp/rpm-tmp.10997 (%build) make: *** [rpm] Error 1 --- 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.-- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #616 latest staging does not compile
Will provide fix to get rid of compiler warning only. Not going to change the data type. --- ** [tickets:#616] latest staging does not compile** **Status:** accepted **Created:** Tue Nov 05, 2013 12:40 PM UTC by Sirisha Alla **Last Updated:** Tue Nov 05, 2013 12:40 PM UTC **Owner:** Praveen current default staging(cs 4585) does not compile with the following error g++ -DHAVE_CONFIG_H -I. -I../../../../.. -DSA_CLM_B01=1 -I../../../../../osaf/libs/saf/include -I../../../../../osaf/libs/core/include -I../../../../../osaf/libs/core/leap/include -I../../../../../osaf/libs/core/mds/include -I../../../../../osaf/libs/core/common/include -I../../../../../osaf/libs/common/amf/include -I../../../../../osaf/services/saf/amf/amfnd/include -I../../../../../osaf/libs/common/immsv/include -Wall -fno-strict-aliasing -Werror -fPIC -D__STDC_FORMAT_MACROS -O2 -g -m64 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -MT osafamfnd-mbcsv.o -MD -MP -MF .deps/osafamfnd-mbcsv.Tpo -c -o osafamfnd-mbcsv.o `test -f 'mbcsv.cc' || echo './'`mbcsv.cc cc1plus: warnings being treated as errors mbcsv.cc: In function ‘uint32_t avnd_evt_avd_role_change_evh(AVND_CB*, AVND_EVT*)’: mbcsv.cc:1293: error: comparison between signed and unsigned integer expressions make[8]: *** [osafamfnd-mbcsv.o] Error 1 make[8]: Leaving directory `/home/sirisha/staging_nov5th/rpms/BUILD/opensaf-4.4.M0/osaf/services/saf/amf/amfnd' make[7]: *** [all-recursive] Error 1 make[7]: Leaving directory `/home/sirisha/staging_nov5th/rpms/BUILD/opensaf-4.4.M0/osaf/services/saf/amf/amfnd' make[6]: *** [all-recursive] Error 1 make[6]: Leaving directory `/home/sirisha/staging_nov5th/rpms/BUILD/opensaf-4.4.M0/osaf/services/saf/amf' make[5]: *** [all-recursive] Error 1 make[5]: Leaving directory `/home/sirisha/staging_nov5th/rpms/BUILD/opensaf-4.4.M0/osaf/services/saf' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/home/sirisha/staging_nov5th/rpms/BUILD/opensaf-4.4.M0/osaf/services' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/sirisha/staging_nov5th/rpms/BUILD/opensaf-4.4.M0/osaf' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/sirisha/staging_nov5th/rpms/BUILD/opensaf-4.4.M0' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/sirisha/staging_nov5th/rpms/BUILD/opensaf-4.4.M0' error: Bad exit status from /home/sirisha/staging_nov5th/rpms/tmp/rpm-tmp.10997 (%build) RPM build errors: Bad exit status from /home/sirisha/staging_nov5th/rpms/tmp/rpm-tmp.10997 (%build) make: *** [rpm] Error 1 --- 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.-- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #256 amf: AMF should not allow saAmfSUAdminState set to Shutting_down in the initial config
Validate at CS#4733. Amf is not allowing SU to be created in shutting down state We get following error for saAmfSUAdminState = 4: PM_SC-180:/home/nagu/views/staging # immcfg -c SaAmfSU safSu=SU4,safSg=AmfDemo,safApp=AmfDemo1 -a saAmfSUType=safVersion=1,safSuType=AmfDemo1 -a saAmfSURank=3 -a saAmfSUHostNodeOrNodeGroup=safAmfNode=SC-1,safAmfCluster=myAmfCluster -a saAmfSUAdminState=4 error - saImmOmCcbApply FAILED: SA_AIS_ERR_FAILED_OPERATION (21) OI reports: saAmfSUAdminState must be LOCKED_INSTANTIATION(3) for dynamically created SUs --- ** [tickets:#256] amf: AMF should not allow saAmfSUAdminState set to Shutting_down in the initial config** **Status:** invalid **Created:** Thu May 16, 2013 07:16 AM UTC by Praveen **Last Updated:** Thu May 16, 2013 07:16 AM UTC **Owner:** Nagendra Kumar Migrated from http://devel.opensaf.org/ticket/2702. AMF is allowing creation of SU with saAmfSUAdminState set to Shutting_down.Shutting_down is a transient state, so while creating SU, AMF should not allow saAmfSUAdminState set to Shutting_down. --- 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.-- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #616 latest staging does not compile
- **status**: accepted -- review --- ** [tickets:#616] latest staging does not compile** **Status:** review **Created:** Tue Nov 05, 2013 12:40 PM UTC by Sirisha Alla **Last Updated:** Tue Dec 17, 2013 06:16 AM UTC **Owner:** Praveen current default staging(cs 4585) does not compile with the following error g++ -DHAVE_CONFIG_H -I. -I../../../../.. -DSA_CLM_B01=1 -I../../../../../osaf/libs/saf/include -I../../../../../osaf/libs/core/include -I../../../../../osaf/libs/core/leap/include -I../../../../../osaf/libs/core/mds/include -I../../../../../osaf/libs/core/common/include -I../../../../../osaf/libs/common/amf/include -I../../../../../osaf/services/saf/amf/amfnd/include -I../../../../../osaf/libs/common/immsv/include -Wall -fno-strict-aliasing -Werror -fPIC -D__STDC_FORMAT_MACROS -O2 -g -m64 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -MT osafamfnd-mbcsv.o -MD -MP -MF .deps/osafamfnd-mbcsv.Tpo -c -o osafamfnd-mbcsv.o `test -f 'mbcsv.cc' || echo './'`mbcsv.cc cc1plus: warnings being treated as errors mbcsv.cc: In function ‘uint32_t avnd_evt_avd_role_change_evh(AVND_CB*, AVND_EVT*)’: mbcsv.cc:1293: error: comparison between signed and unsigned integer expressions make[8]: *** [osafamfnd-mbcsv.o] Error 1 make[8]: Leaving directory `/home/sirisha/staging_nov5th/rpms/BUILD/opensaf-4.4.M0/osaf/services/saf/amf/amfnd' make[7]: *** [all-recursive] Error 1 make[7]: Leaving directory `/home/sirisha/staging_nov5th/rpms/BUILD/opensaf-4.4.M0/osaf/services/saf/amf/amfnd' make[6]: *** [all-recursive] Error 1 make[6]: Leaving directory `/home/sirisha/staging_nov5th/rpms/BUILD/opensaf-4.4.M0/osaf/services/saf/amf' make[5]: *** [all-recursive] Error 1 make[5]: Leaving directory `/home/sirisha/staging_nov5th/rpms/BUILD/opensaf-4.4.M0/osaf/services/saf' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/home/sirisha/staging_nov5th/rpms/BUILD/opensaf-4.4.M0/osaf/services' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/sirisha/staging_nov5th/rpms/BUILD/opensaf-4.4.M0/osaf' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/sirisha/staging_nov5th/rpms/BUILD/opensaf-4.4.M0' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/sirisha/staging_nov5th/rpms/BUILD/opensaf-4.4.M0' error: Bad exit status from /home/sirisha/staging_nov5th/rpms/tmp/rpm-tmp.10997 (%build) RPM build errors: Bad exit status from /home/sirisha/staging_nov5th/rpms/tmp/rpm-tmp.10997 (%build) make: *** [rpm] Error 1 --- 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.-- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #291 Admin repaired operation is not instantiating the SU from instantiation-failed state
- **status**: unassigned -- invalid - **assigned_to**: Nagendra Kumar --- ** [tickets:#291] Admin repaired operation is not instantiating the SU from instantiation-failed state** **Status:** invalid **Created:** Wed May 22, 2013 11:20 AM UTC by Nagendra Kumar **Last Updated:** Wed May 22, 2013 11:20 AM UTC **Owner:** Nagendra Kumar Migrated from http://devel.opensaf.org/ticket/2518 Changeset: 3384 A wrong instantiation command path caused the component and the enclosing SU to move to instantiation-failed state. In this condition, after correcting the path and performing an admin-repaired operation is not re-instantiating the SU eventhough its admin-state is unlocked. The similar case is observed even when the node is rebooted with the SU is in instantiation-failed state. The following is the flow: SU state: safSu=testSu2,safSg=testSg,safApp=testApp saAmfSUAdminState=LOCKED-INSTANTIATION(3) saAmfSUOperState=ENABLED(1) saAmfSUPresenceState=UNINSTANTIATED(1) saAmfSUReadinessState=OUT-OF-SERVICE(1) Unlock-in operation on the SU: amf-adm unlock-in safSu=testSu2,safSg=testSg,safApp=testApp error - saImmOmAdminOperationInvoke_2 admin-op RETURNED: SA_AIS_ERR_REPAIR_PENDING (29) /var/log/messages: Mar 1 19:36:23 SLES11-SLOT-1 osafamfnd[2917]: 'safSu=testSu2,safSg=testSg,safApp=testApp' Presence State UNINSTANTIATED = INSTANTIATING Mar 1 19:36:23 SLES11-SLOT-1 osafamfnd[3865]: Could not stat /opt/goahead/tetware/framework/amf_comp_script - No such file or directory Mar 1 19:36:23 SLES11-SLOT-1 osafamfnd[2917]: Instantiation of 'safComp=testComp2,safSu=testSu2,safSg=testSg,safApp=testApp' failed Mar 1 19:36:23 SLES11-SLOT-1 osafamfnd[2917]: Reason:'Exec of script failed (script not readable or path wrong)' Mar 1 19:36:23 SLES11-SLOT-1 osafamfnd[2917]: CLC CLI script:'/opt/goahead/tetware/framework/amf_comp_script instantiate' Mar 1 19:36:23 SLES11-SLOT-1 osafamfnd[3866]: Could not stat /opt/goahead/tetware/framework/amf_comp_script - No such file or directory Mar 1 19:36:23 SLES11-SLOT-1 osafamfnd[2917]: Cleanup of 'safComp=testComp2,safSu=testSu2,safSg=testSg,safApp=testApp' failed Mar 1 19:36:23 SLES11-SLOT-1 osafamfnd[2917]: Reason:'Exec of script failed (script not readable or path wrong)' Mar 1 19:36:23 SLES11-SLOT-1 osafamfnd[2917]: CLC CLI script:'/opt/goahead/tetware/framework/amf_comp_script cleanup' Mar 1 19:36:23 SLES11-SLOT-1 osafamfnd[2917]: 'safSu=testSu2,safSg=testSg,safApp=testApp' Presence State INSTANTIATING = INSTANTIATION_FAILED SU state: safSu=testSu2,safSg=testSg,safApp=testApp saAmfSUAdminState=LOCKED(2) saAmfSUOperState=DISABLED(2) saAmfSUPresenceState=INSTANTIATION-FAILED(6) saAmfSUReadinessState=OUT-OF-SERVICE(1) Admin Repaired Operation: amf-adm repaired safSu=testSu2,safSg=testSg,safApp=testApp /var/log/messages: Mar 1 19:38:51 SLES11-SLOT-1 osafamfnd[2917]: 'safSu=testSu2,safSg=testSg,safApp=testApp' Presence State INSTANTIATION_FAILED = UNINSTANTIATED Final SU state even after node reboot: safSu=testSu2,safSg=testSg,safApp=testApp saAmfSUAdminState=LOCKED(2) saAmfSUOperState=ENABLED(1) saAmfSUPresenceState=UNINSTANTIATED(1) saAmfSUReadinessState=OUT-OF-SERVICE(1) Changed 15 months ago by pavan ¶ ■description modified (diff) follow-up: ↓ 3 Changed 15 months ago by hafe ¶ I cannot reproduce this problem. It is working just fine for me. Please provide more syslogs and traces from when repaired is performed. Changed 15 months ago by pavan ■attachment 2518.tgz added in reply to: ↑ 2 Changed 15 months ago by pavan ¶ Replying to hafe: I cannot reproduce this problem. It is working just fine for me. Please provide more syslogs and traces from when repaired is performed. I added the zip file which includes amfd trace (of Active controller) and syslog, amfnd traces (on the node hosing the SU) To refer the logs, the timestamp for the admin repair operation is: Fri Mar 2 10:50:03 IST 2012 follow-up: ↓ 5 Changed 15 months ago by hafe ¶ Repair is not magic. You will have to repair the system before the admin op is performed. I cannot see anything wrong in the logs. Please redo the test and provide proper logs that indicate that there is a problem. in reply to: ↑ 4 ; follow-up: ↓ 6 Changed 15 months ago by pavan ¶ Replying to hafe: Repair is not magic. You will have to repair the system before the admin op is performed. I
[tickets] [opensaf:tickets] #291 Admin repaired operation is not instantiating the SU from instantiation-failed state
Validated at CS#4733, it works. Logs: Dec 17 12:04:03 PM_SC-180 osafamfnd[8708]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State UNINSTANTIATED = INSTANTIATING Dec 17 12:04:03 PM_SC-180 osafamfnd[9194]: Could not stat /opt/amf_demo/amf_demo_script - No such file or directory Dec 17 12:04:03 PM_SC-180 osafamfnd[8708]: NO Instantiation of 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' failed Dec 17 12:04:03 PM_SC-180 osafamfnd[8708]: NO Reason:'Exec of script failed (script not readable or path wrong)' Dec 17 12:04:03 PM_SC-180 osafamfnd[8708]: NO CLC CLI script:'/opt/amf_demo/amf_demo_script instantiate' Dec 17 12:04:03 PM_SC-180 osafamfnd[9195]: Could not stat /opt/amf_demo/amf_demo_script - No such file or directory Dec 17 12:04:03 PM_SC-180 osafamfnd[8708]: NO Cleanup of 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' failed Dec 17 12:04:03 PM_SC-180 osafamfnd[8708]: NO Reason:'Exec of script failed (script not readable or path wrong)' Dec 17 12:04:03 PM_SC-180 osafamfnd[8708]: NO CLC CLI script:'/opt/amf_demo/amf_demo_script cleanup' Dec 17 12:04:03 PM_SC-180 osafamfnd[8708]: WA 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State INSTANTIATING = TERMINATION_FAILED Dec 17 12:04:03 PM_SC-180 osafamfnd[8708]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State INSTANTIATING = TERMINATION_FAILED After repair: Dec 17 12:04:25 PM_SC-180 osafamfnd[8708]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State TERMINATION_FAILED = UNINSTANTIATED Dec 17 12:04:25 PM_SC-180 osafamfnd[8708]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State UNINSTANTIATED = INSTANTIATING Dec 17 12:04:25 PM_SC-180 amf_demo_script: Instantiate called instantiate ... Dec 17 12:04:25 PM_SC-180 amf_demo[9233]: 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' started Dec 17 12:04:25 PM_SC-180 osafamfnd[8708]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State INSTANTIATING = INSTANTIATED Dec 17 12:04:25 PM_SC-180 amf_demo[9233]: Registered with AMF --- ** [tickets:#291] Admin repaired operation is not instantiating the SU from instantiation-failed state** **Status:** invalid **Created:** Wed May 22, 2013 11:20 AM UTC by Nagendra Kumar **Last Updated:** Wed May 22, 2013 11:20 AM UTC **Owner:** Nagendra Kumar Migrated from http://devel.opensaf.org/ticket/2518 Changeset: 3384 A wrong instantiation command path caused the component and the enclosing SU to move to instantiation-failed state. In this condition, after correcting the path and performing an admin-repaired operation is not re-instantiating the SU eventhough its admin-state is unlocked. The similar case is observed even when the node is rebooted with the SU is in instantiation-failed state. The following is the flow: SU state: safSu=testSu2,safSg=testSg,safApp=testApp saAmfSUAdminState=LOCKED-INSTANTIATION(3) saAmfSUOperState=ENABLED(1) saAmfSUPresenceState=UNINSTANTIATED(1) saAmfSUReadinessState=OUT-OF-SERVICE(1) Unlock-in operation on the SU: amf-adm unlock-in safSu=testSu2,safSg=testSg,safApp=testApp error - saImmOmAdminOperationInvoke_2 admin-op RETURNED: SA_AIS_ERR_REPAIR_PENDING (29) /var/log/messages: Mar 1 19:36:23 SLES11-SLOT-1 osafamfnd[2917]: 'safSu=testSu2,safSg=testSg,safApp=testApp' Presence State UNINSTANTIATED = INSTANTIATING Mar 1 19:36:23 SLES11-SLOT-1 osafamfnd[3865]: Could not stat /opt/goahead/tetware/framework/amf_comp_script - No such file or directory Mar 1 19:36:23 SLES11-SLOT-1 osafamfnd[2917]: Instantiation of 'safComp=testComp2,safSu=testSu2,safSg=testSg,safApp=testApp' failed Mar 1 19:36:23 SLES11-SLOT-1 osafamfnd[2917]: Reason:'Exec of script failed (script not readable or path wrong)' Mar 1 19:36:23 SLES11-SLOT-1 osafamfnd[2917]: CLC CLI script:'/opt/goahead/tetware/framework/amf_comp_script instantiate' Mar 1 19:36:23 SLES11-SLOT-1 osafamfnd[3866]: Could not stat /opt/goahead/tetware/framework/amf_comp_script - No such file or directory Mar 1 19:36:23 SLES11-SLOT-1 osafamfnd[2917]: Cleanup of 'safComp=testComp2,safSu=testSu2,safSg=testSg,safApp=testApp' failed Mar 1 19:36:23 SLES11-SLOT-1 osafamfnd[2917]: Reason:'Exec of script failed (script not readable or path wrong)' Mar 1 19:36:23 SLES11-SLOT-1 osafamfnd[2917]: CLC CLI script:'/opt/goahead/tetware/framework/amf_comp_script cleanup' Mar 1 19:36:23 SLES11-SLOT-1 osafamfnd[2917]: 'safSu=testSu2,safSg=testSg,safApp=testApp' Presence State INSTANTIATING = INSTANTIATION_FAILED SU state: safSu=testSu2,safSg=testSg,safApp=testApp saAmfSUAdminState=LOCKED(2) saAmfSUOperState=DISABLED(2)
[tickets] [opensaf:tickets] #297 si-swap operation doesn't show status complete
- **status**: unassigned -- invalid - **assigned_to**: Nagendra Kumar --- ** [tickets:#297] si-swap operation doesn't show status complete** **Status:** invalid **Created:** Wed May 22, 2013 11:28 AM UTC by Nagendra Kumar **Last Updated:** Wed May 22, 2013 11:28 AM UTC **Owner:** Nagendra Kumar Migrated from http://devel.opensaf.org/ticket/2847 changeset : 3784 4.2.2rc1 model : 2n configuration : 1App,1SG,2SUs with 4comps each, 4SIs with 1 CSI each No si-si deps configured. SU1 is active, SU2 is standby. SU1 is mapped to pl-3 and SU2 to pl-4 SI-swap operation is performed using amf-adm utility. steps 1. perform si-swap op on SI1 2. Comp1 of SU1 is made to timeout the quiesced assignment. SU1 takes stanby and SU2 active assignments,but the status completion doesn't reflect in syslog of active controller console output: error - command timed out (alarm) /var/log/messages on SC-1: Oct 8 12:47:01 linux-xc76 osafamfd[3599]: safSi=SI1,safApp=test2nApp Swap initiated Oct 8 12:47:01 linux-xc76 osafamfd[3599]: Failed to modify assignment for 'safSu=SU1,safSg=SG,safApp=test2nApp' Oct 8 12:47:01 linux-xc76 osafamfd[3599]: avd_su_si_assign_evh:971 2 3 5 59 2030f Oct 8 12:47:01 linux-xc76 osafamfd[3599]: avd_su_si_assign_evh:971 Oct 8 12:47:01 linux-xc76 osafamfd[3599]: avd_su_si_assign_evh:971 safSu=SU1,safSg=SG,safApp=test2nApp --- 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.-- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
