date:20170223

[tickets] [opensaf:tickets] #2324 amfd: SG admin state is nor honored during node group unlock_instantiation

2017-02-23 Thread Tai Dinh

Attached temporary fix for this.


Attachments:

- 
[2324.patch](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/aac4dfbd/7ed5/attachment/2324.patch)
 (1.0 kB; application/octet-stream)


---

** [tickets:#2324] amfd: SG admin state is nor honored during node group 
unlock_instantiation**

**Status:** unassigned
**Milestone:** 5.2.FC
**Created:** Fri Feb 24, 2017 07:20 AM UTC by Tai Dinh
**Last Updated:** Fri Feb 24, 2017 07:20 AM UTC
**Owner:** nobody


SG admin state is not honored during node group unlock_instantiation.

This can always be reproduced:
- Put the SG under locked_instantiation state. SU is now UNINSTANTIATED
- Lock/lock_in the node group that the SG or its SUs hosted on
- Unlock_in the node group, the expectation here is that SU should be kept as 
UNINSTANTIATED state but they're not.
- AMF always try to instantiate the SUs without checking their SG state.

if ((su->saAmfSUAdminState != SA_AMF_ADMIN_LOCKED_INSTANTIATION) &&
(su->su_on_node->saAmfNodeAdminState != 
SA_AMF_ADMIN_LOCKED_INSTANTIATION) &&
(su->saAmfSUOperState == SA_AMF_OPERATIONAL_ENABLED) &&
(su->saAmfSUPresenceState == 
SA_AMF_PRESENCE_UNINSTANTIATED) &&
(su->su_on_node->saAmfNodeOperState == 
SA_AMF_OPERATIONAL_ENABLED)) {
if ((su->saAmfSUPreInstantiable == false) ||
(su->su_on_node->node_state != AVD_AVND_STATE_PRESENT))
continue;

if (sg->saAmfSGNumPrefInserviceSUs > su_try_inst) {
if (avd_snd_presence_msg(avd_cb, su, false) != 
NCSCC_RC_SUCCESS) {
LOG_NO("Failed to send Instantiation of '%s'", 
su->name.c_str());
} else {
su->su_on_node->su_cnt_admin_oper++;
su_try_inst++;
}
}
}



---

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] #2324 amfd: SG admin state is nor honored during node group unlock_instantiation

2017-02-23 Thread Tai Dinh




---

** [tickets:#2324] amfd: SG admin state is nor honored during node group 
unlock_instantiation**

**Status:** unassigned
**Milestone:** 5.2.FC
**Created:** Fri Feb 24, 2017 07:20 AM UTC by Tai Dinh
**Last Updated:** Fri Feb 24, 2017 07:20 AM UTC
**Owner:** nobody


SG admin state is not honored during node group unlock_instantiation.

This can always be reproduced:
- Put the SG under locked_instantiation state. SU is now UNINSTANTIATED
- Lock/lock_in the node group that the SG or its SUs hosted on
- Unlock_in the node group, the expectation here is that SU should be kept as 
UNINSTANTIATED state but they're not.
- AMF always try to instantiate the SUs without checking their SG state.

if ((su->saAmfSUAdminState != SA_AMF_ADMIN_LOCKED_INSTANTIATION) &&
(su->su_on_node->saAmfNodeAdminState != 
SA_AMF_ADMIN_LOCKED_INSTANTIATION) &&
(su->saAmfSUOperState == SA_AMF_OPERATIONAL_ENABLED) &&
(su->saAmfSUPresenceState == 
SA_AMF_PRESENCE_UNINSTANTIATED) &&
(su->su_on_node->saAmfNodeOperState == 
SA_AMF_OPERATIONAL_ENABLED)) {
if ((su->saAmfSUPreInstantiable == false) ||
(su->su_on_node->node_state != AVD_AVND_STATE_PRESENT))
continue;

if (sg->saAmfSGNumPrefInserviceSUs > su_try_inst) {
if (avd_snd_presence_msg(avd_cb, su, false) != 
NCSCC_RC_SUCCESS) {
LOG_NO("Failed to send Instantiation of '%s'", 
su->name.c_str());
} else {
su->su_on_node->su_cnt_admin_oper++;
su_try_inst++;
}
}
}



---

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] #1190 AMF: saAmfSIPrefActiveAssignments has wrong default, stopping scaling nway active SGs

2017-02-23 Thread Praveen

- Description has changed:

Diff:



--- old
+++ new
@@ -11,4 +11,17 @@
 
 "saAmfSGNumPrefInserviceSUs" should have a default value of "the number of the 
service units configured for the service group."
 
-The value of saAmfSIPrefActiveAssignments is currently set to one when not 
configured, instead it should be set to saAmfSGNumPrefAssignedSUs
+The value of saAmfSIPrefActiveAssignments is currently set to one when not 
configured, instead it should be set to saAmfSGNumPrefAssignedSUs.
+
+
+In order to avoid any backward compatibility issue, choice is left to the user 
for default value of the attribute.
+Default value of  saAmfSIPrefActiveAssignments will be either 
saAmfSGNumPrefAssignedSUs or 1
+based on user choice.
+Following are conditions in which different default values will be honoured:
+-if a user configures saAmfSIPrefActiveAssignments=1 then SI will assigned to 
only one
+SU.This is to ensure backward compatibility.
+-if a user does not configure attribute saAmfSIPrefActiveAssignments in 
application or
+ deletes this attributes via CCB operation then AMFD will still  honor default 
value as 1. This
+ is again to ensure backward compatibility.
+-if a user sets saAmfSIPrefActiveAssignments=0 via CCB or in application conf 
then AMFD will
+ use section 3.6.5 definition for default value i.e saAmfSGNumPrefAssignedSUs.



- **status**: review --> fixed
- **Comment**:

changeset:   8615:121dbcd7391b
tag: tip
user:Praveen Malviya 
date:Fri Feb 24 11:39:13 2017 +0530
files:   src/amf/amfd/sg.cc src/amf/amfd/sg.h src/amf/amfd/si.cc
description:
amfd: fix default value of saAmfSIPrefActiveAssignments [1190]

Will be updating AMF PR doc



---

