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

2017-03-06 Thread Neelakanta Reddy
changeset:   8617:37f663fdfaaa
branch:  opensaf-5.1.x
parent:  8606:f667c97dab51
user:Rafael Odzakow 
date:Fri Feb 24 10:27:59 2017 +0100
summary: smf: admin owner err_exist on parallel procedures [#2288]

changeset:   8612:12d8b8f1e182
user:Rafael Odzakow 
date:Thu Feb 23 13:37:46 2017 +0100
summary: smf: admin owner err_exist on parallel procedures [#2288]



---

** [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.--
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


[tickets] [opensaf:tickets] #2338 amfd got crashed while changing role from queised to active

2017-03-06 Thread Nagendra Kumar
- **status**: unassigned --> assigned
- **assigned_to**: Nagendra Kumar



---

** [tickets:#2338] amfd got crashed while changing role from queised to active**

**Status:** assigned
**Milestone:** 5.2.RC1
**Created:** Fri Mar 03, 2017 05:41 AM UTC by Ritu Raj
**Last Updated:** Fri Mar 03, 2017 05:42 AM UTC
**Owner:** Nagendra Kumar
**Attachments:**

- 
[osafamfd.tgz](https://sourceforge.net/p/opensaf/tickets/2338/attachment/osafamfd.tgz)
 (2.8 MB; application/octet-stream)
- 
[syslog.7z](https://sourceforge.net/p/opensaf/tickets/2338/attachment/syslog.7z)
 (649.4 kB; application/octet-stream)


#Environment details
OS : Suse 64bit
Changeset : 8634 ( 5.2.FC)
Setup : 4 nodes ( 2 controllers and 2 payloads with 1PBE enabled )


#Summary
amfd got crashed while changing role from queised to active

#Steps followed & Observed behaviour
   1. Invoke switchovers
   2. After few successfull switchovers, SC-1 got Active role and SC-2 got 
standby role.
   3. Invoke one more switchover where SC-1 got queised role and 
SC-2 successfully become active after this cpd got crashed(SC-2) while 
SC-1 changing role from queised to active amfd got crashed on SC-1, resulted 
into cluster reset

>>For CPD crash refer ticket #2337

Syslog of SC-1:
Mar  2 14:12:00 TestBed-R1 osafimmnd[2138]: NO PBE-OI established on this SC. 
Dumping incrementally to file imm.db
Mar  2 14:12:03 TestBed-R1 osafamfd[2178]: ER Impl Set Failed for 
SaAmfNodeSwBundle, returned 5
Mar  2 14:12:03 TestBed-R1 osafamfd[2178]: ER avd_imm_applier_set FAILED, 5
Mar  2 14:12:03 TestBed-R1 osafamfd[2178]: src/amf/amfd/role.cc:807: 
avd_mds_qsd_role_evh: Assertion '0' failed.
Mar  2 14:12:03 TestBed-R1 osafamfnd[2188]: ER AMFD has unexpectedly crashed. 
Rebooting node
Mar  2 14:12:03 TestBed-R1 osafamfnd[2188]: Rebooting OpenSAF NodeId = 131343 
EE Name = , Reason: AMFD has unexpectedly crashed. Rebooting node, OwnNodeId = 
131343, SupervisionTime = 60



BT:
(gdb) thread apply all bt

Thread 4 (Thread 0x7f2e04fe4b00 (LWP 2182)):
0  0x7f2e034174f6 in poll () from /lib64/libc.so.6
1  0x7f2e0414633b in osaf_ppoll (io_fds=0x7f2e04fe41c0, i_nfds=1, 
i_timeout_ts=0x7f2e04fe4180, i_sigmask=0x0) at src/base/osaf_poll.c:105
2  0x7f2e04146261 in osaf_poll (io_fds=0x7f2e04fe41c0, i_nfds=1, 
i_timeout=3) at src/base/osaf_poll.c:44
3  0x7f2e04146430 in osaf_poll_one_fd (i_fd=15, i_timeout=3) at 
src/base/osaf_poll.c:128
4  0x7f2e0418d360 in rda_read_msg (sockfd=15, msg=0x7f2e04fe4260 "10 1", 
size=64) at src/rde/agent/rda_papi.cc:673
5  0x7f2e0418cb40 in rda_callback_task (rda_callback_cb=0x7f2e0549c440) at 
src/rde/agent/rda_papi.cc:150
6  0x7f2e036c47b6 in start_thread () from /lib64/libpthread.so.0
7  0x7f2e034209cd in clone () from /lib64/libc.so.6
8  0x in ?? ()

Thread 3 (Thread 0x7f2e05004b00 (LWP 2181)):
0  0x7f2e034174f6 in poll () from /lib64/libc.so.6
1  0x7f2e04188958 in mdtm_process_recv_events () at 
src/mds/mds_dt_tipc.c:669
2  0x7f2e036c47b6 in start_thread () from /lib64/libpthread.so.0
3  0x7f2e034209cd in clone () from /lib64/libc.so.6
4  0x in ?? ()

Thread 2 (Thread 0x7f2e0503ab00 (LWP 2180)):
0  0x7f2e034174f6 in poll () from /lib64/libc.so.6
1  0x7f2e0414633b in osaf_ppoll (io_fds=0x7f2e0503a270, i_nfds=1, 
i_timeout_ts=0x7f2e0503a2a0, i_sigmask=0x0) at src/base/osaf_poll.c:105
2  0x7f2e04150604 in ncs_tmr_wait () at src/base/sysf_tmr.c:406
3  0x7f2e036c47b6 in start_thread () from /lib64/libpthread.so.0
4  0x7f2e034209cd in clone () from /lib64/libc.so.6
5  0x in ?? ()

Thread 1 (Thread 0x7f2e05007720 (LWP 2178)):
0  0x7f2e0337bb55 in raise () from /lib64/libc.so.6
1  0x7f2e0337d131 in abort () from /lib64/libc.so.6
2  0x7f2e0414b6e7 in __osafassert_fail (__file=0x7f2e05215e2f 
"src/amf/amfd/role.cc", __line=807,
__func=0x7f2e05216c90  "avd_mds_qsd_role_evh", __assertion=0x7f2e05216548 "0")
at src/base/sysf_def.c:281
3  0x7f2e05182755 in avd_mds_qsd_role_evh (cb=0x7f2e054640c0 
<_control_block>, evt=0x7f2dfc000b20) at src/amf/amfd/role.cc:807
4  0x7f2e05156536 in process_event (cb_now=0x7f2e054640c0 <_control_block>, 
evt=0x7f2dfc000b20) at src/amf/amfd/main.cc:811
5  0x7f2e051560ee in main_loop () at src/amf/amfd/main.cc:702
6  0x7f2e051566fd in main (argc=2, argv=0x7fff5826f318) at 
src/amf/amfd/main.cc:861
(gdb)





Notes:
1. Syslog of both controller's attached
2. amfd bt attached
3. amfd trace attached

Both nodes are not in time sysnc, there is time gap between two nodes
Relative to SC-2, SC-1 is (+50 min ahead)
Time Diff
==
TestBed-R1:~  date
Thu Mar 2 16:34:45 IST 2017
TestBed-R2:~  date
Thu Mar 2 15:44:30 IST 2017
=


---

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 

[tickets] [opensaf:tickets] #2213 AMFND: Coredump if suFailover while shutting down

2017-03-06 Thread Nagendra Kumar
- **status**: assigned --> review
- **Version**:  --> 5.1 GA



---

** [tickets:#2213] AMFND: Coredump if suFailover while shutting down**

**Status:** review
**Milestone:** 5.2.RC1
**Created:** Fri Dec 02, 2016 04:54 AM UTC by Minh Hon Chau
**Last Updated:** Thu Mar 02, 2017 08:08 AM UTC
**Owner:** Nagendra Kumar
**Attachments:**

- [log.tgz](https://sourceforge.net/p/opensaf/tickets/2213/attachment/log.tgz) 
(548.6 kB; application/x-compressed)


Seen amfnd coredump in PL5 with bt as below while cluster is shutting down
~~~
Thread 1 (Thread 0x7f92a8925780 (LWP 411)):
#0  __strcmp_sse2 () at ../sysdeps/x86_64/multiarch/../strcmp.S:1358
No locals.
#1  0x00449cc9 in avsv_dblist_sastring_cmp (key1=, 
key2=) at util.c:361
i = 0
str1 = 
str2 = 
#2  0x7f92a84b1f95 in ncs_db_link_list_find (list_ptr=0x1ee89f0, 
key=0x656d6e6769737361 ) at ncsdlib.c:169
start_ptr = 0x1ee3168
#3  0x00416dc0 in avnd_comp_cmplete_all_csi_rec (cb=0x666940 
<_avnd_cb>, comp=0x1ee8200) at comp.cc:2652
curr = 0x1ee8060
prv = 0x1ee3150
__FUNCTION__ = "avnd_comp_cmplete_all_csi_rec"
#4  0x0040ca47 in avnd_instfail_su_failover (failed_comp=0x1ee8200, 
su=0x1ee74e0, cb=0x666940 <_avnd_cb>) at clc
.cc:3161
rc = 
#5  avnd_comp_clc_st_chng_prc (cb=cb@entry=0x666940 <_avnd_cb>, 
comp=comp@entry=0x1ee8200, prv_st=prv_st@entry=
SA_AMF_PRESENCE_RESTARTING, 
final_st=final_st@entry=SA_AMF_PRESENCE_TERMINATION_FAILED) at clc.cc:967
csi = 0x0
__FUNCTION__ = "avnd_comp_clc_st_chng_prc"
ev = AVND_SU_PRES_FSM_EV_MAX
is_en = 
rc = 1
#6  0x0040f530 in avnd_comp_clc_fsm_run (cb=cb@entry=0x666940 
<_avnd_cb>, comp=comp@entry=0x1ee8200, ev=
AVND_COMP_CLC_PRES_FSM_EV_CLEANUP_FAIL) at clc.cc:906
prv_st = 
final_st = 
rc = 1
__FUNCTION__ = "avnd_comp_clc_fsm_run"
#7  0x0040fdea in avnd_evt_clc_resp_evh (cb=0x666940 <_avnd_cb>, 
evt=0x7f9298c0) at clc.cc:414
__FUNCTION__ = "avnd_evt_clc_resp_evh"
ev = 
clc_evt = 0x7f9298e0
comp = 0x1ee8200
rc = 1
#8  0x0042676f in avnd_evt_process (evt=0x7f9298c0) at main.cc:626
cb = 0x666940 <_avnd_cb>
rc = 1
#9  avnd_main_process () at main.cc:577
ret = 
fds = {{fd = 12, events = 1, revents = 1}, {fd = 16, events = 1, 
revents = 0}, {fd = 14, events = 1, revents = 
0}, {fd = 0, events = 0, revents = 0}}
evt = 0x7f9298c0
__FUNCTION__ = "avnd_main_process"
result = 
rc = 
#10 0x004058f3 in main (argc=1, argv=0x7ffe700c5c78) at main.cc:202
error = 0
1358../sysdeps/x86_64/multiarch/../strcmp.S: No such file or directory.
~~~
In syslog of PL5:

2016-11-20 22:01:21 PL-5 osafamfnd[411]: NO 'safSu=3,safSg=1,safApp=npm_1' 
component restart probation timer started (timeout: 600 ns)
2016-11-20 22:01:21 PL-5 osafamfnd[411]: NO Restarting a component of 
'safSu=3,safSg=1,safApp=npm_1' (comp restart count: 1)
2016-11-20 22:01:21 PL-5 osafamfnd[411]: NO 
'safComp=A,safSu=3,safSg=1,safApp=npm_1' faulted due to 
'csiRemovecallbackTimeout' : Recovery is 'componentRestart'
2016-11-20 22:01:21 PL-5 osafamfnd[411]: NO 'safSu=3,safSg=1,safApp=npm_1' 
Presence State INSTANTIATED => RESTARTING
2016-11-20 22:01:21 PL-5 osafamfnd[411]: NO 'safSu=3,safSg=1,safApp=nway_1' 
component restart probation timer started (timeout: 600 ns)
2016-11-20 22:01:21 PL-5 osafamfnd[411]: NO Restarting a component of 
'safSu=3,safSg=1,safApp=nway_1' (comp restart count: 1)
2016-11-20 22:01:21 PL-5 osafamfnd[411]: NO 
'safComp=A,safSu=3,safSg=1,safApp=nway_1' faulted due to 
'csiRemovecallbackTimeout' : Recovery is 'componentRestart'
2016-11-20 22:01:21 PL-5 osafamfnd[411]: NO 'safSu=3,safSg=1,safApp=nway_1' 
Presence State INSTANTIATED => RESTARTING
2016-11-20 22:01:21 PL-5 osafamfnd[411]: NO 'safSu=4,safSg=1,safApp=npm_2' 
component restart probation timer started (timeout: 600 ns)
2016-11-20 22:01:21 PL-5 osafamfnd[411]: NO Restarting a component of 
'safSu=4,safSg=1,safApp=npm_2' (comp restart count: 1)
2016-11-20 22:01:21 PL-5 osafamfnd[411]: NO 
'safComp=A,safSu=4,safSg=1,safApp=npm_2' faulted due to 
'csiRemovecallbackTimeout' : Recovery is 'componentRestart'
2016-11-20 22:01:21 PL-5 osafamfnd[411]: NO 'safSu=4,safSg=1,safApp=npm_2' 
Presence State INSTANTIATED => RESTARTING
2016-11-20 22:01:21 PL-5 amfclccli[729]: CLEANUP request 
'safComp=A,safSu=4,safSg=1,safApp=npm_2'
2016-11-20 22:01:21 PL-5 amfclccli[728]: CLEANUP request 
'safComp=A,safSu=3,safSg=1,safApp=nway_1'
2016-11-20 22:01:21 PL-5 amfclccli[727]: CLEANUP request 
'safComp=A,safSu=3,safSg=1,safApp=npm_1'
2016-11-20 22:02:12 PL-5 osafamfnd[411]: NO Removed 'safSi=2,safApp=nway_1' 
from 'safSu=3,safSg=1,safApp=nway_1'
2016-11-20 22:02:12 PL-5 osafimmnd[394]: NO Global discard node received for 
nodeId:2040f pid:399
2016-11-20 22:02:12 PL-5 osafdtmd[380]: 

[tickets] [opensaf:tickets] #2344 log: leak memory in unix domain socket destination handler

2017-03-06 Thread Vu Minh Nguyen
- **status**: review --> fixed
- **assigned_to**: Vu Minh Nguyen -->  nobody 
- **Comment**:

changeset:   8654:bdc938d5787e
tag: tip
user:Vu Minh Nguyen 
date:Mon Mar 06 16:38:37 2017 +0700
summary: log: fix leak memory in socket destination handler [#2344]




---

** [tickets:#2344] log: leak memory in unix domain socket destination handler**

**Status:** fixed
**Milestone:** 5.2.RC1
**Created:** Sun Mar 05, 2017 05:41 PM UTC by Vu Minh Nguyen
**Last Updated:** Mon Mar 06, 2017 12:11 PM UTC
**Owner:** nobody


When updating the data store in the configuration handler a dynamic buffer is 
used. Data is added to this buffer using function lgs_cfgupd_list_create() 
which is also used by the help function lgs_cfgupd_mutival_replace(). When the 
buffer is created and expanded when adding more attributes memory is allocated 
that must be freed when the buffer is no longer used. 

In function `void DestinationHandler::UpdateRtDestStatus()`, it uses 
`lgs_cfgupd_mutival_replace()` to update `logRecordDestinationStatus` but not 
freeing buffer at the end of the function.

The allocated buffer needs to be freed by following code line:

```C
  // Free memory allocated for the config_data buffer
  if (config_data.ckpt_buffer_ptr != NULL)
free(config_data.ckpt_buffer_ptr);
```
 



---

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.--
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


[tickets] [opensaf:tickets] #2346 OpenSAF failed to start on controller randomaly

2017-03-06 Thread Hans Nordebäck
- **status**: unassigned --> review
- **assigned_to**: Hans Nordebäck



---

** [tickets:#2346] OpenSAF failed to start on controller randomaly **

**Status:** review
**Milestone:** 5.2.RC1
**Created:** Mon Mar 06, 2017 08:43 AM UTC by Ritu Raj
**Last Updated:** Mon Mar 06, 2017 08:46 AM UTC
**Owner:** Hans Nordebäck


###Environment details
OS : Suse 64bit
Changeset : 8634 ( 5.2.FC)

###Summary
OpenSAF failed to start on controller

###Steps followed & Observed behaviour
1. After couple of start and stop operation it is observed that some time 
opensaf failed to start on controller.

 >  Issue is random and till now it is observed 4 times

Mar 10 12:26:11 suseR2-S1 kernel: [346024.678444] TIPC: Own node address 
<1.1.1>, network identity 8181
Mar 10 12:26:11 suseR2-S1 kernel: [346024.704494] TIPC: Enabled bearer 
, discovery domain <1.1.0>, priority 10
Mar 10 12:26:11 suseR2-S1 kernel: [346024.704868] TIPC: Established link 
<1.1.1:eth0-1.1.6:eth0> on network plane A
Mar 10 12:26:11 suseR2-S1 kernel: [346024.704897] TIPC: Established link 
<1.1.1:eth0-1.1.4:eth0> on network plane A
Mar 10 12:26:11 suseR2-S1 kernel: [346024.704944] TIPC: Established link 
<1.1.1:eth0-1.1.5:eth0> on network plane A
Mar 10 12:26:11 suseR2-S1 opensafd[2869]: **ER Failed to open 
/var/lib/opensaf/osaftransportd.fifo, error: No such device or address**
Mar 10 12:26:11 suseR2-S1 opensafd[2869]: ER Failed to start monitoring for 
service TRANSPORT, exiting
Mar 10 12:26:12 suseR2-S1 osaftransportd[2899]: mkfifo already exists: 
/var/lib/opensaf/osaftransportd.fifo File exists
Mar 10 12:26:12 suseR2-S1 osaftransportd[2899]: Started
Mar 10 12:26:12 suseR2-S1 osafclmna[2909]: mkfifo already exists: 
/var/lib/opensaf/osafclmna.fifo File exists
Mar 10 12:26:12 suseR2-S1 osafclmna[2909]: Started
Mar 10 12:26:12 suseR2-S1 osafclmna[2909]: NO Starting to promote this node to 
a system controller
Mar 10 12:26:13 suseR2-S1 osafclmna[2909]: exiting for shutdown
Mar 10 12:26:14 suseR2-S1 osaftransportd[2899]: exiting for shutdown



---

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.--
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


[tickets] [opensaf:tickets] #2349 Immnd faild to load/sync during headless opeartion resulted opensaf failed to start on controller

2017-03-06 Thread Ritu Raj
New traces attahced:
1. immnd trace
2. immd  trace
3. mds log
4. syslog 

time stamp:
Mar  7 11:33:58 suseR2-S1 osafimmnd[3053]: ER Failed to load/sync. Giving up 
after 51.019371 seconds, restarting..
Mar  7 11:33:58 suseR2-S1 osafimmnd[3053]: ER IMMND - Periodic server job failed



Attachments:

- 
[mds.log](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/477607e2/6e39/attachment/mds.log)
 (3.6 MB; text/x-log)
- 
[messages](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/477607e2/6e39/attachment/messages)
 (2.4 MB; application/octet-stream)
- 
[osafimmd](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/477607e2/6e39/attachment/osafimmd)
 (12.0 MB; application/octet-stream)
- 
[osafimmnd](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/477607e2/6e39/attachment/osafimmnd)
 (22.4 MB; application/octet-stream)


---

** [tickets:#2349] Immnd faild to load/sync during headless opeartion resulted 
opensaf failed to start on controller**

**Status:** unassigned
**Milestone:** 5.2.RC1
**Created:** Mon Mar 06, 2017 10:06 AM UTC by Ritu Raj
**Last Updated:** Mon Mar 06, 2017 12:11 PM UTC
**Owner:** nobody
**Attachments:**

- 
[osafimmnd.tgz](https://sourceforge.net/p/opensaf/tickets/2349/attachment/osafimmnd.tgz)
 (1.0 MB; application/x-compressed-tar)


Environment details
OS : Suse 64bit
Changeset : 8634 ( 5.2.FC)
6 nodes setup(3 controller and 3 payload)

#Summary
Immnd faild to load/sync during headless opeartion resulted opensaf failed to 
start on controller

Steps followed & Observed behaviour
1. Invkoed headless 
2. after couple of headless opeartion immnd faild to load on one of the 
controller (SC-1) and later opensaf failed to start on same node.
 
 >> The issue is random
 
syslog--
Mar 10 16:52:40 suseR2-S1 **osafimmnd[2987]: ER Failed to load/sync. **Giving 
up after 51.061144 seconds, restarting..
Mar 10 16:52:40 suseR2-S1 opensafd[2873]: ER Could Not RESPAWN IMMND
Mar 10 16:52:40 suseR2-S1 opensafd[2873]: ER Failed   DESC:IMMND
Mar 10 16:52:40 suseR2-S1 opensafd[2873]: ER FAILED TO RESPAWN
Mar 10 16:52:40 suseR2-S1 osafimmnd[2987]: ER IMMND - Periodic server job failed
Mar 10 16:52:40 suseR2-S1 osafimmnd[2987]: ER Failed, exiting...
Mar 10 16:52:40 suseR2-S1 osafimmd[2934]: NO MDS event from svc_id 25 
(change:4, dest:564118002024465)
Mar 10 16:52:41 suseR2-S1 osafclmna[2904]: exiting for shutdown
Mar 10 16:52:41 suseR2-S1 osaffmd[2922]: exiting for shutdown
Mar 10 16:52:41 suseR2-S1 osafimmd[2934]: exiting for shutdown
Mar 10 16:52:42 suseR2-S1 osafrded[2913]: exiting for shutdown
Mar 10 16:52:42 suseR2-S1 osaftransportd[2899]: exiting for shutdown
...
Mar 10 16:52:42 suseR2-S1 kernel: [354116.766597] TIPC: Deactivated
Mar 10 16:52:42 suseR2-S1 opensafd: Starting OpenSAF failed


Notes:
1. Immnd traces attched 


---

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.--
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


[tickets] [opensaf:tickets] #2335 dtm: Fix all Cppcheck 1.77 issues

2017-03-06 Thread A V Mahesh (AVM)
- **status**: accepted --> invalid
- **Comment**:

No CPP (.CC file) erros exist



---

** [tickets:#2335] dtm: Fix all Cppcheck 1.77 issues**

**Status:** invalid
**Milestone:** next
**Created:** Fri Mar 03, 2017 04:12 AM UTC by A V Mahesh (AVM)
**Last Updated:** Fri Mar 03, 2017 04:12 AM UTC
**Owner:** A V Mahesh (AVM)


[staging/src/dtm/dtmnd/dtm_inter_trans.c:337]: (style) Condition 
'NULL!=mov_ptr.next' is always true
[staging/src/dtm/dtmnd/dtm_inter_trans.c:225] -> 
[staging/src/dtm/dtmnd/dtm_inter_trans.c:228]: (style) Variable 'node' is 
reassigned a value before the old one has been used.
[staging/src/dtm/dtmnd/dtm_inter_trans.c:257] -> 
[staging/src/dtm/dtmnd/dtm_inter_trans.c:260]: (style) Variable 'node' is 
reassigned a value before the old one has been used.
[staging/src/dtm/dtmnd/dtm_intra.c:363] -> 
[staging/src/dtm/dtmnd/dtm_intra.c:367]: (style) Variable 'data' is reassigned 
a value before the old one has been used.
[staging/src/dtm/dtmnd/dtm_intra.c:442] -> 
[staging/src/dtm/dtmnd/dtm_intra.c:444]: (style) Variable 'node' is reassigned 
a value before the old one has been used.
[staging/src/dtm/dtmnd/dtm_intra.c:631] -> 
[staging/src/dtm/dtmnd/dtm_intra.c:633]: (style) Variable 'msg_elem' is 
reassigned a value before the old one has been used.
[staging/src/dtm/dtmnd/dtm_intra.c:193]: (information) Skipping configuration 
'MDS_PORT_NUMBER' since the value of 'MDS_PORT_NUMBER' is unknown. Use -D if 
you want to check it. You can use -U to skip it explicitly.
[staging/src/dtm/dtmnd/dtm_intra.c:207]: (information) Skipping configuration 
'MDS_PORT_NUMBER' since the value of 'MDS_PORT_NUMBER' is unknown. Use -D if 
you want to check it. You can use -U to skip it explicitly.
[staging/src/dtm/dtmnd/dtm_intra_svc.c:85] -> 
[staging/src/dtm/dtmnd/dtm_intra_svc.c:88]: (style) Variable 'pid_node' is 
reassigned a value before the old one has been used.
[staging/src/dtm/dtmnd/dtm_intra_svc.c:132] -> 
[staging/src/dtm/dtmnd/dtm_intra_svc.c:133]: (style) Variable 'pid_node' is 
reassigned a value before the old one has been used.
[staging/src/dtm/dtmnd/dtm_intra_svc.c:145] -> 
[staging/src/dtm/dtmnd/dtm_intra_svc.c:147]: (style) Variable 'subscr_tmp' is 
reassigned a value before the old one has been used.
[staging/src/dtm/dtmnd/dtm_intra_svc.c:175] -> 
[staging/src/dtm/dtmnd/dtm_intra_svc.c:176]: (style) Variable 'svc_node' is 
reassigned a value before the old one has been used.
[staging/src/dtm/dtmnd/dtm_intra_svc.c:270] -> 
[staging/src/dtm/dtmnd/dtm_intra_svc.c:272]: (style) Variable 'pid_node' is 
reassigned a value before the old one has been used.
[staging/src/dtm/dtmnd/dtm_intra_svc.c:379] -> 
[staging/src/dtm/dtmnd/dtm_intra_svc.c:398]: (style) Variable 'pid_node' is 
reassigned a value before the old one has been used.
[staging/src/dtm/dtmnd/dtm_intra_svc.c:476] -> 
[staging/src/dtm/dtmnd/dtm_intra_svc.c:478]: (style) Variable 'pid_node' is 
reassigned a value before the old one has been used.
[staging/src/dtm/dtmnd/dtm_intra_svc.c:485] -> 
[staging/src/dtm/dtmnd/dtm_intra_svc.c:497]: (style) Variable 'subscr_node' is 
reassigned a value before the old one has been used.
[staging/src/dtm/dtmnd/dtm_intra_svc.c:590] -> 
[staging/src/dtm/dtmnd/dtm_intra_svc.c:592]: (style) Variable 'pid_node' is 
reassigned a value before the old one has been used.
[staging/src/dtm/dtmnd/dtm_intra_svc.c:602] -> 
[staging/src/dtm/dtmnd/dtm_intra_svc.c:605]: (style) Variable 'data_subscr' is 
reassigned a value before the old one has been used.
[staging/src/dtm/dtmnd/dtm_intra_svc.c:643] -> 
[staging/src/dtm/dtmnd/dtm_intra_svc.c:645]: (style) Variable 'pid_node' is 
reassigned a value before the old one has been used.
[staging/src/dtm/dtmnd/dtm_intra_svc.c:701] -> 
[staging/src/dtm/dtmnd/dtm_intra_svc.c:703]: (style) Variable 'pid_node' is 
reassigned a value before the old one has been used.
[staging/src/dtm/dtmnd/dtm_intra_svc.c:1316] -> 
[staging/src/dtm/dtmnd/dtm_intra_svc.c:1321]: (style) Variable 'local_svc_info' 
is reassigned a value before the old one has been used.
[staging/src/dtm/dtmnd/dtm_intra_svc.c:1353] -> 
[staging/src/dtm/dtmnd/dtm_intra_svc.c:1354]: (style) Variable 'pid_node' is 
reassigned a value before the old one has been used.
[staging/src/dtm/dtmnd/dtm_intra_svc.c:1577] -> 
[staging/src/dtm/dtmnd/dtm_intra_svc.c:1578]: (style) Variable 'node' is 
reassigned a value before the old one has been used.
[staging/src/dtm/dtmnd/dtm_intra_svc.c:1669] -> 
[staging/src/dtm/dtmnd/dtm_intra_svc.c:1670]: (style) Variable 'node' is 
reassigned a value before the old one has been used.
[staging/src/dtm/dtmnd/dtm_intra_svc.c:1711] -> 
[staging/src/dtm/dtmnd/dtm_intra_svc.c:1716]: (style) Variable 'svc_info' is 
reassigned a value before the old one has been used.
[staging/src/dtm/dtmnd/dtm_intra_svc.c:1840] -> 
[staging/src/dtm/dtmnd/dtm_intra_svc.c:1846]: (style) Variable 'svc_info' is 
reassigned a value before the old one has been used.
[staging/src/dtm/dtmnd/dtm_intra_svc.c:1964] -> 

[tickets] [opensaf:tickets] #2334 clm: Fix all Cppcheck 1.77 issue

2017-03-06 Thread A V Mahesh (AVM)
- **status**: accepted --> wontfix
- **Comment**:

No .cc files sof far in CLM



---

** [tickets:#2334] clm: Fix all Cppcheck 1.77 issue **

**Status:** wontfix
**Milestone:** next
**Created:** Fri Mar 03, 2017 04:09 AM UTC by A V Mahesh (AVM)
**Last Updated:** Fri Mar 03, 2017 04:09 AM UTC
**Owner:** A V Mahesh (AVM)


[staging/src/clm/clmd/clms_evt.c:602] -> [staging/src/clm/clmd/clms_evt.c:545]: 
(warning) Either the condition 'node!=NULL' is redundant or there is possible 
null pointer dereference: node.
[staging/src/clm/clmd/clms_evt.c:603] -> [staging/src/clm/clmd/clms_evt.c:545]: 
(warning) Either the condition 'node!=NULL' is redundant or there is possible 
null pointer dereference: node.
[staging/src/clm/clmd/clms_evt.c:618]: (warning) Possible null pointer 
dereference: ip
[staging/src/clm/clmd/clms_evt.c:101] -> [staging/src/clm/clmd/clms_evt.c:104]: 
(style) Variable 'clma_down_rec' is reassigned a value before the old one has 
been used.
[staging/src/clm/clmd/clms_evt.c:177] -> [staging/src/clm/clmd/clms_evt.c:182]: 
(style) Variable 'client' is reassigned a value before the old one has been 
used.
[staging/src/clm/clmd/clms_evt.c:188] -> [staging/src/clm/clmd/clms_evt.c:191]: 
(style) Variable 'rc' is reassigned a value before the old one has been used.
[staging/src/clm/clmd/clms_evt.c:504] -> [staging/src/clm/clmd/clms_evt.c:521]: 
(style) Variable 'node' is reassigned a value before the old one has been used.
[staging/src/clm/clmd/clms_evt.c:678] -> [staging/src/clm/clmd/clms_evt.c:683]: 
(style) Variable 'node_name' is reassigned a value before the old one has been 
used.
[staging/src/clm/clmd/clms_evt.c:679] -> [staging/src/clm/clmd/clms_evt.c:684]: 
(style) Variable 'op_node' is reassigned a value before the old one has been 
used.
[staging/src/clm/clmd/clms_evt.c:677] -> [staging/src/clm/clmd/clms_evt.c:687]: 
(style) Variable 'rc' is reassigned a value before the old one has been used.
[staging/src/clm/clmd/clms_evt.c:873] -> [staging/src/clm/clmd/clms_evt.c:877]: 
(style) Variable 'node' is reassigned a value before the old one has been used.
[staging/src/clm/clmd/clms_evt.c:1039] -> 
[staging/src/clm/clmd/clms_evt.c:1048]: (style) Variable 'op_node' is 
reassigned a value before the old one has been used.
[staging/src/clm/clmd/clms_evt.c:1134] -> 
[staging/src/clm/clmd/clms_evt.c:1142]: (style) Variable 'node' is reassigned a 
value before the old one has been used.
[staging/src/clm/clmd/clms_evt.c:1236] -> 
[staging/src/clm/clmd/clms_evt.c:1240]: (style) Variable 'node' is reassigned a 
value before the old one has been used.
[staging/src/clm/clmd/clms_evt.c:2028] -> 
[staging/src/clm/clmd/clms_evt.c:2036]: (style) Variable 'mds_rc' is reassigned 
a value before the old one has been used.
[staging/src/clm/clmd/clms_evt.c:2046] -> 
[staging/src/clm/clmd/clms_evt.c:2052]: (style) Variable 'node_down_rec' is 
reassigned a value before the old one has been used.
[staging/src/clm/clmd/clms_imm.c:178] -> [staging/src/clm/clmd/clms_imm.c:184]: 
(style) Variable 'node' is reassigned a value before the old one has been used.
[staging/src/clm/clmd/clms_imm.c:275] -> [staging/src/clm/clmd/clms_imm.c:295]: 
(style) Variable 'rc' is reassigned a value before the old one has been used.
[staging/src/clm/clmd/clms_imm.c:335] -> [staging/src/clm/clmd/clms_imm.c:352]: 
(style) Variable 'rc' is reassigned a value before the old one has been used.
[staging/src/clm/clmd/clms_imm.c:690] -> [staging/src/clm/clmd/clms_imm.c:693]: 
(style) Variable 'node' is reassigned a value before the old one has been used.
[staging/src/clm/clmd/clms_imm.c:993] -> [staging/src/clm/clmd/clms_imm.c:996]: 
(style) Variable 'trk' is reassigned a value before the old one has been used.
[staging/src/clm/clmd/clms_imm.c:1721] -> 
[staging/src/clm/clmd/clms_imm.c:1726]: (style) Variable 'node' is reassigned a 
value before the old one has been used.
[staging/src/clm/clmd/clms_imm.c:1998] -> 
[staging/src/clm/clmd/clms_imm.c:2004]: (style) Variable 'node' is reassigned a 
value before the old one has been used.
[staging/src/clm/clmd/clms_imm.c:1527]: (style) The scope of the variable 'i' 
can be reduced.
[staging/src/clm/clmd/clms_imm.c:1528]: (style) The scope of the variable 
'attrMod' can be reduced.
[staging/src/clm/clmd/clms_imm.c:1529]: (style) The scope of the variable 
'name' can be reduced.
[staging/src/clm/clmd/clms_imm.c:557]: (style) Variable 'attr_Mod' is assigned 
a value that is never used.
[staging/src/clm/clmd/clms_imm.c:649]: (style) Variable 'attr_Mod' is assigned 
a value that is never used.
[staging/src/clm/clmd/clms_imm.c:829]: (style) Variable 'attr_Mod' is assigned 
a value that is never used.
[staging/src/clm/clmd/clms_main.c:329]: (style) Suspicious condition 
(assignment + comparison); Clarify expression with parentheses.
[staging/src/clm/clmd/clms_main.c:87] -> [staging/src/clm/clmd/clms_main.c:91]: 
(style) Variable 'evt' is reassigned a value before the old one has been used.

[tickets] [opensaf:tickets] #2178 MDS: mdstest 13 14 failed

2017-03-06 Thread A V Mahesh (AVM)
- **status**: review --> fixed
- **Comment**:

changeset:   8650:b1794d3c341d
tag: tip
user:Hoang Vo 
date:Tue Mar 07 09:57:48 2017 +0530
summary: mdstest: correct test cases [#2178]



---

** [tickets:#2178] MDS: mdstest 13 14 failed**

**Status:** fixed
**Milestone:** 5.2.RC1
**Created:** Tue Nov 08, 2016 06:58 AM UTC by Quyen Dao
**Last Updated:** Mon Mar 06, 2017 07:51 AM UTC
**Owner:** Vo Minh Hoang
**Attachments:**

- 
[mdstest_13_14_mds.log](https://sourceforge.net/p/opensaf/tickets/2178/attachment/mdstest_13_14_mds.log)
 (65.8 kB; application/octet-stream)


Changeset: 8287:bcc7af78a5a7
OS: Ubuntu 16.04
MDS transport: TCP

root@SC-1:~# export MDS_LOG_LEVEL=5
root@SC-1:~# mdstest 13 14

Suite 13: Direct Just Send test cases
/ntet_initialise_setup: Get an ADEST handle,Create PWE=2 on ADEST,Install 
EXTMIN and INTMIN svc on ADEST,Install INTMIN,EXTMIN services on ADEST's PWE=2,
Create VDEST 100 and VDEST 200,Change the role of VDEST 200 to ACTIVE,
Install EXTMIN  service on VDEST 100,Install INTMIN, EXTMIN services on 
VDEST 200

ADEST <2010f021f > : GET_HDLS is SUCCESSFUL
 100 : VDEST_CREATE is SUCCESSFUL
 200 : VDEST_CREATE is SUCCESSFUL
VDEST_CHANGE ROLE to 1 is SUCCESSFULL
PWE_CREATE is SUCCESSFUL : PWE = 2
 256 : SERVICE INSTALL is SUCCESSFULL
 512 : SERVICE INSTALL is SUCCESSFULL
 256 : SERVICE INSTALL is SUCCESSFULL
 512 : SERVICE INSTALL is SUCCESSFULL
 512 : SERVICE INSTALL is SUCCESSFULL
 256 : SERVICE INSTALL is SUCCESSFULL
 512 : SERVICE INSTALL is SUCCESSFULL
 MDS SERVICE SUBSCRIBE is SUCCESSFULL
The Subscriber Service id = 512 is on ADEST
UP: Subscribed Svc = 512 with svc pvt ver = 1 is UP on dest=  anchor= <0> 
role= 1 with PWE id = 1 on node = 2010f

The Subscriber Service id = 512 is on ADEST
UP: Subscribed Svc = 512 with svc pvt ver = 3 is UP on dest= <2010f021f> 
anchor= <0> role= 1 with PWE id = 1 on node = 2010f

 MDS RETRIEVE is SUCCESSFULL
Test Case 14: Not able to send a message of size >(MDS_DIRECT_BUF_MAXSIZE) to 
2000

Request to ncsmds_api: MDS DIRECT SEND is SUCCESSFULL
Fail

Cancel subscription

 MDS CANCEL SUBSCRIBE is SUCCESSFULLUninstalling the services on both 
VDESTs and ADEST

 UnInstalling the Services on both the VDESTs

 MDS RETRIEVE is SUCCESSFULL
 512 : SERVICE UNINSTALL is SUCCESSFULL
 MDS RETRIEVE is SUCCESSFULL
 256 : SERVICE UNINSTALL is SUCCESSFULL
 MDS RETRIEVE is SUCCESSFULL
 512 : SERVICE UNINSTALL is SUCCESSFULL
Destroying the VDESTS
Destroying both the VDESTs and PWE=2 on ADEST

VDEST_CHANGE ROLE to 2 is SUCCESSFULL
 200 : VDEST_DESTROY is SUCCESSFULL
VDEST_CHANGE ROLE to 2 is SUCCESSFULL
 100 : VDEST_DESTROY is SUCCESSFULL
Direct Receive callback
 The Sender service is = 512 is on <2010f021f> destination with anchor = 
<2010f021f> on Node = 2010f with msg fmt ver=1

The Receiver service is = 512 is on <2010f021f> destination

Received Message len = 8002 and the message 
is=sss
 
s
 

[tickets] [opensaf:tickets] #2326 log : fix all cpp check issues

2017-03-06 Thread A V Mahesh (AVM)
- **status**: review --> fixed
- **Comment**:

changeset:   8649:4a94f841107b
tag: tip
user:A V Mahesh 
date:Tue Mar 07 09:44:44 2017 +0530
summary: log: Fix all Cppcheck 1.77 issues [#2326]



---

** [tickets:#2326] log : fix all cpp check issues **

**Status:** fixed
**Milestone:** next
**Created:** Mon Feb 27, 2017 03:40 AM UTC by A V Mahesh (AVM)
**Last Updated:** Tue Feb 28, 2017 06:47 AM UTC
**Owner:** A V Mahesh (AVM)


[staging/src/log/logd/lgs_config.h:90]: (performance) Function parameter 
param_name should be passed by reference.
[staging/src/log/logd/lgs_config.h:230]: (performance) Function parameter 
attribute_name should be passed by reference.
[staging/src/log/logd/lgs_config.h:231]: (performance) Function parameter 
value_list should be passed by reference.
[staging/src/log/logd/lgs_config.h:238]: (performance) Function parameter 
attribute_name should be passed by reference.
[staging/src/log/logd/lgs_config.h:239]: (performance) Function parameter 
value_list should be passed by reference.
[staging/src/log/logd/lgs_clm.cc:137]: (style) The scope of the variable 
clm_node can be reduced.
[staging/src/log/logd/lgs_clm.cc:220]: (performance) Prefer prefix ++/-- 
operators for non-primitive types.
[staging/src/log/logd/lgs_config.cc:401] -> 
[staging/src/log/logd/lgs_config.cc:498]: (warning) Either the condition 
allocmem_ptr!=NULL is redundant or there is possible null pointer dereference: 
param_ptr.
[staging/src/log/logd/lgs_config.cc:410] -> 
[staging/src/log/logd/lgs_config.cc:498]: (warning) Either the condition 
allocmem_ptr!=NULL is redundant or there is possible null pointer dereference: 
param_ptr.
[staging/src/log/logd/lgs_config.cc:184] -> 
[staging/src/log/logd/lgs_config.cc:190]: (style) Variable cfg_param_str is 
reassigned a value before the old one has been used.
[staging/src/log/logd/lgs_config.cc:183]: (style) The scope of the variable 
prev_size can be reduced.
[staging/src/log/logd/lgs_config.cc:727]: (style) The scope of the variable 
nl_cnt can be reduced.
[staging/src/log/logd/lgs_config.cc:995]: (style) The scope of the variable 
value_string can be reduced.
[staging/src/log/logd/lgs_config.cc:1034]: (style) The scope of the variable n 
can be reduced.
[staging/src/log/logd/lgs_config.cc:142]: (warning) Member variable 
_lgs_conf_t::chkp_file_close_time is not initialized in the constructor.
[staging/src/log/logd/lgs_config.cc:293]: (performance) Function parameter 
attribute_name should be passed by reference.
[staging/src/log/logd/lgs_config.cc:294]: (performance) Function parameter 
value_list should be passed by reference.
[staging/src/log/logd/lgs_config.cc:324]: (performance) Function parameter 
attribute_name should be passed by reference.
[staging/src/log/logd/lgs_config.cc:325]: (performance) Function parameter 
value_list should be passed by reference.
[staging/src/log/logd/lgs_evt.cc:531] -> [staging/src/log/logd/lgs_evt.cc:536]: 
(style) Variable lga_down_rec is reassigned a value before the old one has been 
used.
[staging/src/log/logd/lgs_evt.cc:416]: (style) The scope of the variable 
ckpt_ptr can be reduced.
[staging/src/log/logd/lgs_evt.cc:553]: (style) The scope of the variable stream 
can be reduced.
[staging/src/log/logd/lgs_evt.cc:163]: (error) Mismatching allocation and 
deallocation: client
[staging/src/log/logd/lgs_evt.cc:168]: (error) Mismatching allocation and 
deallocation: client
[staging/src/log/logd/lgs_evt.cc:344]: (performance) Prefer prefix ++/-- 
operators for non-primitive types.
[staging/src/log/logd/lgs_filehdl.cc:542]: (style) Variable len is assigned a 
value that is never used.
[staging/src/log/logd/lgs_fmt.cc:560]: (style) The scope of the variable no_ch 
can be reduced.
[staging/src/log/logd/lgs_imm.cc:3478] -> 
[staging/src/log/logd/lgs_imm.cc:3479]: (warning) Either the condition 
attribute!=NULL is redundant or there is possible null pointer dereference: 
attribute.
[staging/src/log/logd/lgs_imm.cc:963]: (style) The scope of the variable i can 
be reduced.
[staging/src/log/logd/lgs_imm.cc:1885]: (style) The scope of the variable 
current_time can be reduced.
[staging/src/log/logd/lgs_imm.cc:1924]: (style) The scope of the variable 
stream can be reduced.
[staging/src/log/logd/lgs_imm.cc:3264]: (style) The scope of the variable 
name_str can be reduced.
[staging/src/log/logd/lgs_imm.cc:3474]: (style) The scope of the variable value 
can be reduced.
[staging/src/log/logd/lgs_imm_gcfg.cc:857] -> 
[staging/src/log/logd/lgs_imm_gcfg.cc:859]: (style) Variable rc is reassigned a 
value before the old one has been used.
[staging/src/log/logd/lgs_imm_gcfg.cc:532]: (style) The scope of the variable 
name_len can be reduced.
[staging/src/log/logd/lgs_imm_gcfg.cc:940]: (style) The scope of the variable 
rc can be reduced.
[staging/src/log/logd/lgs_main.cc:319]: (style) Suspicious condition 
(assignment + comparison); Clarify expression with parentheses.

[tickets] [opensaf:tickets] #2350 mds: reduce log level to Err for TIPC_ERR_OVERLOAD in syslog

2017-03-06 Thread A V Mahesh (AVM)
- **status**: accepted --> review



---

** [tickets:#2350] mds: reduce log level to Err for TIPC_ERR_OVERLOAD in syslog 
**

**Status:** review
**Milestone:** 5.2.RC1
**Created:** Tue Mar 07, 2017 03:21 AM UTC by A V Mahesh (AVM)
**Last Updated:** Tue Mar 07, 2017 03:21 AM UTC
**Owner:** A V Mahesh (AVM)


 CR MDTM: undelivered message condition ancillary data: TIPC_ERR_OVERLOAD
 CR MDTM: undelivered message condition ancillary data: TIPC_RETDATA

Note : MDS still maintained as MDS_LOG_CRITICAL


---

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.--
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


[tickets] [opensaf:tickets] #2350 mds: reduce log level to Err for TIPC_ERR_OVERLOAD in syslog

2017-03-06 Thread A V Mahesh (AVM)



---

** [tickets:#2350] mds: reduce log level to Err for TIPC_ERR_OVERLOAD in syslog 
**

**Status:** accepted
**Milestone:** 5.2.RC1
**Created:** Tue Mar 07, 2017 03:21 AM UTC by A V Mahesh (AVM)
**Last Updated:** Tue Mar 07, 2017 03:21 AM UTC
**Owner:** A V Mahesh (AVM)


 CR MDTM: undelivered message condition ancillary data: TIPC_ERR_OVERLOAD
 CR MDTM: undelivered message condition ancillary data: TIPC_RETDATA

Note : MDS still maintained as MDS_LOG_CRITICAL


---

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.--
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


[tickets] [opensaf:tickets] #2339 CLM : Cluster reset doesn't succed as "reboot now" command fails on SLES

2017-03-06 Thread Hans Nordebäck
- **status**: accepted --> review



---

** [tickets:#2339] CLM : Cluster reset doesn't succed as "reboot now" command 
fails on SLES**

**Status:** review
**Milestone:** 5.2.RC1
**Created:** Fri Mar 03, 2017 06:05 AM UTC by Srikanth R
**Last Updated:** Mon Mar 06, 2017 03:04 PM UTC
**Owner:** Hans Nordebäck


Changeset : 8634 5.2.FC
SLES TIPC setup with one controller.


 Once the controller is brought up with opensaf 5.2.FC, the following cluster 
reset command is issued.
 
 immadm -o 4  safCluster=myClmCluster
 
 The command failed with the following log.
 
Mar 11 16:09:52 SUSE-S1-C1 osafclmd[6772]: Command: 
/usr/lib64/opensaf/opensaf_reboot 0 not_used 1 failed, rc = 256


On SLES, "reboot now" command fails. Instead "shutdown -r now"  should be 
invoked for graceful shutdown. 


---

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] #2339 CLM : Cluster reset doesn't succed as "reboot now" command fails on SLES

2017-03-06 Thread Hans Nordebäck
- **status**: unassigned --> accepted
- **assigned_to**: Hans Nordebäck



---

** [tickets:#2339] CLM : Cluster reset doesn't succed as "reboot now" command 
fails on SLES**

**Status:** accepted
**Milestone:** 5.2.RC1
**Created:** Fri Mar 03, 2017 06:05 AM UTC by Srikanth R
**Last Updated:** Mon Mar 06, 2017 11:47 AM UTC
**Owner:** Hans Nordebäck


Changeset : 8634 5.2.FC
SLES TIPC setup with one controller.


 Once the controller is brought up with opensaf 5.2.FC, the following cluster 
reset command is issued.
 
 immadm -o 4  safCluster=myClmCluster
 
 The command failed with the following log.
 
Mar 11 16:09:52 SUSE-S1-C1 osafclmd[6772]: Command: 
/usr/lib64/opensaf/opensaf_reboot 0 not_used 1 failed, rc = 256


On SLES, "reboot now" command fails. Instead "shutdown -r now"  should be 
invoked for graceful shutdown. 


---

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] #2145 SMF: add support for detection of asynchronous failures of AMF entities

2017-03-06 Thread Alex Jones
- **status**: review --> fixed
- **Comment**:

changeset:   8648:bdb733a7f7da
tag: tip
user:Alex Jones 
date:Mon Mar 06 09:18:16 2017 -0500
summary: smf: add support for asynchronous detection of failed AMF entities 
[#2145]




---

** [tickets:#2145] SMF: add support for detection of asynchronous failures of 
AMF entities**

**Status:** fixed
**Milestone:** 5.2.RC1
**Created:** Thu Oct 27, 2016 04:42 PM UTC by Alex Jones
**Last Updated:** Mon Oct 31, 2016 08:34 PM UTC
**Owner:** Alex Jones


This ticket adds support for Section 4.2.1.3 of SMF A.01.02 spec: Detection of 
Asynchronous Failures of AMF Entities. The ticket which does the AMF related 
work is 2144.



---

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] #2072 log: examples is not correct in OpenSAF_LOGSv_PR.odt document

2017-03-06 Thread Vu Minh Nguyen
- **status**: unassigned --> duplicate
- **assigned_to**: Canh Truong -->  nobody 
- **Comment**:

The info will be updated in [#2200]. Change the status to duplicated to avoid 
confusion. 



---

** [tickets:#2072] log: examples is not correct in OpenSAF_LOGSv_PR.odt 
document**

**Status:** duplicate
**Milestone:** 4.7.2
**Created:** Tue Sep 27, 2016 11:37 AM UTC by Canh Truong
**Last Updated:** Mon Oct 03, 2016 09:39 AM UTC
**Owner:** nobody


The example  is not correct in OpenSAF_LOGSv_PR.odt :

saflogger -a safLgStrCfg=Test -f testLogFile "Hello world"
*Will make an application stream named “safLgStrCfg=Test” and send “Hello 
world” logbuffer to the log file name “testLogFile”.*

root@SC-1:~# saflogger -a safLgStrCfg=Test -f testLogFile "Hello world"
saLogStreamOpen_2 FAILED: SA_AIS_ERR_INVALID_PARAM (7)

The RDN of runtime stream is "safLgStr=". So we use "safLgStr=...instead of 
"safLgStrCfg=..." in command saflogger.



---

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] #2200 log: Update the PR documentation for 5.2 release

2017-03-06 Thread Vu Minh Nguyen
- **summary**: log: no document saLogStreamLogFileFormat value depending on 
logMaxLogrecsize --> log: Update the PR documentation for 5.2 release
- Description has changed:

Diff:



--- old
+++ new
@@ -5,3 +5,4 @@
 Also update the PR due to tickets:
  log: implement SaLogFilterSetCallbackT [#2146]
  log: add alternative destinations of log records [#2258]
+ log: examples is not correct [#2072] 






---

** [tickets:#2200] log: Update the PR documentation for 5.2 release**

**Status:** review
**Milestone:** 5.2.RC1
**Created:** Wed Nov 23, 2016 07:23 AM UTC by Vu Minh Nguyen
**Last Updated:** Mon Mar 06, 2017 12:21 PM UTC
**Owner:** elunlen


The attribute `saLogStreamFixedLogRecordSize` value of log streams can be set 
to zero (flexilble log record) or an specific number, but must not be larger 
than `logMaxLogrecsize` attribute value which belongs to `OpenSafLogConfig` 
class.

`saLogStreamFixedLogRecordSize` value is limited by `logMaxLogrecsize`. This 
info should be described in PR documentation.

Also update the PR due to tickets:
 log: implement SaLogFilterSetCallbackT [#2146]
 log: add alternative destinations of log records [#2258]
 log: examples is not correct [#2072] 


---

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] #2200 log: no document saLogStreamLogFileFormat value depending on logMaxLogrecsize

2017-03-06 Thread Vu Minh Nguyen
- **status**: accepted --> review



---

** [tickets:#2200] log: no document saLogStreamLogFileFormat value depending on 
logMaxLogrecsize**

**Status:** review
**Milestone:** 5.2.RC1
**Created:** Wed Nov 23, 2016 07:23 AM UTC by Vu Minh Nguyen
**Last Updated:** Mon Mar 06, 2017 12:18 PM UTC
**Owner:** elunlen


The attribute `saLogStreamFixedLogRecordSize` value of log streams can be set 
to zero (flexilble log record) or an specific number, but must not be larger 
than `logMaxLogrecsize` attribute value which belongs to `OpenSafLogConfig` 
class.

`saLogStreamFixedLogRecordSize` value is limited by `logMaxLogrecsize`. This 
info should be described in PR documentation.

Also update the PR due to tickets:
 log: implement SaLogFilterSetCallbackT [#2146]
 log: add alternative destinations of log records [#2258]


---

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] #2200 log: no document saLogStreamLogFileFormat value depending on logMaxLogrecsize

2017-03-06 Thread Vu Minh Nguyen
Hi Lennart,

This ticket was originally written for updating the information about 
`saLogStreamFixedLogRecordSize` attribute.

We have to state something like "`saLogStreamFixedLogRecordSize` attribute 
value of log streams can be set to zero (flexilble log record) or an specific 
number, but must not be larger than `logMaxLogrecsize` attribute value which 
belongs to OpenSafLogConfig class."

Should we put above info toghether with updating info regarding: 
1) log: implement SaLogFilterSetCallbackT [#2146]
2) log: add alternative destinations of log records [#2258]

Regards, Vu


---

** [tickets:#2200] log: no document saLogStreamLogFileFormat value depending on 
logMaxLogrecsize**

**Status:** accepted
**Milestone:** 5.2.RC1
**Created:** Wed Nov 23, 2016 07:23 AM UTC by Vu Minh Nguyen
**Last Updated:** Mon Mar 06, 2017 11:44 AM UTC
**Owner:** elunlen


The attribute `saLogStreamFixedLogRecordSize` value of log streams can be set 
to zero (flexilble log record) or an specific number, but must not be larger 
than `logMaxLogrecsize` attribute value which belongs to `OpenSafLogConfig` 
class.

`saLogStreamFixedLogRecordSize` value is limited by `logMaxLogrecsize`. This 
info should be described in PR documentation.

Also update the PR due to tickets:
 log: implement SaLogFilterSetCallbackT [#2146]
 log: add alternative destinations of log records [#2258]


---

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] #2343 IMM: immnd failed to spawn while starting opensaf on controller

2017-03-06 Thread Neelakanta Reddy
share immnd, immd and mds.log 


---

** [tickets:#2343] IMM: immnd failed to spawn while starting opensaf on 
controller**

**Status:** unassigned
**Milestone:** 5.2.RC1
**Created:** Fri Mar 03, 2017 11:46 AM UTC by Chani Srivastava
**Last Updated:** Fri Mar 03, 2017 11:46 AM UTC
**Owner:** nobody


**Environment details**

OS : Suse 64bit
Changeset : 8634 ( 5.2.FC)
Setup : 4 nodes ( 2 controllers and 2 payloads with 1PBE enabled )

Summary

immnd failed to spawn a number of times while starting openSaf on controller.
This issue is observed in various situations

1. While resetting cluster and starting OpenSaf again
2. While invoking continuous failovers.
3. While stoping and starting openSaf on standby controller.



Mar  3 15:45:49 OSAF-SC1 opensafd: Starting OpenSAF Services(5.2.FC - ) (Using 
TIPC)
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.828240] TIPC: Activated (version 2.0.0)
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.828391] NET: Registered protocol family 
30
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.828393] TIPC: Started in single node 
mode
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.834836] TIPC: Started in network mode
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.834839] TIPC: Own node address <1.1.1>, 
network identity 4141
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.838982] TIPC: Enabled bearer 
, discovery domain <1.1.0>, priority 10
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.840611] TIPC: Established link 
<1.1.1:eth1-1.1.2:eth1> on network plane A
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.840688] TIPC: Established link 
<1.1.1:eth1-1.1.3:eth1> on network plane A
Mar  3 15:45:49 OSAF-SC1 osaftransportd[3854]: mkfifo already exists: 
/var/lib/opensaf/osaftransportd.fifo File exists
Mar  3 15:45:49 OSAF-SC1 osaftransportd[3854]: Started
Mar  3 15:45:49 OSAF-SC1 opensafd[3830]: NO Monitoring of TRANSPORT started
Mar  3 15:45:50 OSAF-SC1 osafclmna[3861]: mkfifo already exists: 
/var/lib/opensaf/osafclmna.fifo File exists
Mar  3 15:45:50 OSAF-SC1 osafclmna[3861]: Started
Mar  3 15:45:50 OSAF-SC1 opensafd[3830]: NO Monitoring of CLMNA started
Mar  3 15:45:50 OSAF-SC1 osafclmna[3861]: NO 
safNode=SC-1,safCluster=myClmCluster Joined cluster, nodeid=2010f
Mar  3 15:45:50 OSAF-SC1 osafrded[3870]: mkfifo already exists: 
/var/lib/opensaf/osafrded.fifo File exists
Mar  3 15:45:50 OSAF-SC1 osafrded[3870]: Started
Mar  3 15:45:50 OSAF-SC1 osaffmd[3879]: mkfifo already exists: 
/var/lib/opensaf/osaffmd.fifo File exists
Mar  3 15:45:50 OSAF-SC1 osaffmd[3879]: Started
Mar  3 15:45:50 OSAF-SC1 osaffmd[3879]: NO Remote fencing is disabled
Mar  3 15:45:50 OSAF-SC1 opensafd[3830]: NO Monitoring of HLFM started
Mar  3 15:45:50 OSAF-SC1 osafimmd[3889]: mkfifo already exists: 
/var/lib/opensaf/osafimmd.fifo File exists
Mar  3 15:45:50 OSAF-SC1 osafimmd[3889]: Started
Mar  3 15:45:50 OSAF-SC1 opensafd[3830]: NO Monitoring of IMMD started
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: mkfifo already exists: 
/var/lib/opensaf/osafimmnd.fifo File exists
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: Started
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: NO Persistent Back-End capability 
configured, Pbe file:imm.db (suffix may get added)
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: NO IMMD service is UP ... 
ScAbsenseAllowed?:0 introduced?:0
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: NO SERVER STATE: IMM_SERVER_ANONYMOUS 
--> IMM_SERVER_CLUSTER_WAITING
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: NO SERVER STATE: 
IMM_SERVER_CLUSTER_WAITING --> IMM_SERVER_LOADING_PENDING
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: NO SERVER STATE: 
IMM_SERVER_LOADING_PENDING --> IMM_SERVER_SYNC_PENDING
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: NO NODE STATE-> IMM_NODE_ISOLATED
Mar  3 15:45:51 OSAF-SC1 osafimmnd[3900]: NO NODE STATE-> IMM_NODE_W_AVAILABLE
Mar  3 15:45:51 OSAF-SC1 osafimmnd[3900]: NO SERVER STATE: 
IMM_SERVER_SYNC_PENDING --> IMM_SERVER_SYNC_CLIENT
Mar  3 15:51:01 OSAF-SC1 osafimmnd[3900]: WA Global ABORT SYNC received for 
epoch 508
Mar  3 15:51:01 OSAF-SC1 osafimmnd[3900]: WA SERVER STATE: 
IMM_SERVER_SYNC_CLIENT --> IMM_SERVER_LOADING_PENDING (sync aborted)
Mar  3 15:51:01 OSAF-SC1 osafimmnd[3900]: NO NODE STATE-> IMM_NODE_UNKNOW 2827
Mar  3 15:51:01 OSAF-SC1 osafimmnd[3900]: NO Abort sync: Discarding synced 
objects
Mar  3 15:51:04 OSAF-SC1 osafimmnd[3900]: NO Abort sync: Discarding synced 
classes
Mar  3 15:51:04 OSAF-SC1 osafimmnd[3900]: NO SERVER STATE: 
IMM_SERVER_LOADING_PENDING --> IMM_SERVER_SYNC_PENDING
Mar  3 15:51:05 OSAF-SC1 osafimmnd[3900]: NO NODE STATE-> IMM_NODE_ISOLATED
Mar  3 15:51:06 OSAF-SC1 osafimmnd[3900]: NO NODE STATE-> IMM_NODE_W_AVAILABLE
Mar  3 15:51:06 OSAF-SC1 osafimmnd[3900]: NO SERVER STATE: 
IMM_SERVER_SYNC_PENDING --> IMM_SERVER_SYNC_CLIENT
Mar  3 15:51:41 OSAF-SC1 osafimmnd[3900]: NO Implementer connected: 1223 
(RUNTIMEIMPL) <0, 2030f>
Mar  3 15:53:50 OSAF-SC1 opensafd[3830]: ER Timed-out for response from IMMND
Mar  3 15:53:50 OSAF-SC1 opensafd[3830]: ER 
Mar  3 15:53:50 OSAF-SC1 opensafd[3830]: ER Going for recovery
Mar  3 

[tickets] [opensaf:tickets] #2344 log: leak memory in unix domain socket destination handler

2017-03-06 Thread Vu Minh Nguyen
- **status**: assigned --> review



---

** [tickets:#2344] log: leak memory in unix domain socket destination handler**

**Status:** review
**Milestone:** 5.2.RC1
**Created:** Sun Mar 05, 2017 05:41 PM UTC by Vu Minh Nguyen
**Last Updated:** Sun Mar 05, 2017 05:41 PM UTC
**Owner:** Vu Minh Nguyen


When updating the data store in the configuration handler a dynamic buffer is 
used. Data is added to this buffer using function lgs_cfgupd_list_create() 
which is also used by the help function lgs_cfgupd_mutival_replace(). When the 
buffer is created and expanded when adding more attributes memory is allocated 
that must be freed when the buffer is no longer used. 

In function `void DestinationHandler::UpdateRtDestStatus()`, it uses 
`lgs_cfgupd_mutival_replace()` to update `logRecordDestinationStatus` but not 
freeing buffer at the end of the function.

The allocated buffer needs to be freed by following code line:

```C
  // Free memory allocated for the config_data buffer
  if (config_data.ckpt_buffer_ptr != NULL)
free(config_data.ckpt_buffer_ptr);
```
 



---

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] #2349 Immnd faild to load/sync during headless opeartion resulted opensaf failed to start on controller

2017-03-06 Thread Neelakanta Reddy
share corrsponding immd traces and mds.log


---

** [tickets:#2349] Immnd faild to load/sync during headless opeartion resulted 
opensaf failed to start on controller**

**Status:** unassigned
**Milestone:** 5.2.RC1
**Created:** Mon Mar 06, 2017 10:06 AM UTC by Ritu Raj
**Last Updated:** Mon Mar 06, 2017 12:04 PM UTC
**Owner:** nobody
**Attachments:**

- 
[osafimmnd.tgz](https://sourceforge.net/p/opensaf/tickets/2349/attachment/osafimmnd.tgz)
 (1.0 MB; application/x-compressed-tar)


Environment details
OS : Suse 64bit
Changeset : 8634 ( 5.2.FC)
6 nodes setup(3 controller and 3 payload)

#Summary
Immnd faild to load/sync during headless opeartion resulted opensaf failed to 
start on controller

Steps followed & Observed behaviour
1. Invkoed headless 
2. after couple of headless opeartion immnd faild to load on one of the 
controller (SC-1) and later opensaf failed to start on same node.
 
 >> The issue is random
 
syslog--
Mar 10 16:52:40 suseR2-S1 **osafimmnd[2987]: ER Failed to load/sync. **Giving 
up after 51.061144 seconds, restarting..
Mar 10 16:52:40 suseR2-S1 opensafd[2873]: ER Could Not RESPAWN IMMND
Mar 10 16:52:40 suseR2-S1 opensafd[2873]: ER Failed   DESC:IMMND
Mar 10 16:52:40 suseR2-S1 opensafd[2873]: ER FAILED TO RESPAWN
Mar 10 16:52:40 suseR2-S1 osafimmnd[2987]: ER IMMND - Periodic server job failed
Mar 10 16:52:40 suseR2-S1 osafimmnd[2987]: ER Failed, exiting...
Mar 10 16:52:40 suseR2-S1 osafimmd[2934]: NO MDS event from svc_id 25 
(change:4, dest:564118002024465)
Mar 10 16:52:41 suseR2-S1 osafclmna[2904]: exiting for shutdown
Mar 10 16:52:41 suseR2-S1 osaffmd[2922]: exiting for shutdown
Mar 10 16:52:41 suseR2-S1 osafimmd[2934]: exiting for shutdown
Mar 10 16:52:42 suseR2-S1 osafrded[2913]: exiting for shutdown
Mar 10 16:52:42 suseR2-S1 osaftransportd[2899]: exiting for shutdown
...
Mar 10 16:52:42 suseR2-S1 kernel: [354116.766597] TIPC: Deactivated
Mar 10 16:52:42 suseR2-S1 opensafd: Starting OpenSAF failed


Notes:
1. Immnd traces attched 


---

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] #2349 Immnd faild to load/sync during headless opeartion resulted opensaf failed to start on controller

2017-03-06 Thread Ritu Raj
Iusue observed again and this time one of the payload (S4) immnd got 
healthCheckcallbackTimeout.


Mar  9 18:02:26 suseR2-S4 osafamfnd[12153]: NO 
'safSu=PL-4,safSg=NoRed,safApp=OpenSAF' component restart probation timer 
started (timeout: 600 ns)
Mar  9 18:02:26 suseR2-S4 osafamfnd[12153]: NO Restarting a component of 
'safSu=PL-4,safSg=NoRed,safApp=OpenSAF' (comp restart count: 1)
Mar  9 18:02:26 suseR2-S4 osafamfnd[12153]: NO 
'safComp=IMMND,safSu=PL-4,safSg=NoRed,safApp=OpenSAF' faulted due to 
'healthCheckcallbackTimeout' : Recovery is 'componentRestart'
Mar  9 18:02:32 suseR2-S4 osafimmnd[12897]: mkfifo already exists: 
/var/lib/opensaf/osafimmnd.fifo File exists

>>PL-4 immnd traces attached.


Attachments:

- 
[osafimmnd_PL.tgz](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/477607e2/bb66/attachment/osafimmnd_PL.tgz)
 (1.0 MB; application/x-compressed-tar)


---

** [tickets:#2349] Immnd faild to load/sync during headless opeartion resulted 
opensaf failed to start on controller**

**Status:** unassigned
**Milestone:** 5.2.RC1
**Created:** Mon Mar 06, 2017 10:06 AM UTC by Ritu Raj
**Last Updated:** Mon Mar 06, 2017 10:06 AM UTC
**Owner:** nobody
**Attachments:**

- 
[osafimmnd.tgz](https://sourceforge.net/p/opensaf/tickets/2349/attachment/osafimmnd.tgz)
 (1.0 MB; application/x-compressed-tar)


Environment details
OS : Suse 64bit
Changeset : 8634 ( 5.2.FC)
6 nodes setup(3 controller and 3 payload)

#Summary
Immnd faild to load/sync during headless opeartion resulted opensaf failed to 
start on controller

Steps followed & Observed behaviour
1. Invkoed headless 
2. after couple of headless opeartion immnd faild to load on one of the 
controller (SC-1) and later opensaf failed to start on same node.
 
 >> The issue is random
 
syslog--
Mar 10 16:52:40 suseR2-S1 **osafimmnd[2987]: ER Failed to load/sync. **Giving 
up after 51.061144 seconds, restarting..
Mar 10 16:52:40 suseR2-S1 opensafd[2873]: ER Could Not RESPAWN IMMND
Mar 10 16:52:40 suseR2-S1 opensafd[2873]: ER Failed   DESC:IMMND
Mar 10 16:52:40 suseR2-S1 opensafd[2873]: ER FAILED TO RESPAWN
Mar 10 16:52:40 suseR2-S1 osafimmnd[2987]: ER IMMND - Periodic server job failed
Mar 10 16:52:40 suseR2-S1 osafimmnd[2987]: ER Failed, exiting...
Mar 10 16:52:40 suseR2-S1 osafimmd[2934]: NO MDS event from svc_id 25 
(change:4, dest:564118002024465)
Mar 10 16:52:41 suseR2-S1 osafclmna[2904]: exiting for shutdown
Mar 10 16:52:41 suseR2-S1 osaffmd[2922]: exiting for shutdown
Mar 10 16:52:41 suseR2-S1 osafimmd[2934]: exiting for shutdown
Mar 10 16:52:42 suseR2-S1 osafrded[2913]: exiting for shutdown
Mar 10 16:52:42 suseR2-S1 osaftransportd[2899]: exiting for shutdown
...
Mar 10 16:52:42 suseR2-S1 kernel: [354116.766597] TIPC: Deactivated
Mar 10 16:52:42 suseR2-S1 opensafd: Starting OpenSAF failed


Notes:
1. Immnd traces attched 


---

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] #2339 CLM : Cluster reset doesn't succed as "reboot now" command fails on SLES

2017-03-06 Thread Hans Nordebäck
yes, shutdown is specified in LSB and can be used, is the problem the "now" 
argument? 
Perhaps every other calls to reboot in opensaf_reboot should be changed to 
shutdown?


---

** [tickets:#2339] CLM : Cluster reset doesn't succed as "reboot now" command 
fails on SLES**

**Status:** unassigned
**Milestone:** 5.2.RC1
**Created:** Fri Mar 03, 2017 06:05 AM UTC by Srikanth R
**Last Updated:** Fri Mar 03, 2017 06:06 AM UTC
**Owner:** nobody


Changeset : 8634 5.2.FC
SLES TIPC setup with one controller.


 Once the controller is brought up with opensaf 5.2.FC, the following cluster 
reset command is issued.
 
 immadm -o 4  safCluster=myClmCluster
 
 The command failed with the following log.
 
Mar 11 16:09:52 SUSE-S1-C1 osafclmd[6772]: Command: 
/usr/lib64/opensaf/opensaf_reboot 0 not_used 1 failed, rc = 256


On SLES, "reboot now" command fails. Instead "shutdown -r now"  should be 
invoked for graceful shutdown. 


---

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] #2336 logsv saLogInitialize() returns SA_AIS_ERR_VERSION for invalid minor version

2017-03-06 Thread Canh Truong
The version handling has already implemented in ticket #2146. Your comments 
will be updated in PR document. The ticket PR document was raised in ticket 
#2200. So I will update the ticket status to duplicate


---

** [tickets:#2336] logsv saLogInitialize() returns SA_AIS_ERR_VERSION for 
invalid minor version**

**Status:** unassigned
**Milestone:** 5.2.RC1
**Created:** Fri Mar 03, 2017 04:35 AM UTC by Ritu Raj
**Last Updated:** Fri Mar 03, 2017 10:04 AM UTC
**Owner:** nobody


#Environment details
OS : Suse 64bit
Changeset : 8634( 5.2.FC)

#Summary
logsv saLogInitialize() returns SA_AIS_ERR_VERSION if values of minor_version 
is other than [0,1,2,3]

#Steps
1. saLogInitialize() with version [A.2.100]
got return value SA_AIS_ERR_VERSION
-
In case if user provide unsupported minor version it should set highest value 
of the minor version that this implementation can support for the required 
value of releaseCode and the returned value of majorVersion

As per spec "SAI-AIS-LOG-A.02.01" section "3.5.1":
"version - [in/out] As an input parameter, version is a pointer to a structure 
containing
the required Log Service version. In this case, minorVersion is ignored and 
should be
set to 0x00"

If the preceding condition cannot be met, SA_AIS_ERR_VERSION is returned, and
the structure pointed to by the version parameter is set to:
if (implementation supports the required releaseCode)
releaseCode = required releaseCode
else {
if (implementation supports releaseCode higher than the required
releaseCode)
releaseCode = the lowest value of the supported release codes that is
higher than the required releaseCode
else
releaseCode = the highest value of the supported release codes that is
lower than the required releaseCode
}

In following lines I can see some changes:
>> src/log/agent/lga_api.c 

~~~
static bool is_log_version_valid(const SaVersionT *ver) {
bool rc = false;
if ((ver->releaseCode == LOG_RELEASE_CODE) &&
(ver->majorVersion <= LOG_MAJOR_VERSION) &&
(ver->majorVersion > 0) &&
(ver->minorVersion <= LOG_MINOR_VERSION)) {
rc = true;
}
return rc;
}


TRACE("version FAILED, required: %c.%u.%u, supported: %c.%u.%u\n",
  version->releaseCode, version->majorVersion, 
version->minorVersion,
  LOG_RELEASE_CODE, LOG_MAJOR_VERSION, LOG_MINOR_VERSION);
version->releaseCode = LOG_RELEASE_CODE;
version->majorVersion = LOG_MAJOR_VERSION;
version->minorVersion = LOG_MINOR_VERSION;
ais_rc = SA_AIS_ERR_VERSION;
goto done
~~~

#Below is the snippet of agent traces::
Mar  2 23:14:00.124164 lga [27362:src/log/agent/lga_api.c:0175] >> 
saLogInitialize
Mar  2 23:14:00.124193 lga [27362:src/log/agent/lga_api.c:0199] TR version 
FAILED, required: A.2.100, supported: A.2.3
Mar  2 23:14:00.124201 lga [27362:src/log/agent/lga_api.c:0322] << 
saLogInitialize: client_id = 0
Mar  2 23:14:00.144561 lga [27406:src/imm/agent/imma_om_api.cc:0165] >> 
saImmOmInitialize
Mar  2 23:14:00.144588 lga [27406:src/imm/agent/imma_om_api.cc:0191] TR OM 
client version A.2.17



---

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] #2336 logsv saLogInitialize() returns SA_AIS_ERR_VERSION for invalid minor version

2017-03-06 Thread Canh Truong
- **status**: unassigned --> duplicate



---

** [tickets:#2336] logsv saLogInitialize() returns SA_AIS_ERR_VERSION for 
invalid minor version**

**Status:** duplicate
**Milestone:** 5.2.RC1
**Created:** Fri Mar 03, 2017 04:35 AM UTC by Ritu Raj
**Last Updated:** Mon Mar 06, 2017 11:47 AM UTC
**Owner:** nobody


#Environment details
OS : Suse 64bit
Changeset : 8634( 5.2.FC)

#Summary
logsv saLogInitialize() returns SA_AIS_ERR_VERSION if values of minor_version 
is other than [0,1,2,3]

#Steps
1. saLogInitialize() with version [A.2.100]
got return value SA_AIS_ERR_VERSION
-
In case if user provide unsupported minor version it should set highest value 
of the minor version that this implementation can support for the required 
value of releaseCode and the returned value of majorVersion

As per spec "SAI-AIS-LOG-A.02.01" section "3.5.1":
"version - [in/out] As an input parameter, version is a pointer to a structure 
containing
the required Log Service version. In this case, minorVersion is ignored and 
should be
set to 0x00"

If the preceding condition cannot be met, SA_AIS_ERR_VERSION is returned, and
the structure pointed to by the version parameter is set to:
if (implementation supports the required releaseCode)
releaseCode = required releaseCode
else {
if (implementation supports releaseCode higher than the required
releaseCode)
releaseCode = the lowest value of the supported release codes that is
higher than the required releaseCode
else
releaseCode = the highest value of the supported release codes that is
lower than the required releaseCode
}

In following lines I can see some changes:
>> src/log/agent/lga_api.c 

~~~
static bool is_log_version_valid(const SaVersionT *ver) {
bool rc = false;
if ((ver->releaseCode == LOG_RELEASE_CODE) &&
(ver->majorVersion <= LOG_MAJOR_VERSION) &&
(ver->majorVersion > 0) &&
(ver->minorVersion <= LOG_MINOR_VERSION)) {
rc = true;
}
return rc;
}


TRACE("version FAILED, required: %c.%u.%u, supported: %c.%u.%u\n",
  version->releaseCode, version->majorVersion, 
version->minorVersion,
  LOG_RELEASE_CODE, LOG_MAJOR_VERSION, LOG_MINOR_VERSION);
version->releaseCode = LOG_RELEASE_CODE;
version->majorVersion = LOG_MAJOR_VERSION;
version->minorVersion = LOG_MINOR_VERSION;
ais_rc = SA_AIS_ERR_VERSION;
goto done
~~~

#Below is the snippet of agent traces::
Mar  2 23:14:00.124164 lga [27362:src/log/agent/lga_api.c:0175] >> 
saLogInitialize
Mar  2 23:14:00.124193 lga [27362:src/log/agent/lga_api.c:0199] TR version 
FAILED, required: A.2.100, supported: A.2.3
Mar  2 23:14:00.124201 lga [27362:src/log/agent/lga_api.c:0322] << 
saLogInitialize: client_id = 0
Mar  2 23:14:00.144561 lga [27406:src/imm/agent/imma_om_api.cc:0165] >> 
saImmOmInitialize
Mar  2 23:14:00.144588 lga [27406:src/imm/agent/imma_om_api.cc:0191] TR OM 
client version A.2.17



---

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] #2200 log: no document saLogStreamLogFileFormat value depending on logMaxLogrecsize

2017-03-06 Thread elunlen
Comment from Ritu Rai [#2336]
Please, Can you update the PR doc specifically for minor version.
Points can be added in PR doc-
* If Initialize with other than supported minor version [current supported 
minor version{0,1,2,3}] api should return "SA_AIS_ERR_VERSION"
 


---

** [tickets:#2200] log: no document saLogStreamLogFileFormat value depending on 
logMaxLogrecsize**

**Status:** accepted
**Milestone:** 5.2.RC1
**Created:** Wed Nov 23, 2016 07:23 AM UTC by Vu Minh Nguyen
**Last Updated:** Thu Feb 16, 2017 09:33 AM UTC
**Owner:** elunlen


The attribute `saLogStreamFixedLogRecordSize` value of log streams can be set 
to zero (flexilble log record) or an specific number, but must not be larger 
than `logMaxLogrecsize` attribute value which belongs to `OpenSafLogConfig` 
class.

`saLogStreamFixedLogRecordSize` value is limited by `logMaxLogrecsize`. This 
info should be described in PR documentation.

Also update the PR due to tickets:
 log: implement SaLogFilterSetCallbackT [#2146]
 log: add alternative destinations of log records [#2258]


---

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] #2329 IMM: Output parameter *version is not updated with A, 2, 18 after calling saImmOmInitiailize()

2017-03-06 Thread Neelakanta Reddy
- **status**: accepted --> review



---

** [tickets:#2329] IMM: Output parameter *version is not updated with A,2,18 
after calling saImmOmInitiailize()**

**Status:** review
**Milestone:** 5.2.RC1
**Created:** Thu Mar 02, 2017 08:54 AM UTC by Chani Srivastava
**Last Updated:** Mon Mar 06, 2017 11:24 AM UTC
**Owner:** Neelakanta Reddy


Changeset: 8634 5.2.FC
SLES four node cluster.

Issue Observed: Version param is returning A,2,17 on calling saImmOmInitialize()

Steps to reproduce:
1. Initialize ver with A,2,18
2. Call saImmOmInitialize(None, ver)
3. Print ver

Output:
{'majorVersion': 2, 'minorVersion': 17, 'releaseCode': 65}

Expected: Output parameter should be filled with version actually supported by 
IMM service.




---

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] #2329 IMM: Output parameter *version is not updated with A, 2, 18 after calling saImmOmInitiailize()

2017-03-06 Thread Neelakanta Reddy
- **status**: unassigned --> accepted
- **assigned_to**: Neelakanta Reddy
- **Part**: - --> lib
- **Version**:  --> 5.2



---

** [tickets:#2329] IMM: Output parameter *version is not updated with A,2,18 
after calling saImmOmInitiailize()**

**Status:** accepted
**Milestone:** 5.2.RC1
**Created:** Thu Mar 02, 2017 08:54 AM UTC by Chani Srivastava
**Last Updated:** Thu Mar 02, 2017 08:54 AM UTC
**Owner:** Neelakanta Reddy


Changeset: 8634 5.2.FC
SLES four node cluster.

Issue Observed: Version param is returning A,2,17 on calling saImmOmInitialize()

Steps to reproduce:
1. Initialize ver with A,2,18
2. Call saImmOmInitialize(None, ver)
3. Print ver

Output:
{'majorVersion': 2, 'minorVersion': 17, 'releaseCode': 65}

Expected: Output parameter should be filled with version actually supported by 
IMM service.




---

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] #2348 uml: Fix busybox build problem and upgrade Linux version

2017-03-06 Thread Anders Widell
- **status**: accepted --> review



---

** [tickets:#2348] uml: Fix busybox build problem and upgrade Linux version**

**Status:** review
**Milestone:** 5.0.2
**Created:** Mon Mar 06, 2017 08:52 AM UTC by Anders Widell
**Last Updated:** Mon Mar 06, 2017 08:52 AM UTC
**Owner:** Anders Widell


UML fails to build on Fedora 24:

~~~
Trying libraries: crypt m
 Library crypt is not needed, excluding it
 Library m is not needed, excluding it
Final link with: 
Warning! Space in _end[] is too small (56 bytes)!
Rerun make to build a binary which doesn't use it!
Makefile:717: recipe for target 'busybox_unstripped' failed
~~~

This happens due to a tuning configuration option that ought to be disabled. 
Fix this and also upgrade the Linux version to the latest.


---

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] #2348 uml: Fix busybox build problem and upgrade Linux version

2017-03-06 Thread Anders Widell



---

** [tickets:#2348] uml: Fix busybox build problem and upgrade Linux version**

**Status:** accepted
**Milestone:** 5.0.2
**Created:** Mon Mar 06, 2017 08:52 AM UTC by Anders Widell
**Last Updated:** Mon Mar 06, 2017 08:52 AM UTC
**Owner:** Anders Widell


UML fails to build on Fedora 24:

~~~
Trying libraries: crypt m
 Library crypt is not needed, excluding it
 Library m is not needed, excluding it
Final link with: 
Warning! Space in _end[] is too small (56 bytes)!
Rerun make to build a binary which doesn't use it!
Makefile:717: recipe for target 'busybox_unstripped' failed
~~~

This happens due to a tuning configuration option that ought to be disabled. 
Fix this and also upgrade the Linux version to the latest.


---

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] #2347 base: Service startup can be slow due to DNS problems

2017-03-06 Thread Anders Widell



---

** [tickets:#2347] base: Service startup can be slow due to DNS problems**

**Status:** accepted
**Milestone:** 5.2.RC1
**Created:** Mon Mar 06, 2017 08:46 AM UTC by Anders Widell
**Last Updated:** Mon Mar 06, 2017 08:46 AM UTC
**Owner:** Anders Widell


Ticket [#2267] introduced functionality for querying the domain name of the 
current node. This query can be slow if the name server is not responding or if 
it is misconfigured. A solution is to perform the query once and store the 
result in a file which is used on subsequent invocations. 


---

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] #2346 OpenSAF failed to start on controller randomaly

2017-03-06 Thread Ritu Raj
- **summary**: OpenSAF failed to start on controller --> OpenSAF failed to 
start on controller randomaly 



---

** [tickets:#2346] OpenSAF failed to start on controller randomaly **

**Status:** unassigned
**Milestone:** 5.2.RC1
**Created:** Mon Mar 06, 2017 08:43 AM UTC by Ritu Raj
**Last Updated:** Mon Mar 06, 2017 08:43 AM UTC
**Owner:** nobody


###Environment details
OS : Suse 64bit
Changeset : 8634 ( 5.2.FC)

###Summary
OpenSAF failed to start on controller

###Steps followed & Observed behaviour
1. After couple of start and stop operation it is observed that some time 
opensaf failed to start on controller.

 >  Issue is random and till now it is observed 4 times

Mar 10 12:26:11 suseR2-S1 kernel: [346024.678444] TIPC: Own node address 
<1.1.1>, network identity 8181
Mar 10 12:26:11 suseR2-S1 kernel: [346024.704494] TIPC: Enabled bearer 
, discovery domain <1.1.0>, priority 10
Mar 10 12:26:11 suseR2-S1 kernel: [346024.704868] TIPC: Established link 
<1.1.1:eth0-1.1.6:eth0> on network plane A
Mar 10 12:26:11 suseR2-S1 kernel: [346024.704897] TIPC: Established link 
<1.1.1:eth0-1.1.4:eth0> on network plane A
Mar 10 12:26:11 suseR2-S1 kernel: [346024.704944] TIPC: Established link 
<1.1.1:eth0-1.1.5:eth0> on network plane A
Mar 10 12:26:11 suseR2-S1 opensafd[2869]: **ER Failed to open 
/var/lib/opensaf/osaftransportd.fifo, error: No such device or address**
Mar 10 12:26:11 suseR2-S1 opensafd[2869]: ER Failed to start monitoring for 
service TRANSPORT, exiting
Mar 10 12:26:12 suseR2-S1 osaftransportd[2899]: mkfifo already exists: 
/var/lib/opensaf/osaftransportd.fifo File exists
Mar 10 12:26:12 suseR2-S1 osaftransportd[2899]: Started
Mar 10 12:26:12 suseR2-S1 osafclmna[2909]: mkfifo already exists: 
/var/lib/opensaf/osafclmna.fifo File exists
Mar 10 12:26:12 suseR2-S1 osafclmna[2909]: Started
Mar 10 12:26:12 suseR2-S1 osafclmna[2909]: NO Starting to promote this node to 
a system controller
Mar 10 12:26:13 suseR2-S1 osafclmna[2909]: exiting for shutdown
Mar 10 12:26:14 suseR2-S1 osaftransportd[2899]: exiting for shutdown



---

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] #2328 log: logtest 5 17 fail

2017-03-06 Thread Vu Minh Nguyen
- **status**: review --> fixed
- **assigned_to**: Canh Truong -->  nobody 
- **Part**: - --> tests
- **Comment**:

changeset:   8646:6ae9d544b25e
tag: tip
user:Canh Van Truong 
date:Fri Mar 03 08:43:22 2017 +0700
summary: log: fix the problem cause the logtest 5 17 failed [#2328]




---

** [tickets:#2328] log: logtest 5 17 fail**

**Status:** fixed
**Milestone:** 5.2.RC1
**Created:** Wed Mar 01, 2017 07:56 AM UTC by Canh Truong
**Last Updated:** Wed Mar 01, 2017 10:33 AM UTC
**Owner:** nobody


2017-03-01 00:02:45,535 DEBUG - *** Test 17 (Suite 5): Add 
logRecordDestinationConfiguration. OK
2017-03-01 00:02:45,860 ERROR - *** FAILED in Test 17 (Suite 5): Add 
logRecordDestinationConfiguration. OK
Command: 'logtest 5 17'
rc: 255 - output:
Suite 5: LOG OI tests, Service configuration object
Check OpenSafLogConfig Fail
?[1;31m 17 FAILED (expected EXIT_SUCCESS, got EXIT_FAILURE (1)) Add 
logRecordDestinationConfiguration. OK?[0m;

step to reproduce:
logtest 18 1
logtest 5 17

Some test cases in test suite logtest 18 do not restore the system to beginning 
of test case after testing. This causes the checking in logtest 5 17 failed.



---

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] #2346 OpenSAF failed to start on controller

2017-03-06 Thread Ritu Raj



---

** [tickets:#2346] OpenSAF failed to start on controller**

**Status:** unassigned
**Milestone:** 5.2.RC1
**Created:** Mon Mar 06, 2017 08:43 AM UTC by Ritu Raj
**Last Updated:** Mon Mar 06, 2017 08:43 AM UTC
**Owner:** nobody


###Environment details
OS : Suse 64bit
Changeset : 8634 ( 5.2.FC)

###Summary
OpenSAF failed to start on controller

###Steps followed & Observed behaviour
1. After couple of start and stop operation it is observed that some time 
opensaf failed to start on controller.

 >  Issue is random and till now it is observed 4 times

Mar 10 12:26:11 suseR2-S1 kernel: [346024.678444] TIPC: Own node address 
<1.1.1>, network identity 8181
Mar 10 12:26:11 suseR2-S1 kernel: [346024.704494] TIPC: Enabled bearer 
, discovery domain <1.1.0>, priority 10
Mar 10 12:26:11 suseR2-S1 kernel: [346024.704868] TIPC: Established link 
<1.1.1:eth0-1.1.6:eth0> on network plane A
Mar 10 12:26:11 suseR2-S1 kernel: [346024.704897] TIPC: Established link 
<1.1.1:eth0-1.1.4:eth0> on network plane A
Mar 10 12:26:11 suseR2-S1 kernel: [346024.704944] TIPC: Established link 
<1.1.1:eth0-1.1.5:eth0> on network plane A
Mar 10 12:26:11 suseR2-S1 opensafd[2869]: **ER Failed to open 
/var/lib/opensaf/osaftransportd.fifo, error: No such device or address**
Mar 10 12:26:11 suseR2-S1 opensafd[2869]: ER Failed to start monitoring for 
service TRANSPORT, exiting
Mar 10 12:26:12 suseR2-S1 osaftransportd[2899]: mkfifo already exists: 
/var/lib/opensaf/osaftransportd.fifo File exists
Mar 10 12:26:12 suseR2-S1 osaftransportd[2899]: Started
Mar 10 12:26:12 suseR2-S1 osafclmna[2909]: mkfifo already exists: 
/var/lib/opensaf/osafclmna.fifo File exists
Mar 10 12:26:12 suseR2-S1 osafclmna[2909]: Started
Mar 10 12:26:12 suseR2-S1 osafclmna[2909]: NO Starting to promote this node to 
a system controller
Mar 10 12:26:13 suseR2-S1 osafclmna[2909]: exiting for shutdown
Mar 10 12:26:14 suseR2-S1 osaftransportd[2899]: exiting for shutdown



---

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] #2345 amf: standby controller reboots after switchover

2017-03-06 Thread Nagendra Kumar
- **summary**: amf: standby controller reboots during switchover --> amf: 
standby controller reboots after switchover



---

** [tickets:#2345] amf: standby controller reboots after switchover**

**Status:** review
**Milestone:** 5.2.RC1
**Created:** Mon Mar 06, 2017 07:27 AM UTC by Nagendra Kumar
**Last Updated:** Mon Mar 06, 2017 08:37 AM UTC
**Owner:** Nagendra Kumar


Steps to reproduce
--
1. Make the following changes at Standby Amfd (SC-2) :
diff --git a/src/amf/amfnd/evt.cc b/src/amf/amfnd/evt.cc
--- a/src/amf/amfnd/evt.cc
+++ b/src/amf/amfnd/evt.cc
@@ -71,6 +71,11 @@ AVND_EVT *avnd_evt_create(AVND_CB *cb,
/* fill the event specific fields */
switch (type) {
/* AvD event types */
+   case AVND_EVT_AVD_ROLE_CHANGE_MSG:
+   case AVND_EVT_AVD_VERIFY_MSG:
+   evt->priority = NCS_IPC_PRIORITY_VERY_HIGH; /* bump up the 
priority */
+   evt->info.avd = (AVSV_DND_MSG *)info;
+   break;
case AVND_EVT_AVD_NODE_UP_MSG:
case AVND_EVT_AVD_REG_SU_MSG:
case AVND_EVT_AVD_REG_COMP_MSG:
@@ -79,12 +84,10 @@ AVND_EVT *avnd_evt_create(AVND_CB *cb,
case AVND_EVT_AVD_PG_UPD_MSG:
case AVND_EVT_AVD_OPERATION_REQUEST_MSG:
case AVND_EVT_AVD_SU_PRES_MSG:
-   case AVND_EVT_AVD_VERIFY_MSG:
case AVND_EVT_AVD_ACK_MSG:
case AVND_EVT_AVD_SHUTDOWN_APP_SU_MSG:
case AVND_EVT_AVD_SET_LEDS_MSG:
case AVND_EVT_AVD_COMP_VALIDATION_RESP_MSG:
-   case AVND_EVT_AVD_ROLE_CHANGE_MSG:
case AVND_EVT_AVD_ADMIN_OP_REQ_MSG:
case AVND_EVT_AVD_REBOOT_MSG:
case AVND_EVT_AVD_COMPCSI_ASSIGN_MSG:
diff --git a/src/amf/amfnd/mds.cc b/src/amf/amfnd/mds.cc
--- a/src/amf/amfnd/mds.cc
+++ b/src/amf/amfnd/mds.cc
@@ -543,6 +543,9 @@ uint32_t avnd_mds_svc_evt(AVND_CB *cb, M
// DOWN is received for the old director ..
if (m_AVND_CB_IS_AVD_UP(cb)) {
m_AVND_CB_AVD_UP_RESET(cb);
+   LOG_NO("Before sleep");
+   sleep(2);
+   LOG_NO("After sleep");
}

evt = avnd_evt_create(cb, AVND_EVT_MDS_AVD_UP, 0, 
_info->i_dest, 0, 0, 0);

2. Start both controllers. Upload app configuration, hosting SC-1 on SC-2.
3. Issue amf-adm si-swap safSi=SC-2N,safApp=OpenSAF
4. Then issue amf-adm unlock-in safSu=SU1,safSg=AmfDemo_2N,safApp=AmfDemo1
Observed behaviour
--
Mar  6 12:53:58 PM_SC-2 osafamfnd[8501]: NO After sleep
Mar  6 12:54:01 PM_SC-2 osafamfnd[8501]: Rebooting OpenSAF NodeId = 0 EE Name = 
No EE Mapped, Reason: Message ID mismatch, rec 2, expected 1, OwnNodeId = 
131599, SupervisionTime = 60
Mar  6 12:54:01 PM_SC-2 opensaf_reboot: Rebooting local node; timeout=60

This happens because role change(avnd_evt_mds_avd_up_evh) comes before 
avnd_evt_mds_avd_up_evh.

osafamfnd [9054:src/amf/amfnd/mds.cc:0540] NO AVD NEW_ACTIVE, adest:1
osafamfnd [9054:src/amf/amfnd/mds.cc:0546] NO Before sleep
osafamfnd [9054:src/amf/amfnd/mds.cc:0548] NO After sleep
osafamfnd [9054:src/amf/amfnd/mds.cc:0345] T1 Active AVD Adest = 565214626185244
osafamfnd [9054:src/amf/amfnd/main.cc:0647] >> avnd_evt_process
osafamfnd [9054:src/amf/amfnd/main.cc:0664] TR Evt type:9
osafamfnd [9054:src/amf/amfnd/verify.cc:0058] >> avnd_evt_avd_verify_evh: Data 
Verify message received from newly ACTIVE AVD
osafamfnd [9054:src/amf/amfnd/verify.cc:0071] T1 AVD send ID count: 7
osafamfnd [9054:src/amf/amfnd/verify.cc:0072] T1 AVND receive ID count: 7
osafamfnd [9054:src/amf/amfnd/di.cc:1087] >> avnd_di_ack_nack_msg_send: Receive 
id = 7
osafamfnd [9054:src/amf/amfnd/di.cc:1103] T1 MsgId=84,ACK=1
osafamfnd [9054:src/amf/amfnd/di.cc:1033] >> avnd_di_msg_send: Msg type '10'
osafamfnd [9054:src/amf/amfnd/di.cc:1043] T1 avnd_di_msg_send, Active AVD 
Adest: 565214626185244
osafamfnd [9054:src/amf/amfnd/mds.cc:1496] >> avnd_mds_red_send: Msg type '1'
osafamfnd [9054:src/amf/amfnd/mds.cc:1534] << avnd_mds_red_send: rc '1'
osafamfnd [9054:src/amf/amfnd/di.cc:1065] << avnd_di_msg_send: 1
osafamfnd [9054:src/amf/amfnd/di.cc:1112] << avnd_di_ack_nack_msg_send: retval=1
osafamfnd [9054:src/amf/amfnd/verify.cc:0095] T1 AVD receive ID count: 83
osafamfnd [9054:src/amf/amfnd/verify.cc:0096] T1 AVND send ID count: 83
osafamfnd [9054:src/amf/amfnd/di.cc:1571] >> avnd_di_resend_pg_start_track
osafamfnd [9054:src/amf/amfnd/di.cc:1581] << avnd_di_resend_pg_start_track
osafamfnd [9054:src/amf/amfnd/verify.cc:0143] << avnd_evt_avd_verify_evh
osafamfnd [9054:src/amf/amfnd/main.cc:0670] TR Evt Type:9 success
osafamfnd [9054:src/amf/amfnd/main.cc:0675] << avnd_evt_process
osafamfnd [9054:src/amf/amfnd/main.cc:0647] >> avnd_evt_process
osafamfnd [9054:src/amf/amfnd/main.cc:0664] TR Evt type:14
osafamfnd [9054:src/amf/amfnd/di.cc:1503] >> avnd_evt_avd_role_change_evh
osafamfnd [9054:src/amf/amfnd/di.cc:1507] IN AVD is 

[tickets] [opensaf:tickets] #2345 amf: standby controller reboots during switchover

2017-03-06 Thread Nagendra Kumar
- **status**: accepted --> review



---

** [tickets:#2345] amf: standby controller reboots during switchover**

**Status:** review
**Milestone:** 5.2.RC1
**Created:** Mon Mar 06, 2017 07:27 AM UTC by Nagendra Kumar
**Last Updated:** Mon Mar 06, 2017 07:27 AM UTC
**Owner:** Nagendra Kumar


Steps to reproduce
--
1. Make the following changes at Standby Amfd (SC-2) :
diff --git a/src/amf/amfnd/evt.cc b/src/amf/amfnd/evt.cc
--- a/src/amf/amfnd/evt.cc
+++ b/src/amf/amfnd/evt.cc
@@ -71,6 +71,11 @@ AVND_EVT *avnd_evt_create(AVND_CB *cb,
/* fill the event specific fields */
switch (type) {
/* AvD event types */
+   case AVND_EVT_AVD_ROLE_CHANGE_MSG:
+   case AVND_EVT_AVD_VERIFY_MSG:
+   evt->priority = NCS_IPC_PRIORITY_VERY_HIGH; /* bump up the 
priority */
+   evt->info.avd = (AVSV_DND_MSG *)info;
+   break;
case AVND_EVT_AVD_NODE_UP_MSG:
case AVND_EVT_AVD_REG_SU_MSG:
case AVND_EVT_AVD_REG_COMP_MSG:
@@ -79,12 +84,10 @@ AVND_EVT *avnd_evt_create(AVND_CB *cb,
case AVND_EVT_AVD_PG_UPD_MSG:
case AVND_EVT_AVD_OPERATION_REQUEST_MSG:
case AVND_EVT_AVD_SU_PRES_MSG:
-   case AVND_EVT_AVD_VERIFY_MSG:
case AVND_EVT_AVD_ACK_MSG:
case AVND_EVT_AVD_SHUTDOWN_APP_SU_MSG:
case AVND_EVT_AVD_SET_LEDS_MSG:
case AVND_EVT_AVD_COMP_VALIDATION_RESP_MSG:
-   case AVND_EVT_AVD_ROLE_CHANGE_MSG:
case AVND_EVT_AVD_ADMIN_OP_REQ_MSG:
case AVND_EVT_AVD_REBOOT_MSG:
case AVND_EVT_AVD_COMPCSI_ASSIGN_MSG:
diff --git a/src/amf/amfnd/mds.cc b/src/amf/amfnd/mds.cc
--- a/src/amf/amfnd/mds.cc
+++ b/src/amf/amfnd/mds.cc
@@ -543,6 +543,9 @@ uint32_t avnd_mds_svc_evt(AVND_CB *cb, M
// DOWN is received for the old director ..
if (m_AVND_CB_IS_AVD_UP(cb)) {
m_AVND_CB_AVD_UP_RESET(cb);
+   LOG_NO("Before sleep");
+   sleep(2);
+   LOG_NO("After sleep");
}

evt = avnd_evt_create(cb, AVND_EVT_MDS_AVD_UP, 0, 
_info->i_dest, 0, 0, 0);

2. Start both controllers. Upload app configuration, hosting SC-1 on SC-2.
3. Issue amf-adm si-swap safSi=SC-2N,safApp=OpenSAF
4. Then issue amf-adm unlock-in safSu=SU1,safSg=AmfDemo_2N,safApp=AmfDemo1
Observed behaviour
--
Mar  6 12:53:58 PM_SC-2 osafamfnd[8501]: NO After sleep
Mar  6 12:54:01 PM_SC-2 osafamfnd[8501]: Rebooting OpenSAF NodeId = 0 EE Name = 
No EE Mapped, Reason: Message ID mismatch, rec 2, expected 1, OwnNodeId = 
131599, SupervisionTime = 60
Mar  6 12:54:01 PM_SC-2 opensaf_reboot: Rebooting local node; timeout=60

This happens because role change(avnd_evt_mds_avd_up_evh) comes before 
avnd_evt_mds_avd_up_evh.

osafamfnd [9054:src/amf/amfnd/mds.cc:0540] NO AVD NEW_ACTIVE, adest:1
osafamfnd [9054:src/amf/amfnd/mds.cc:0546] NO Before sleep
osafamfnd [9054:src/amf/amfnd/mds.cc:0548] NO After sleep
osafamfnd [9054:src/amf/amfnd/mds.cc:0345] T1 Active AVD Adest = 565214626185244
osafamfnd [9054:src/amf/amfnd/main.cc:0647] >> avnd_evt_process
osafamfnd [9054:src/amf/amfnd/main.cc:0664] TR Evt type:9
osafamfnd [9054:src/amf/amfnd/verify.cc:0058] >> avnd_evt_avd_verify_evh: Data 
Verify message received from newly ACTIVE AVD
osafamfnd [9054:src/amf/amfnd/verify.cc:0071] T1 AVD send ID count: 7
osafamfnd [9054:src/amf/amfnd/verify.cc:0072] T1 AVND receive ID count: 7
osafamfnd [9054:src/amf/amfnd/di.cc:1087] >> avnd_di_ack_nack_msg_send: Receive 
id = 7
osafamfnd [9054:src/amf/amfnd/di.cc:1103] T1 MsgId=84,ACK=1
osafamfnd [9054:src/amf/amfnd/di.cc:1033] >> avnd_di_msg_send: Msg type '10'
osafamfnd [9054:src/amf/amfnd/di.cc:1043] T1 avnd_di_msg_send, Active AVD 
Adest: 565214626185244
osafamfnd [9054:src/amf/amfnd/mds.cc:1496] >> avnd_mds_red_send: Msg type '1'
osafamfnd [9054:src/amf/amfnd/mds.cc:1534] << avnd_mds_red_send: rc '1'
osafamfnd [9054:src/amf/amfnd/di.cc:1065] << avnd_di_msg_send: 1
osafamfnd [9054:src/amf/amfnd/di.cc:1112] << avnd_di_ack_nack_msg_send: retval=1
osafamfnd [9054:src/amf/amfnd/verify.cc:0095] T1 AVD receive ID count: 83
osafamfnd [9054:src/amf/amfnd/verify.cc:0096] T1 AVND send ID count: 83
osafamfnd [9054:src/amf/amfnd/di.cc:1571] >> avnd_di_resend_pg_start_track
osafamfnd [9054:src/amf/amfnd/di.cc:1581] << avnd_di_resend_pg_start_track
osafamfnd [9054:src/amf/amfnd/verify.cc:0143] << avnd_evt_avd_verify_evh
osafamfnd [9054:src/amf/amfnd/main.cc:0670] TR Evt Type:9 success
osafamfnd [9054:src/amf/amfnd/main.cc:0675] << avnd_evt_process
osafamfnd [9054:src/amf/amfnd/main.cc:0647] >> avnd_evt_process
osafamfnd [9054:src/amf/amfnd/main.cc:0664] TR Evt type:14
osafamfnd [9054:src/amf/amfnd/di.cc:1503] >> avnd_evt_avd_role_change_evh
osafamfnd [9054:src/amf/amfnd/di.cc:1507] IN AVD is not up yet
osafamfnd [9054:src/amf/amfnd/di.cc:] << avnd_evt_avd_role_change_evh

[tickets] [opensaf:tickets] #1860 mdstest: Mdstest leaks a huge amount of memory

2017-03-06 Thread Vo Minh Hoang
- **status**: assigned --> review
- **assigned_to**: A V Mahesh (AVM) --> Vo Minh Hoang



---

** [tickets:#1860] mdstest: Mdstest leaks a huge amount of memory**

**Status:** review
**Milestone:** 5.0.2
**Created:** Wed Jun 01, 2016 02:54 PM UTC by Anders Widell
**Last Updated:** Tue Sep 20, 2016 06:04 PM UTC
**Owner:** Vo Minh Hoang


mdstest in OpenSAF 5.0.0 leaks a huge amount of memory. Here is the result when 
running mdstest with valgrind:

==512== LEAK SUMMARY:
==512==definitely lost: 535,634,854 bytes in 2,099 blocks
==512==indirectly lost: 209,800 bytes in 45 blocks
==512==  possibly lost: 4,221,632 bytes in 66 blocks
==512==still reachable: 262,984 bytes in 2 blocks
==512== suppressed: 0 bytes in 0 blocks



---

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