[tickets] [opensaf:tickets] #2396 base: Use dlopen to avoid LSB violation
changeset: 8745:a4fce6b40ce5 user:Anders Widell date:Fri Mar 31 15:55:28 2017 +0200 summary: base: Fix GCC 6 compilation error [#2396] --- ** [tickets:#2396] base: Use dlopen to avoid LSB violation** **Status:** fixed **Milestone:** 5.2.RC2 **Created:** Thu Mar 23, 2017 02:59 PM UTC by Anders Widell **Last Updated:** Tue Mar 28, 2017 12:21 PM UTC **Owner:** Anders Widell Ticket [#2266] introduced a dependency towards the openssl library. This causes two problems: the first one is that this library is not part of LSB. The second (and related) one is that OpenSAF binaries built on one Linux distribution may fail to load on another Linux distribution, due to different names (versions) of this library. The suggested solution is to follow our earlier pattern and use dlopen() to open the library. If the library doesn't exist then the functionality will exhibit some default behaviour (e.g. the hash function will always return zero). --- 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.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2406 log: not finalize accessor handle when getting scAbsenceAllowed
- **status**: assigned --> review --- ** [tickets:#2406] log: not finalize accessor handle when getting scAbsenceAllowed** **Status:** review **Milestone:** 5.0.2 **Created:** Fri Mar 31, 2017 07:36 AM UTC by Vu Minh Nguyen **Last Updated:** Fri Mar 31, 2017 07:36 AM UTC **Owner:** Vu Minh Nguyen In `lgs_get_scAbsenceAllowed_attr()`, did not finalize IMM OM object accessor handle after done getting `scAbsenceAllowed`. --- 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.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2405 base: Use getdomainname() to build the FQDN
- **status**: review --> fixed - **Comment**: changeset: 8744:cd17b015441c user:Anders Widell date:Thu Mar 30 14:18:58 2017 +0200 summary: base: Use getdomainname() to build the FQDN [#2405] [staging:cd17b0] --- ** [tickets:#2405] base: Use getdomainname() to build the FQDN** **Status:** fixed **Milestone:** 5.2.RC2 **Created:** Thu Mar 30, 2017 11:10 AM UTC by Anders Widell **Last Updated:** Thu Mar 30, 2017 12:21 PM UTC **Owner:** Anders Widell Querying the DNS can potentially be very slow, especially in the case when the DNS servers are not responding e.g. due to a misconfiguration. Therefore, the proposed solution is to instead use gethostname() + getdomainname() to build the fully qualified domain name (FQDN) using locally stored information. The result from getdomainname() may not always be accurate so the long-term solution is probably to introduce a separate process/thread that can query the DNS in the background. --- 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.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2381 clmd: clm admin operation returns BAD_OP after rebooting node
- **status**: assigned --> accepted - **Milestone**: 5.0.2 --> next - **Comment**: Analysis: There seems problem with atleast one CLM clinet which resides on PL-3. CLM is unable to send any message to this client. 1) CLMD creates this client as standby: 2) Mar 15 13:47:47.080883 osafclmd [2763:src/clm/clmd/clms_evt.c:0140] TR client_id: 63 lookup failed Mar 15 13:47:47.080886 osafclmd [2763:src/clm/clmd/clms_evt.c:0250] >> clms_client_new: MDS dest 2030feebec01a Mar 15 13:47:47.080888 osafclmd [2763:src/clm/clmd/clms_evt.c:0277] << clms_client_new: client_id 63 2) When user performs admin operation, CLMD tries to send track callback for complete step to this client but mds returns failure: 3) Mar 15 14:32:10.759655 osafclmd [2763:src/clm/clmd/clms_util.c:1095] TR Client ID 63 ,track_flags=3 Mar 15 14:32:10.759658 osafclmd [2763:src/clm/clmd/clms_imm.c:1380] >> clms_prep_and_send_track Mar 15 14:32:10.759661 osafclmd [2763:src/clm/clmd/clms_util.c:0352] >> clms_nodedb_lookup Mar 15 14:32:10.759664 osafclmd [2763:src/clm/clmd/clms_util.c:0354] TR patricia tree size 4 Mar 15 14:32:10.759667 osafclmd [2763:src/clm/clmd/clms_util.c:0149] TR Node found 131343 Mar 15 14:32:10.759670 osafclmd [2763:src/clm/clmd/clms_util.c:0149] TR Node found 131599 Mar 15 14:32:10.759673 osafclmd [2763:src/clm/clmd/clms_util.c:0149] TR Node found 131855 Mar 15 14:32:10.759676 osafclmd [2763:src/clm/clmd/clms_util.c:0149] TR Node found 132111 Mar 15 14:32:10.759687 osafclmd [2763:src/clm/clmd/clms_util.c:0375] TR num_nd_changes 4 Mar 15 14:32:10.759689 osafclmd [2763:src/clm/clmd/clms_util.c:0376] << clms_nodedb_lookup Mar 15 14:32:10.759693 osafclmd [2763:src/clm/clmd/clms_mds.c:1494] >> clms_mds_msg_send Mar 15 14:32:10.759728 osafclmd [2763:src/clm/clmd/clms_mds.c:1525] IN mds send returned: 2 Mar 15 14:32:10.759732 osafclmd [2763:src/clm/clmd/clms_mds.c:1527] << clms_mds_msg_send Mar 15 14:32:10.759735 osafclmd [2763:src/clm/clmd/clms_imm.c:1439] TR callback msg send to clma failed 4) Before admin operation on PL-3, this node was restarted. There is no evidence of this client going down in clmd traces. 5) When unlock operation was performed, CLMD again could not send membeship status to this client and did not reply to IMM. Also admin op params are not reset.. Since admin operation params are not reset, no further admin operation are not allowed and getting timed out. --- ** [tickets:#2381] clmd: clm admin operation returns BAD_OP after rebooting node** **Status:** accepted **Milestone:** next **Created:** Thu Mar 16, 2017 07:30 AM UTC by Ritu Raj **Last Updated:** Thu Mar 16, 2017 09:01 AM UTC **Owner:** Praveen **Attachments:** - [active_clmd.tgz](https://sourceforge.net/p/opensaf/tickets/2381/attachment/active_clmd.tgz) (1.3 MB; application/x-compressed-tar) - [messages](https://sourceforge.net/p/opensaf/tickets/2381/attachment/messages) (1.9 MB; application/octet-stream) ###Environment details OS : Suse 64bit Changeset : 8701 ( 5.2.RC1) 4 nodes setup(2 controller and 2 payload) ###Summary clm admin operation returns SA_AIS_ERR_BAD_OPERATION after rebooting node ###Steps followed & Observed behaviour 1. Initially performed clm_lock operation on Payload (PL-3) and immediately restarted the same payload(PL-3) > init 6; exit 2. Later, performed clm_unlock operation on PL-3, and got message unlock operation got timed out but still node joined the cluster > SLES-SLOT1:~ # amf-adm unlock safNode=PL-3,safCluster=myClmCluster > Mar 15 14:35:20 SLES-SLOT1 osafclmd[2763]: ER clms_imm_node_unlock failed > Mar 15 14:35:20 SLES-SLOT1 osafamfd[2773]: NO Received node_up from 2030f: > msg_id 1 > Mar 15 14:35:20 SLES-SLOT1 osafamfd[2773]: NO Node 'PL-3' joined the cluster > Mar 15 14:35:20 SLES-SLOT1 osafimmnd[2733]: NO Implementer connected: 197 > (MsgQueueService131855) <0, 2030f> > error - command timed out (alarm) 3. After, that if clm_lock or unlock opeartion performed it returns 'SA_AIS_ERR_BAD_OPERATION' SLES-SLOT1:~ # amf-adm lock safNode=PL-3,safCluster=myClmCluster error - saImmOmAdminOperationInvoke_2 admin-op RETURNED: SA_AIS_ERR_BAD_OPERATION (20) > > SLES-SLOT1:~ # amf-adm unlock safNode=PL-3,safCluster=myClmCluster > error - saImmOmAdminOperationInvoke_2 admin-op RETURNED: > SA_AIS_ERR_BAD_OPERATION (20) Traces: >From the traces: Node PL-3 joined the cluster ~~~ Mar 15 14:35:20.373997 osafclmd [2763:src/clm/clmd/clms_imm.c:0939] >> clms_imm_admin_op_callback: Admin callback for nodename:safNode=PL-3,safCluster=myClmCluster, opId:1 Mar 15 14:35:20.374002 osafclmd [2763:src/clm/clmd/clms_util.c:0038] >> clms_node_get_by_name: name input safNode=PL-3,safCluster=myClmCluster length 36 Mar 15 14:35:20.374006 osafclmd [2763:src/clm/clmd/clms_util.c:0046] TR nodename after patricia tree get safNode=PL-3,safCluster=myClmCluster Mar 15 14:35:20.374009 osafclmd [2763:src/clm/clmd/clms_util.c:0049] << clms_node_get_by_name Mar 15 14:35:20.374012 osafclmd [2763:s
[tickets] [opensaf:tickets] #2407 amfnd: message ID mismatches during SC absence recovery
--- ** [tickets:#2407] amfnd: message ID mismatches during SC absence recovery** **Status:** accepted **Milestone:** 5.0.2 **Created:** Fri Mar 31, 2017 08:55 AM UTC by Gary Lee **Last Updated:** Fri Mar 31, 2017 08:55 AM UTC **Owner:** Gary Lee In a test case where the active SC is repeatedly powered off abruptly, sometimes this can be seen: 2017-03-27 21:42:38 PL-5 osafamfnd[422]: Rebooting OpenSAF NodeId = 0 EE Name = No EE Mapped, Reason: Message ID mismatch, rec 1, expected 2, OwnNodeId = 132367, SupervisionTime = 60 2017-03-27 21:42:36 SC-1 osafamfd[510]: Started 2017-03-27 21:42:36 SC-1 osafamfd[510]: NO Received node_up from 2030f: msg_id 2 2017-03-27 21:42:36 SC-1 osafamfd[510]: NO Received node_up from 2030f: msg_id 2 2017-03-27 21:42:36 SC-1 osafamfd[510]: NO Received node_up_msg from all nodes 2017-03-27 21:42:36 SC-1 osafamfd[510]: NO Received node_up from 2040f: msg_id 2 2017-03-27 21:42:36 SC-1 osafamfd[510]: NO Received node_up from 2030f: msg_id 2 2017-03-27 21:42:36 SC-1 osafamfd[510]: NO Received node_up from 2050f: msg_id 2 ``` 2017-03-27 21:39:50 PL-5 osafamfnd[422]: Started 2017-03-27 21:39:50 PL-5 osafamfnd[422]: WA saClmInitialize_4 returned 31 2017-03-27 21:39:50 PL-5 osafamfnd[422]: NO Sending node up due to NCSMDS_UP 2017-03-27 21:39:51 PL-5 osafamfnd[422]: NO 'safSu=PL-5,safSg=NoRed,safApp=OpenSAF' Presence State UNINSTANTIATED => INSTANTIATING 2017-03-27 21:39:51 PL-5 osafamfnd[422]: NO 'safSu=PL-5,safSg=NoRed,safApp=OpenSAF' Presence State INSTANTIATING => INSTANTIATED 2017-03-27 21:39:51 PL-5 osafamfnd[422]: NO Assigning 'safSi=NoRed2,safApp=OpenSAF' ACTIVE to 'safSu=PL-5,safSg=NoRed,safApp=OpenSAF' 2017-03-27 21:39:51 PL-5 osafamfnd[422]: NO Assigned 'safSi=NoRed2,safApp=OpenSAF' ACTIVE to 'safSu=PL-5,safSg=NoRed,safApp=OpenSAF' 2017-03-27 21:40:00 PL-5 osafamfnd[422]: NO AVD NEW_ACTIVE, adest:1 2017-03-27 21:40:15 PL-5 osafamfnd[422]: message repeated 2 times: [ NO AVD NEW_ACTIVE, adest:1] 2017-03-27 21:40:19 PL-5 osafamfnd[422]: WA AMF director unexpectedly crashed 2017-03-27 21:40:19 PL-5 osafamfnd[422]: NO Checking 'safSu=PL-5,safSg=NoRed,safApp=OpenSAF' for pending messages 2017-03-27 21:40:35 PL-5 osafamfnd[422]: NO AVD NEW_ACTIVE, adest:1 2017-03-27 21:40:35 PL-5 osafamfnd[422]: NO saClmDispatch BAD_HANDLE 2017-03-27 21:40:35 PL-5 osafamfnd[422]: NO 1 SISU states sent 2017-03-27 21:40:35 PL-5 osafamfnd[422]: NO 1 SU states sent 2017-03-27 21:40:35 PL-5 osafamfnd[422]: NO 5 CSICOMP states sent 2017-03-27 21:40:35 PL-5 osafamfnd[422]: NO 5 COMP states sent 2017-03-27 21:40:35 PL-5 osafamfnd[422]: NO Sending node up due to NCSMDS_NEW_ACTIVE 2017-03-27 21:40:40 PL-5 osafamfnd[422]: NO AVD NEW_ACTIVE, adest:1 2017-03-27 21:41:11 PL-5 osafamfnd[422]: message repeated 3 times: [ NO AVD NEW_ACTIVE, adest:1] 2017-03-27 21:41:18 PL-5 osafamfnd[422]: WA AMF director unexpectedly crashed 2017-03-27 21:41:18 PL-5 osafamfnd[422]: NO Checking 'safSu=PL-5,safSg=NoRed,safApp=OpenSAF' for pending messages 2017-03-27 21:41:35 PL-5 osafamfnd[422]: NO AVD NEW_ACTIVE, adest:1 2017-03-27 21:41:35 PL-5 osafamfnd[422]: NO saClmDispatch BAD_HANDLE 2017-03-27 21:41:35 PL-5 osafamfnd[422]: NO 1 SISU states sent 2017-03-27 21:41:35 PL-5 osafamfnd[422]: NO 1 SU states sent 2017-03-27 21:41:35 PL-5 osafamfnd[422]: NO 5 CSICOMP states sent 2017-03-27 21:41:35 PL-5 osafamfnd[422]: NO 5 COMP states sent 2017-03-27 21:41:35 PL-5 osafamfnd[422]: NO Sending node up due to NCSMDS_NEW_ACTIVE 2017-03-27 21:41:43 PL-5 osafamfnd[422]: WA AMF director unexpectedly crashed 2017-03-27 21:41:43 PL-5 osafamfnd[422]: NO Checking 'safSu=PL-5,safSg=NoRed,safApp=OpenSAF' for pending messages 2017-03-27 21:42:02 PL-5 osafamfnd[422]: NO AVD NEW_ACTIVE, adest:1 2017-03-27 21:42:02 PL-5 osafamfnd[422]: NO saClmDispatch BAD_HANDLE 2017-03-27 21:42:02 PL-5 osafamfnd[422]: NO 1 SISU states sent 2017-03-27 21:42:02 PL-5 osafamfnd[422]: NO 1 SU states sent 2017-03-27 21:42:02 PL-5 osafamfnd[422]: NO 5 CSICOMP states sent 2017-03-27 21:42:02 PL-5 osafamfnd[422]: NO 5 COMP states sent 2017-03-27 21:42:02 PL-5 osafamfnd[422]: NO Sending node up due to NCSMDS_NEW_ACTIVE 2017-03-27 21:42:12 PL-5 osafamfnd[422]: NO AVD NEW_ACTIVE, adest:1 2017-03-27 21:42:12 PL-5 osafamfnd[422]: NO saClmDispatch BAD_HANDLE 2017-03-27 21:42:36 PL-5 osafamfnd[422]: NO AVD NEW_ACTIVE, adest:1 2017-03-27 21:42:36 PL-5 osafamfnd[422]: NO saClmDispatch BAD_HANDLE 2017-03-27 21:42:38 PL-5 osafamfnd[422]: Rebooting OpenSAF NodeId = 0 EE Name = No EE Mapped, Reason: Message ID mismatch, rec 1, expected 2, OwnNodeId = 132367, SupervisionTime = 60 2017-03-27 21:40:53 SC-2 osafamfd[477]: Started 2017-03-27 21:40:53 SC-2 osafamfnd[485]: NO Start monitoring AMFD using /var/lib/opensaf/osafamfd.fifo 2017-03-27 21:40:56 SC-2 osafamfd[477]: NO Cold sync complete! 2017-03-27 21:41:00 SC-2 osafamfd[477]: NO FAILOVER StandBy --> Active 2017-03-27 21:41:00 SC-2 osafamfd[477]: NO Node 'SC-1' left the cluster 2017-03-27 21:41:00 SC-2 osaf
[tickets] [opensaf:tickets] #2406 log: not finalize accessor handle when getting scAbsenceAllowed
--- ** [tickets:#2406] log: not finalize accessor handle when getting scAbsenceAllowed** **Status:** assigned **Milestone:** 5.0.2 **Created:** Fri Mar 31, 2017 07:36 AM UTC by Vu Minh Nguyen **Last Updated:** Fri Mar 31, 2017 07:36 AM UTC **Owner:** Vu Minh Nguyen In `lgs_get_scAbsenceAllowed_attr()`, did not finalize IMM OM object accessor handle after done getting `scAbsenceAllowed`. --- 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.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