** [tickets:#1190] AMF: saAmfSIPrefActiveAssignments has wrong default, 
stopping scaling nway active SGs**

**Status:** fixed
**Milestone:** 5.2.FC
**Created:** Thu Oct 23, 2014 01:10 PM UTC by Hans Feldt
**Last Updated:** Mon Jan 16, 2017 09:59 AM UTC
**Owner:** Praveen


Problem: In naway-active, SUs are not instantiated unless 
saAmfSIPrefActiveAssignments is configured.

saAmfSIPrefActiveAssignments is a configuration attribute only valid for the 
nway-active redundancy model.

According to the spec 3.6.5.3 it should have a default value of "the preferred 
number of assigned service units."

and 
"saAmfSGNumPrefAssignedSUs" should have a default value of "the preferred 
number of in-service service units"

and 

"saAmfSGNumPrefInserviceSUs" should have a default value of "the number of the 
service units configured for the service group."

The value of saAmfSIPrefActiveAssignments is currently set to one when not 
configured, instead it should be set to saAmfSGNumPrefAssignedSUs.


In order to avoid any backward compatibility issue, choice is left to the user 
for default value of the attribute.
Default value of  saAmfSIPrefActiveAssignments will be either 
saAmfSGNumPrefAssignedSUs or 1
based on user choice.
Following are conditions in which different default values will be honoured:
-if a user configures saAmfSIPrefActiveAssignments=1 then SI will assigned to 
only one
SU.This is to ensure backward compatibility.
-if a user does not configure attribute saAmfSIPrefActiveAssignments in 
application or
 deletes this attributes via CCB operation then AMFD will still  honor default 
value as 1. This
 is again to ensure backward compatibility.
-if a user sets saAmfSIPrefActiveAssignments=0 via CCB or in application conf 
then AMFD will
 use section 3.6.5 definition for default value i.e saAmfSGNumPrefAssignedSUs.



---

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] #2239 log: no housekeeping for cfg files

2017-02-23 Thread A V Mahesh (AVM)

- **status**: review --> fixed
- **Comment**:

changeset:   8614:0623f817f002
tag: tip
user:A V Mahesh 
date:Fri Feb 24 09:41:04 2017 +0530
summary: logd: implement cfg files rotation [#2239]



---

** [tickets:#2239] log: no housekeeping for cfg files**

**Status:** fixed
**Milestone:** 5.2.FC
**Created:** Wed Dec 21, 2016 08:19 AM UTC by Vu Minh Nguyen
**Last Updated:** Mon Feb 06, 2017 07:34 AM UTC
**Owner:** A V Mahesh (AVM)


At the moment, LOGsv takes care of the housekeeping of the log files, but not 
for cfg files.

So, if we play with log streams in a long time, or we encounter an cyclic 
reboots of SCs, 
a large numbers of cfg files are generated even log files that go along with 
them have been removed due to rotation.


---

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] #2316 amfnd: amfnd is stuck in removing assignment in shutting down phase

2017-02-23 Thread Minh Hon Chau

Hi Praveen,

Problem in this ticket happens in the area of @pending_removal, which is 
introduced in ticket #1046. In #1046, the component that has pending assignment 
will be restarted, thus amfnd will not have to wait for csi callback of pending 
assignment. In this ticket #2316, amfnd has to wait for the response of pending 
assignment, then amfnd can continue removal assignment afterwards. By this 
understanding, I think to fix the problem in #2316, amfnd does not remove 
callback record of pending csi. That would not violate to scenario of #1046.

I could not replicate the problem in #1046, attached patch is an illustration 
for fix of #2316. It needs a bit clean up if it is ok. Could you have a look?

Thanks,
Minh


Attachments:

- 
[2316.diff](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/c4f9a458/a284/attachment/2316.diff)
 (2.6 kB; text/x-patch)


---

** [tickets:#2316] amfnd: amfnd is stuck in removing assignment in shutting 
down phase**

**Status:** accepted
**Milestone:** 5.0.2
**Created:** Wed Feb 22, 2017 01:00 AM UTC by Minh Hon Chau
**Last Updated:** Wed Feb 22, 2017 05:15 AM UTC
**Owner:** Minh Hon Chau
**Attachments:**

- 
[app3_twon2su1si.xml](https://sourceforge.net/p/opensaf/tickets/2316/attachment/app3_twon2su1si.xml)
 (9.2 kB; text/xml)
- [log.tgz](https://sourceforge.net/p/opensaf/tickets/2316/attachment/log.tgz) 
(696.0 kB; application/x-compressed)


- Configuration: Using attached model
- Steps:
. Loading application in attached model
. SU5 in PL5 has standby assignment
. kill amf_demo in PL5 which is component of SU5
. amd_demo will be instantiated and reassigned assignment
. Delay csi set callback for standby assignment in amf_demo component
. stop opensafd: /opensafd stop
. Release csi set callback in amf_demo component
- Observation: amfnd is stucked in removing assignment until it's killed by 
opensafd

> 2017-02-21 23:04:54 PL-5 amf_demo[543]: exiting (caught term signal)
> 2017-02-21 23:04:54 PL-5 osafamfnd[412]: NO 
> 'safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemo3' component restart probation 
> timer started (timeout: 300 ns)
> 2017-02-21 23:04:54 PL-5 osafamfnd[412]: NO Restarting a component of 
> 'safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemo3' (comp restart count: 1)
> 2017-02-21 23:04:54 PL-5 osafamfnd[412]: NO 
> 'safComp=AmfDemo,safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemo3' faulted due to 
> 'avaDown' : Recovery is 'componentRestart'
> 2017-02-21 23:04:54 PL-5 osafamfnd[412]: NO 
> 'safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemo3' Presence State INSTANTIATED => 
> RESTARTING
> 2017-02-21 23:04:54 PL-5 amf_demo[605]: 
> 'safComp=AmfDemo,safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemo3' started
> 2017-02-21 23:04:54 PL-5 amf_demo_script: 
> safComp=AmfDemo,safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemo3
> 2017-02-21 23:04:54 PL-5 amf_demo_script: Starting 
> /srv/osaftest/amf_demo/amf_demo succeeded, rc:0
> 2017-02-21 23:04:54 PL-5 osafamfnd[412]: NO 
> 'safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemo3' Presence State RESTARTING => 
> INSTANTIATED
> 2017-02-21 23:04:54 PL-5 amf_demo[605]: Registered with AMF and HC started
> 2017-02-21 23:04:54 PL-5 amf_demo[605]: CSI Set - add 
> 'safCsi=AmfDemo3,safSi=AmfDemo3,safApp=AmfDemo3' HAState Standby
> 2017-02-21 23:04:54 PL-5 amf_demo[605]: debug delay 2 secs
> 2017-02-21 23:04:57 PL-5 opensafd: Stopping OpenSAF Services
> 2017-02-21 23:04:57 PL-5 osafamfnd[412]: NO Shutdown initiated
> 2017-02-21 23:04:57 PL-5 osafamfnd[412]: NO Removing assignments from AMF 
> components
> 2017-02-21 23:05:00 PL-5 amf_demo[605]: message repeated 3 times: [ debug 
> delay 2 secs]
> 2017-02-21 23:05:02 PL-5 amf_demo[605]: Health check 1
> 2017-02-21 23:05:24 PL-5 osafamfnd[412]: NO 
> 'safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemo3' Component or SU restart 
> probation timer expired
> 2017-02-21 23:05:57 PL-5 opensafd: amfnd has not yet exited, killing it 
> forcibly.
> 2017-02-21 23:05:57 PL-5 amf_demo[605]: AL AMF Node Director is down, 
> terminate this process
> 2017-02-21 23:05:57 PL-5 amf_demo[605]: exiting (caught term signal)
> 2017-02-21 23:05:57 PL-5 osafclmna[404]: AL AMF Node Director is down, 
> terminate this process
> 2017-02-21 23:05:57 PL-5 osafimmnd[395]: AL AMF Node Director is down, 
> terminate this process
> 2017-02-21 23:05:57 PL-5 osafckptnd[431]: AL AMF Node Director is down, 
> terminate this process
> 2017-02-21 23:05:57 PL-5 osafsmfnd[453]: AL AMF Node Director is down, 
> terminate this process
> 2017-02-21 23:05:57 PL-5 osafamfwd[422]: Rebooting OpenSAF NodeId = 0 EE Name 
> = No EE Mapped, Reason: AMF unexpectedly crashed, OwnNodeId = 132367, 
> SupervisionTime = 60
> 
log/trace is attached



---

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

[tickets] [opensaf:tickets] #2210 AMFD: Loss of RT attribute update before headless

2017-02-23 Thread Minh Hon Chau

- **status**: fixed --> review
- **assigned_to**: Minh Hon Chau
- **Comment**:

One bug is introduced in changeset changeset: 8603:314f3f2fa3ef that causes SU 
in admin operation of si-swap becoming out of service after headless. Updated 
patch is sent for review.




---

** [tickets:#2210] AMFD: Loss of RT attribute update before headless**

**Status:** review
**Milestone:** 5.2.FC
**Created:** Mon Nov 28, 2016 10:18 PM UTC by Minh Hon Chau
**Last Updated:** Wed Feb 22, 2017 04:21 AM UTC
**Owner:** Minh Hon Chau


A loss of IMM RT saAmfSIAdminState update in AMFD has been seen just before 
cluster goes headless. It results in coredump after headless.

One scenario is:
- Issue amf-admin shutdown SI, delay csi quiescing callback
- Stop SCs, release csi quiescing callback
- Restart SCs
Observation: the saAmfSIAdminState is read as UNLOCKED while related SUSI was 
QUIESCED, and coredump as below

~~~
Thread 1 (Thread 0x7fec174a0780 (LWP 493)):
#0  0x004fbfd5 in SG_2N::node_fail_si_oper (this=0x24109d0, 
su=0x2413440) at sg_2n_fsm.cc:3102
s_susi = 0x8f5000b
susi_temp = 0x5fa169
o_su = 0x2417f98
__FUNCTION__ = "node_fail_si_oper"
cb = 0x919240 <_control_block>
#1  0x004fe69c in SG_2N::node_fail (this=0x24109d0, cb=0x919240 
<_control_block>, su=0x2413440) at sg_2n_fsm.cc:
3469
a_susi = 0x1
s_susi = 0x7fffedecd2d0
o_su = 0x5a50bd 
flag = 2
__FUNCTION__ = "node_fail"
su_ha_state = 0
#2  0x00513010 in AVD_SG::failover_absent_assignment (this=0x24109d0) 
at sg.cc:2273
su = @0x2411330: 0x2413440
__for_range = std::vector of length 2, capacity 2 = {0x2413440, 
0x24111e0}
__for_begin = 
__for_end = 
__FUNCTION__ = "failover_absent_assignment"
#3  0x0043be65 in avd_cluster_tmr_init_evh (cb=0x919240 
<_control_block>, evt=0x7fec04000df0) at cluster.cc:103
i_sg = 0x24109d0
it = {first = "safSg=1,safApp=osaftest", second = }
__FUNCTION__ = "avd_cluster_tmr_init_evh"
su = 0x0
node = 0x240f9b0
~~~



---

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] #2323 imm: CCB operations fail after SC absence

2017-02-23 Thread Hung Nguyen




---

** [tickets:#2323] imm: CCB operations fail after SC absence**

**Status:** accepted
**Milestone:** 5.0.2
**Created:** Thu Feb 23, 2017 03:36 PM UTC by Hung Nguyen
**Last Updated:** Thu Feb 23, 2017 03:36 PM UTC
**Owner:** Hung Nguyen
**Attachments:**

- 
[logs_n_traces.tgz](https://sourceforge.net/p/opensaf/tickets/2323/attachment/logs_n_traces.tgz)
 (658.6 kB; application/gzip)


Reproduce steps:
~~~
1. Start SC-1
2. Commit some CCBs
# immcfg -c Test test=0
# immcfg -c Test test=1
# immcfg -c Test test=2
# immcfg -c Test test=3
3. Start PL-3
4. Restart SC-1
5. When SC-1 is back, it fails to add operations to CCB
# immcfg -c Test test=10
error - saImmOmCcbObjectCreate_2 FAILED with SA_AIS_ERR_FAILED_OPERATION 
(21)
OI reports: IMM: Resource abort: CCB is not in an expected state
error - saImmOmCcbApply FAILED: SA_AIS_ERR_FAILED_OPERATION (21)
OI reports: IMM: Resource abort: CCB is not in an expected state
~~~

**cb->mLatestCcbId** was not updated on PL-3 when it joined the cluster so it 
still had value of zero.

When SC-1 was back from headless, IMMND on PL-3 sent re-introduce message to 
IMMD on SC-1 with **cb->mLatestCcbId = 0**.

IMMD failed to update **cb->ccb_id_count** so when new CCB is created, it will 
start from **0+1** instead of **mLatestCcbId + 1**.

That results in the conflict with the CCB in **sCcbVector** and the CCB 
operation failure.

Attached is logs and traces.


---

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] #2294 nid: nodeinit may crash when exit is called from the main thread

2017-02-23 Thread Hans Nordebäck

- **status**: review --> fixed
- **Comment**:

changeset:   8613:0022ff8992a4
tag: tip
user:Hans Nordeback 
date:Wed Feb 08 12:08:21 2017 +0100
summary: nid: nodeinit may crash when exit is called from the main thread 
[#2294]




---

** [tickets:#2294] nid: nodeinit may crash when exit is called from the main 
thread**

**Status:** fixed
**Milestone:** 5.2.FC
**Created:** Wed Feb 08, 2017 11:07 AM UTC by Hans Nordebäck
**Last Updated:** Fri Feb 10, 2017 09:29 AM UTC
**Owner:** Hans Nordebäck


nodeinit may crash when exit is called from the main thread, the std::string in 
svc_map 
is destructed but still used by the svc_monitor_thread

[New LWP 146]
[New LWP 145]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/local/lib/opensaf/opensafd'.
Program terminated with signal SIGSEGV, Segmentation fault.
.#0  __memcmp_sse2 () at ../sysdeps/x86_64/multiarch/../memcmp.S:37
[Current thread is 1 (Thread 0x7fcb6491b700 (LWP 146))]

Thread 2 (Thread 0x7fcb660eb740 (LWP 145)):
.#0  0x7fcb650a934b in __GI__IO_file_close (fp=) at 
fileops.c:1250
resultvar = 0
.#1  0x7fcb650aa960 in _IO_new_file_close_it (fp=fp@entry=0x562267416c40) 
at fileops.c:172
write_status = 0
close_status = 
.#2  0x7fcb6509e3ef in _IO_new_fclose (fp=0x562267416c40) at iofclose.c:58
_IO_acquire_lock_file = 0x562267416c40
status = 
.#3  0x7fcb65c7633c in __gcov_close () from 
/usr/local/lib/opensaf/libopensaf_core.so.0
No symbol table info available.
.#4  0x7fcb65c76ee1 in gcov_do_dump () from 
/usr/local/lib/opensaf/libopensaf_core.so.0
No symbol table info available.
.#5  0x7fcb65c77dd2 in gcov_exit () from 
/usr/local/lib/opensaf/libopensaf_core.so.0
No symbol table info available.
.#6  0x7fcb6506b36a in __cxa_finalize (d=0x7fcb65e9d920) at 
cxa_finalize.c:56
check = 10
cxafn = 
cxaarg = 
f = 0x7fcb653f5cf0 
funcs = 0x7fcb653f5c40 
.#7  0x7fcb65be3543 in __do_global_dtors_aux () from 
/usr/local/lib/opensaf/libopensaf_core.so.0
No symbol table info available.
.#8  0x7ffe23bf6a60 in ?? ()
No symbol table info available.
.#9  0x7fcb65ee2c17 in _dl_fini () at dl-fini.c:235
array = 0x7fcb65e9ab30
i = 0
l = 0x7fcb660f65c8
maps = 0x7fcb65c77dd8 
i = 2
l = 
nmaps = 0
nloaded = 
ns = 140511567373768
do_audit = 0
__PRETTY_FUNCTION__ = "_dl_fini"
Backtrace stopped: frame did not save the PC

Thread 1 (Thread 0x7fcb6491b700 (LWP 146)):
.#0  __memcmp_sse2 () at ../sysdeps/x86_64/multiarch/../memcmp.S:37
No locals.
.#1  0x562266ad276b in std::char_traits::compare (__s1=0x7fcb6491aee0 
"AMFND", __s2=0xcc4 , __n=5) at 
/usr/include/c++/5/bits/char_traits.h:262
No locals.
.#2  0x562266ad2ef7 in std::operator== (__lhs="AMFND", __rhs=) at 
/usr/include/c++/5/bits/basic_string.h:4914
No locals.
.#3  0x562266acf267 in handle_data_request (fds=0x7fcb68c0, 
nid_name="AMFND") at src/nid/nodeinit.cc:1416
svc = @0x562267416cd0: {nid_name = , fifo_file = "\377\377\377\377clmna.fifo", fifo_fd = 9}
__for_range = std::vector of length 11, capacity 11 = {{nid_name = 
, fifo_file = 
"\000\000\000\000\000 
mAg\"V\000\000\304\f\000\000\000\000\000\000\005\000\000\000\000\000\000\000\060mAg\"V",
 '\000' , 
"mAg\"V\000\000\016\000\000\000\000\000\000\000\377\377\377\377clmna.fifo\000\000\t\000\000\000\000\000\000\000\340\066?e\313\177\000\000\001\000\000\000\001\000\000\000@\267\016f\313\177",
 '\000' , "\f\000\000"..., fifo_fd = 1732340932}, {nid_name = 
"", fifo_file = "\206 \255\373\000", fifo_fd = 1732341024}, {nid_name = , fifo_file = 
"\377\377\377\377clmna.fifo", fifo_fd = 9}, {nid_name = "", fifo_file = "", 
fifo_fd = 0}, {nid_name = "", fifo_file = , fifo_fd = -1}, 
{nid_name = "IMMD", fifo_file = "osafimmd.fifo", fifo_fd = -1}, {nid_name = 
"IMMND", fifo_file = "osafimmnd.fifo", fifo_fd = 10}, {nid_name = "LOGD", 
fifo_file = 
"\361\000\000\000\000\000\000\000xK?e\313\177\000\000xK?e\313\177\000\000\220nAg\"V\000\000\004\000\000\000\000\000\000\000NTFD",
 '\000' , 
"\260nAg\"V\000\000\r\000\000\000\000\000\000\000osafntfd.fifo\000\000\000\377\377\377\377\000\000\000\000\330nAg\"V\000\000\004\000\000\000\000\000\000\000PLMD",
 '\000' , 
"\370nAg\"V\000\000\r\000\000\000\000\000\000\000osafplmd.fifo\000\000\000\377\377\377\377\000\000\000\000
 oAg\"V\000\000\004\000\000\000\000\000\000\000CLMD", '\000' ..., fifo_fd = 1698646904}, {nid_name = "NTFD", fifo_file = 
"osafntfd.fifo", fifo_fd = -1}, {nid_name = "PLMD", fifo_file = 
"osafplmd.fifo", fifo_fd = -1}, {nid_name = "CLMD", fifo_file = 
"osafclmd.fifo", fifo_fd = 240}}
__for_begin = {nid_name = , fifo_file = "\377\377\377\377clmna.fifo", fifo_fd = 9}
__for_end = {nid_name = ,

[tickets] [opensaf:tickets] #2288 smf: admin owner err_exist on parallel procedures

2017-02-23 Thread Rafael

- **status**: assigned --> fixed



---

** [tickets:#2288] smf: admin owner err_exist on parallel procedures**

**Status:** fixed
**Milestone:** 5.2.FC
**Created:** Fri Feb 03, 2017 01:42 PM UTC by Rafael
**Last Updated:** Thu Feb 23, 2017 12:57 PM UTC
**Owner:** Rafael


Create a campaign containing several single step procedures that install 
several bundles. If the procedures are on the same saSmfExecLevel the campaign 
will sometimes fail because of conflicting admin owner on IMM object. 

[SmfImmOperation.cc:0445] TR 
SmfImmCreateOperation::execute:saImmOmAdminOwnerSet failed SA_AIS_ERR_EXIST




---

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] #2288 smf: admin owner err_exist on parallel procedures

2017-02-23 Thread Rafael

Pushed to default branch:

HG changeset patch
 User Rafael Odzakow 
 Date 1487853466 -3600
  Thu Feb 23 13:37:46 2017 +0100
 Node ID 12d8b8f1e18240dc285df481baaf6acddc6511e8
 Parent  15ea36eab4835ed048e4f1d28013d27888437d9b
smf: admin owner err_exist on parallel procedures [#2288]



---

** [tickets:#2288] smf: admin owner err_exist on parallel procedures**

**Status:** assigned
**Milestone:** 5.2.FC
**Created:** Fri Feb 03, 2017 01:42 PM UTC by Rafael
**Last Updated:** Fri Feb 03, 2017 02:02 PM UTC
**Owner:** Rafael


Create a campaign containing several single step procedures that install 
several bundles. If the procedures are on the same saSmfExecLevel the campaign 
will sometimes fail because of conflicting admin owner on IMM object. 

[SmfImmOperation.cc:0445] TR 
SmfImmCreateOperation::execute:saImmOmAdminOwnerSet failed SA_AIS_ERR_EXIST




---

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] #2322 Amf: Amfd crashed during cold sync

2017-02-23 Thread Nagendra Kumar

- **status**: accepted --> review



---

** [tickets:#2322] Amf: Amfd crashed during cold sync**

**Status:** review
**Milestone:** 5.0.2
**Created:** Thu Feb 23, 2017 11:33 AM UTC by Nagendra Kumar
**Last Updated:** Thu Feb 23, 2017 11:33 AM UTC
**Owner:** Nagendra Kumar


Steps to reproduce
1. Start SC-1, upload a demo app.
2. Keep 5 seconds delay at the following code:
diff --git a/src/amf/amfd/imm.cc b/src/amf/amfd/imm.cc
--- a/src/amf/amfd/imm.cc
+++ b/src/amf/amfd/imm.cc
@@ -1602,6 +1602,10 @@ unsigned int avd_imm_config_get(void)
if (avd_comptype_config_get() != SA_AIS_OK)
goto done;

+   LOG_ER("1.  Before sleep ");
+   sleep(5);
+   LOG_ER("2.  After sleep");
+
/* SaAmfSUType needed by SaAmfSGType */
if (avd_sutype_config_get() != SA_AIS_OK)
goto done;
3. Start SC-2, when it print "Before sleep". Then run the below command on SC-1:
immcfg -d 
"safMemberCompType=safVersion=1\,safCompType=AmfDemo1,safVersion=1,safSuType=AmfDemo1"

Observed behaviour
--

When SC-2 comes up after sleep, it crashes at:
Core was generated by `/usr/local/lib/opensaf/osafamfd --tracemask=0x'.
Program terminated with signal 11, Segmentation fault.
#0  sutcomptype_ccb_completed_cb(CcbUtilOperationData*) () at 
src/amf/amfd/sutcomptype.cc:131
131 if (sutcomptype->curr_num_components == 0) {
(gdb) bt
#0  sutcomptype_ccb_completed_cb(CcbUtilOperationData*) () at 
src/amf/amfd/sutcomptype.cc:131
#1  0x7f64bc2d9757 in ccb_completed_cb(unsigned long long, unsigned long 
long) () at src/amf/amfd/imm.cc:1065
#2  0x7f64bb81dd64 in imma_process_callback_info(imma_cb*, 
imma_client_node*, imma_callback_info*, unsigned long long) ()
at src/imm/agent/imma_proc.cc:2174
#3  0x7f64bb81f739 in imma_hdl_callbk_dispatch_all(imma_cb*, unsigned long 
long) () at src/imm/agent/imma_proc.cc:1732
#4  0x7f64bb81659a in saImmOiDispatch () at src/imm/agent/imma_oi_api.cc:609
#5  0x7f64bc296ab8 in main () at src/amf/amfd/main.cc:729




---

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] #2289 opensafd (nid): coredump while standby starting

2017-02-23 Thread Anders Widell

Looks like "new" is failing - has it run out of memory? It is a pity that we 
can't see the printouts on standard error, maybe we should collect those 
printouts from out daemons.


---

** [tickets:#2289] opensafd (nid): coredump while standby starting**

**Status:** unassigned
**Milestone:** 5.2.FC
**Created:** Tue Feb 07, 2017 06:31 AM UTC by A V Mahesh (AVM)
**Last Updated:** Thu Feb 23, 2017 12:13 PM UTC
**Owner:** nobody


Restart Standby with TCP , opensafd core dumping


(gdb) bt
/#0  0x7f2f05cb0b55 in raise () from /lib64/libc.so.6
/#1  0x7f2f05cb2131 in abort () from /lib64/libc.so.6
/#2  0x7f2f06704955 in __gnu_cxx::__verbose_terminate_handler() () at 
../../../../gcc-4.8.3/libstdc++-v3/libsupc++/vterminate.cc:95
/#3  0x7f2f06702af6 in __cxxabiv1::__terminate(void (*)()) () at 
../../../../gcc-4.8.3/libstdc++-v3/libsupc++/eh_terminate.cc:38
/#4  0x7f2f06702b23 in std::terminate() () at 
../../../../gcc-4.8.3/libstdc++-v3/libsupc++/eh_terminate.cc:48
/#5  0x7f2f06702d42 in __cxa_throw () at 
../../../../gcc-4.8.3/libstdc++-v3/libsupc++/eh_throw.cc:87
/#6  0x7f2f0670322d in operator new(unsigned long) () at 
../../../../gcc-4.8.3/libstdc++-v3/libsupc++/new_op.cc:56
/#7  0x7f2f06761979 in std::string::_Rep::_S_create(unsigned long, unsigned 
long, std::allocator const&) ()
at 
/home/build/x86_64-unknown-linux-gnu/libstdc++-v3/include/ext/new_allocator.h:104
#8  0x7f2f0676256b in std::string::_Rep::_M_clone(std::allocator 
const&, unsigned long) () at 
/home/build/x86_64-unknown-linux-gnu/libstdc++-v3/include/bits/basic_string.tcc:629
#9  0x7f2f06762bec in std::basic_string::basic_string(std::string const&) ()
at 
/home/build/x86_64-unknown-linux-gnu/libstdc++-v3/include/bits/basic_string.h:229
#10 0x7f2f07262c39 in handle_data_request(pollfd*, std::string const&) () 
at /usr/include/c++/4.8.3/bits/basic_string.h:2405
#11 0x7f2f0726320f in svc_monitor_thread(void*) () at 
src/nid/nodeinit.cc:1539
#12 0x7f2f05ff97b6 in start_thread () from /lib64/libpthread.so.0
#13 0x7f2f05d559cd in clone () from /lib64/libc.so.6
#14 0x in ?? ()
(gdb) q



Feb  7 11:41:13 SC-2 opensafd: OpenSAF services successfully stopped
Feb  7 11:41:21 SC-2 opensafd: Starting OpenSAF Services(5.1.M0 - ) (Using TCP)
Feb  7 11:41:21 SC-2 osafdtmd[5329]: mkfifo already exists: 
/var/lib/opensaf/osafdtmd.fifo File exists
Feb  7 11:41:21 SC-2 osafdtmd[5329]: Started
Feb  7 11:41:21 SC-2 osaftransportd[5336]: Started
Feb  7 11:41:21 SC-2 osafclmna[5343]: Started
Feb  7 11:41:21 SC-2 osafrded[5352]: Started
Feb  7 11:41:22 SC-2 osaffmd[5361]: Started
Feb  7 11:41:22 SC-2 osaffmd[5361]: NO Remote fencing is disabled
Feb  7 11:41:22 SC-2 osafimmd[5371]: Started
Feb  7 11:41:22 SC-2 osafimmd[5371]: NO *** SC_ABSENCE_ALLOWED (Headless 
Hydra) is configured: 900 ***
Feb  7 11:41:22 SC-2 osafimmnd[5382]: Started
Feb  7 11:41:22 SC-2 osafimmnd[5382]: NO Persistent Back-End capability 
configured, Pbe file:imm.db (suffix may get added)
Feb  7 11:41:22 SC-2 opensafd[5318]: NO Monitoring of TRANSPORT started
Feb  7 11:41:22 SC-2 osafclmna[5343]: NO Starting to promote this node to a 
system controller
Feb  7 11:41:22 SC-2 osafrded[5352]: NO Requesting ACTIVE role
Feb  7 11:41:22 SC-2 osafrded[5352]: NO RDE role set to Undefined
Feb  7 11:41:22 SC-2 osafdtmd[5329]: NO Established contact with 'PL-3'
Feb  7 11:41:22 SC-2 osafdtmd[5329]: NO Established contact with 'SC-1'
Feb  7 11:41:22 SC-2 osafdtmd[5329]: NO Established contact with 'PL-4'
Feb  7 11:41:22 SC-2 osafrded[5352]: NO Peer up on node 0x2010f
Feb  7 11:41:22 SC-2 osafimmnd[5382]: NO IMMD service is UP ... 
ScAbsenseAllowed?:0 introduced?:0
Feb  7 11:41:22 SC-2 osafrded[5352]: NO Got peer info request from node 0x2010f 
with role ACTIVE
Feb  7 11:41:22 SC-2 osafrded[5352]: NO Got peer info response from node 
0x2010f with role ACTIVE
Feb  7 11:41:22 SC-2 osafrded[5352]: NO RDE role set to QUIESCED
Feb  7 11:41:22 SC-2 osafrded[5352]: NO Giving up election against 0x2010f with 
role ACTIVE. My role is now QUIESCED
Feb  7 11:41:22 SC-2 osafclmna[5343]: NO safNode=SC-2,safCluster=myClmCluster 
Joined cluster, nodeid=2020f
Feb  7 11:41:22 SC-2 osafimmnd[5382]: NO Fevs count adjusted to 2835 
preLoadPid: 0
Feb  7 11:41:22 SC-2 osafimmnd[5382]: NO SERVER STATE: IMM_SERVER_ANONYMOUS --> 
IMM_SERVER_CLUSTER_WAITING
Feb  7 11:41:22 SC-2 osafimmnd[5382]: NO SERVER STATE: 
IMM_SERVER_CLUSTER_WAITING --> IMM_SERVER_LOADING_PENDING
Feb  7 11:41:22 SC-2 osafimmnd[5382]: NO SERVER STATE: 
IMM_SERVER_LOADING_PENDING --> IMM_SERVER_SYNC_PENDING
Feb  7 11:41:22 SC-2 osafimmnd[5382]: NO NODE STATE-> IMM_NODE_ISOLATED
Feb  7 11:41:23 SC-2 osafimmnd[5382]: NO NODE STATE-> IMM_NODE_W_AVAILABLE
Feb  7 11:41:23 SC-2 osafimmnd[5382]: NO

[tickets] [opensaf:tickets] #2289 opensafd (nid): coredump while standby starting

2017-02-23 Thread Praveen

This is observed two times on TIPC setup also when bringing up standby:

(gdb) bt
\#0  0x7f44a1104b55 in raise () from /lib64/libc.so.6
\#1  0x7f44a1106131 in abort () from /lib64/libc.so.6
\#2  0x7f44a18e0035 in __gnu_cxx::__verbose_terminate_handler() ()
at ../../../../gcc-4.9.0/libstdc++-v3/libsupc++/vterminate.cc:95
\#3  0x7f44a18de096 in __cxxabiv1::__terminate(void (*)()) ()
at ../../../../gcc-4.9.0/libstdc++-v3/libsupc++/eh_terminate.cc:47
\#4  0x7f44a18de0e1 in std::terminate() () at 
../../../../gcc-4.9.0/libstdc++-v3/libsupc++/eh_terminate.cc:57
\#5  0x7f44a18de2f8 in __cxa_throw () at 
../../../../gcc-4.9.0/libstdc++-v3/libsupc++/eh_throw.cc:87
\#6  0x7f44a18de809 in operator new(unsigned long) () at 
../../../../gcc-4.9.0/libstdc++-v3/libsupc++/new_op.cc:54
\#7  0x7f44a1943159 in std::string::_Rep::_S_create(unsigned long, unsigned 
long, std::allocator const&) ()
at 
/home/build/x86_64-unknown-linux-gnu/libstdc++-v3/include/ext/new_allocator.h:104
\#8  0x7f44a1943e3b in std::string::_Rep::_M_clone(std::allocator 
const&, unsigned long) ()
at 
/home/build/x86_64-unknown-linux-gnu/libstdc++-v3/include/bits/basic_string.tcc:629
\#9  0x7f44a194451c in std::basic_string::basic_string(std::string const&) () at 
/home/build/x86_64-unknown-linux-gnu/libstdc++-v3/include/bits/basic_string.h:229
\#10 0x7f44a203bda7 in handle_data_request(pollfd*, std::string const&) ()
at /usr/include/c++/4.9.0/bits/basic_string.h:2424
\#11 0x7f44a203c378 in svc_monitor_thread(void*) () at 
src/nid/nodeinit.cc:1539
\#12 0x7f44a144d7b6 in start_thread () from /lib64/libpthread.so.0
\#13 0x7f44a11a99cd in clone () from /lib64/libc.so.6
\#14 0x in ?? ()



---

** [tickets:#2289] opensafd (nid): coredump while standby starting**

**Status:** unassigned
**Milestone:** 5.2.FC
**Created:** Tue Feb 07, 2017 06:31 AM UTC by A V Mahesh (AVM)
**Last Updated:** Tue Feb 07, 2017 06:31 AM UTC
**Owner:** nobody


Restart Standby with TCP , opensafd core dumping


(gdb) bt
/#0  0x7f2f05cb0b55 in raise () from /lib64/libc.so.6
/#1  0x7f2f05cb2131 in abort () from /lib64/libc.so.6
/#2  0x7f2f06704955 in __gnu_cxx::__verbose_terminate_handler() () at 
../../../../gcc-4.8.3/libstdc++-v3/libsupc++/vterminate.cc:95
/#3  0x7f2f06702af6 in __cxxabiv1::__terminate(void (*)()) () at 
../../../../gcc-4.8.3/libstdc++-v3/libsupc++/eh_terminate.cc:38
/#4  0x7f2f06702b23 in std::terminate() () at 
../../../../gcc-4.8.3/libstdc++-v3/libsupc++/eh_terminate.cc:48
/#5  0x7f2f06702d42 in __cxa_throw () at 
../../../../gcc-4.8.3/libstdc++-v3/libsupc++/eh_throw.cc:87
/#6  0x7f2f0670322d in operator new(unsigned long) () at 
../../../../gcc-4.8.3/libstdc++-v3/libsupc++/new_op.cc:56
/#7  0x7f2f06761979 in std::string::_Rep::_S_create(unsigned long, unsigned 
long, std::allocator const&) ()
at 
/home/build/x86_64-unknown-linux-gnu/libstdc++-v3/include/ext/new_allocator.h:104
#8  0x7f2f0676256b in std::string::_Rep::_M_clone(std::allocator 
const&, unsigned long) () at 
/home/build/x86_64-unknown-linux-gnu/libstdc++-v3/include/bits/basic_string.tcc:629
#9  0x7f2f06762bec in std::basic_string::basic_string(std::string const&) ()
at 
/home/build/x86_64-unknown-linux-gnu/libstdc++-v3/include/bits/basic_string.h:229
#10 0x7f2f07262c39 in handle_data_request(pollfd*, std::string const&) () 
at /usr/include/c++/4.8.3/bits/basic_string.h:2405
#11 0x7f2f0726320f in svc_monitor_thread(void*) () at 
src/nid/nodeinit.cc:1539
#12 0x7f2f05ff97b6 in start_thread () from /lib64/libpthread.so.0
#13 0x7f2f05d559cd in clone () from /lib64/libc.so.6
#14 0x in ?? ()
(gdb) q



Feb  7 11:41:13 SC-2 opensafd: OpenSAF services successfully stopped
Feb  7 11:41:21 SC-2 opensafd: Starting OpenSAF Services(5.1.M0 - ) (Using TCP)
Feb  7 11:41:21 SC-2 osafdtmd[5329]: mkfifo already exists: 
/var/lib/opensaf/osafdtmd.fifo File exists
Feb  7 11:41:21 SC-2 osafdtmd[5329]: Started
Feb  7 11:41:21 SC-2 osaftransportd[5336]: Started
Feb  7 11:41:21 SC-2 osafclmna[5343]: Started
Feb  7 11:41:21 SC-2 osafrded[5352]: Started
Feb  7 11:41:22 SC-2 osaffmd[5361]: Started
Feb  7 11:41:22 SC-2 osaffmd[5361]: NO Remote fencing is disabled
Feb  7 11:41:22 SC-2 osafimmd[5371]: Started
Feb  7 11:41:22 SC-2 osafimmd[5371]: NO *** SC_ABSENCE_ALLOWED (Headless 
Hydra) is configured: 900 ***
Feb  7 11:41:22 SC-2 osafimmnd[5382]: Started
Feb  7 11:41:22 SC-2 osafimmnd[5382]: NO Persistent Back-End capability 
configured, Pbe file:imm.db (suffix may get added)
Feb  7 11:41:22 SC-2 opensafd[5318]: NO Monitoring of TRANSPORT started
Feb  7 11:41:22 SC-2 osafclmna[5343]: NO Starting to promote this node to a

[tickets] [opensaf:tickets] #2258 log: add alternative destinations of log records

2017-02-23 Thread elunlen

changeset:   8611:15ea36eab483
tag: tip
user:Lennart Lund 
date:Thu Feb 23 12:46:32 2017 +0100
summary: lgs: Add new multivalue attributes to configuration handler [#2258]

rev: 15ea36eab4835ed048e4f1d28013d27888437d9b


---

** [tickets:#2258] log: add alternative destinations of log records**

**Status:** review
**Milestone:** 5.2.FC
**Created:** Wed Jan 11, 2017 02:33 AM UTC by Vu Minh Nguyen
**Last Updated:** Thu Feb 16, 2017 10:31 AM UTC
**Owner:** Vu Minh Nguyen
**Attachments:**

- 
[LOGSv_Add_Alternative_Destination.odt](https://sourceforge.net/p/opensaf/tickets/2258/attachment/LOGSv_Add_Alternative_Destination.odt)
 (125.3 kB; application/vnd.oasis.opendocument.text)


The log service is as is dedicated to writing log records to file and this has 
so far been the only destination for log records. Several attributes in the 
configuration object and log stream objects are dedicated for configuration of 
this file handling. This is legacy.

Now, we introduce a generic way of handling alternative destinations of log 
records.  Legacy handling of log records will not be changed.

Find more information in attachement.


---

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] #2322 Amf: Amfd crashed during cold sync

2017-02-23 Thread Nagendra Kumar




---

** [tickets:#2322] Amf: Amfd crashed during cold sync**

**Status:** accepted
**Milestone:** 5.0.2
**Created:** Thu Feb 23, 2017 11:33 AM UTC by Nagendra Kumar
**Last Updated:** Thu Feb 23, 2017 11:33 AM UTC
**Owner:** Nagendra Kumar


Steps to reproduce
1. Start SC-1, upload a demo app.
2. Keep 5 seconds delay at the following code:
diff --git a/src/amf/amfd/imm.cc b/src/amf/amfd/imm.cc
--- a/src/amf/amfd/imm.cc
+++ b/src/amf/amfd/imm.cc
@@ -1602,6 +1602,10 @@ unsigned int avd_imm_config_get(void)
if (avd_comptype_config_get() != SA_AIS_OK)
goto done;

+   LOG_ER("1.  Before sleep ");
+   sleep(5);
+   LOG_ER("2.  After sleep");
+
/* SaAmfSUType needed by SaAmfSGType */
if (avd_sutype_config_get() != SA_AIS_OK)
goto done;
3. Start SC-2, when it print "Before sleep". Then run the below command on SC-1:
immcfg -d 
"safMemberCompType=safVersion=1\,safCompType=AmfDemo1,safVersion=1,safSuType=AmfDemo1"

Observed behaviour
--

When SC-2 comes up after sleep, it crashes at:
Core was generated by `/usr/local/lib/opensaf/osafamfd --tracemask=0x'.
Program terminated with signal 11, Segmentation fault.
#0  sutcomptype_ccb_completed_cb(CcbUtilOperationData*) () at 
src/amf/amfd/sutcomptype.cc:131
131 if (sutcomptype->curr_num_components == 0) {
(gdb) bt
#0  sutcomptype_ccb_completed_cb(CcbUtilOperationData*) () at 
src/amf/amfd/sutcomptype.cc:131
#1  0x7f64bc2d9757 in ccb_completed_cb(unsigned long long, unsigned long 
long) () at src/amf/amfd/imm.cc:1065
#2  0x7f64bb81dd64 in imma_process_callback_info(imma_cb*, 
imma_client_node*, imma_callback_info*, unsigned long long) ()
at src/imm/agent/imma_proc.cc:2174
#3  0x7f64bb81f739 in imma_hdl_callbk_dispatch_all(imma_cb*, unsigned long 
long) () at src/imm/agent/imma_proc.cc:1732
#4  0x7f64bb81659a in saImmOiDispatch () at src/imm/agent/imma_oi_api.cc:609
#5  0x7f64bc296ab8 in main () at src/amf/amfd/main.cc:729




---

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] #2151 osaf: system in not in correct state during Act controller comming up

2017-02-23 Thread Ramesh

- **status**: accepted --> review



---

** [tickets:#2151] osaf: system in not in correct state during Act controller 
comming up**

**Status:** review
**Milestone:** 5.2.FC
**Created:** Mon Oct 31, 2016 10:54 AM UTC by Nagendra Kumar
**Last Updated:** Mon Jan 23, 2017 05:45 AM UTC
**Owner:** Ramesh


Steps to reproduce:
1. Start two controllers(SC-1 Act, SC-2 Standby) and two paylods. Configure 50 
components on SC-2 and unlock them. Keep 1 sec delay in each component stop 
script.
2. Stop SC-1 and after that, stop SC-2.
3. During SC-2 is going down, start SC-1.

Observed behaviour:
Since components are taking time in stopping all components during 'opensad 
stop' of SC-2, Amfnd hasn't exited. But, all middleware components assignments 
are stopped. Only Amfnd and Amfd is alive with few more components to stop.
But SC-1 has come up till Amfd and since two Amfd is Act now, so SC-2 Amfd 
exits by saying "Duplicate ACTIVE detected, exiting".
Till this time, services states including Amfd is in bad state as they couldn't 
differentiate whether it is headless state or failover. This is true also as 
the system is in half middle of headless and failover.


Expected behaviour
In my view:
FMS should stop and shouldn't proceed if peer is going down. i.e. FMS should 
figure out on SC-1 that the peer system is going down. And should allow SC-1 
only if all services are down i.e. it gets node down (may be cb->immd_down && 
cb->immnd_down && cb->amfnd_down && cb->amfd_down && cb->fm_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.--
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] #2324 amfd: SG admin state is nor honored during node group unlock_instantiation

[tickets] [opensaf:tickets] #2324 amfd: SG admin state is nor honored during node group unlock_instantiation

[tickets] [opensaf:tickets] #1190 AMF: saAmfSIPrefActiveAssignments has wrong default, stopping scaling nway active SGs

[tickets] [opensaf:tickets] #2239 log: no housekeeping for cfg files

[tickets] [opensaf:tickets] #2316 amfnd: amfnd is stuck in removing assignment in shutting down phase

[tickets] [opensaf:tickets] #2210 AMFD: Loss of RT attribute update before headless

[tickets] [opensaf:tickets] #2323 imm: CCB operations fail after SC absence

[tickets] [opensaf:tickets] #2294 nid: nodeinit may crash when exit is called from the main thread

[tickets] [opensaf:tickets] #2288 smf: admin owner err_exist on parallel procedures

[tickets] [opensaf:tickets] #2288 smf: admin owner err_exist on parallel procedures

[tickets] [opensaf:tickets] #2322 Amf: Amfd crashed during cold sync

[tickets] [opensaf:tickets] #2289 opensafd (nid): coredump while standby starting

[tickets] [opensaf:tickets] #2289 opensafd (nid): coredump while standby starting

[tickets] [opensaf:tickets] #2258 log: add alternative destinations of log records

[tickets] [opensaf:tickets] #2322 Amf: Amfd crashed during cold sync

[tickets] [opensaf:tickets] #2151 osaf: system in not in correct state during Act controller comming up

16 matches

Site Navigation

Mail list logo

Footer information