- **Version**: 5.0 FC --> 5.0.FC
- **Priority**: minor --> major
- **Comment**:
This issue is observed again on a different setup after 4 failovers.
Setup :
changeset : 7436 ( 5.0.FC)
Setup : 5 node cluster with 150K PBE objects
On the standby controller
Apr 18 12:57:50 SYSTEST-CNTLR-2 osafamfnd[2535]: Started
Apr 18 12:57:50 SYSTEST-CNTLR-2 osafamfnd[2535]: ER Failed to Initialize with
CLM: 8
Apr 18 12:57:50 SYSTEST-CNTLR-2 osafamfnd[2535]: ER avnd_create failed
Apr 18 12:57:50 SYSTEST-CNTLR-2 osafamfnd[2535]: NO exiting
On the active controller
Apr 18 12:59:24 SYSTEST-CNTLR-1 osafimmnd[2298]: NO SERVER STATE:
IMM_SERVER_SYNC_SERVER --> IMM_SERVER_READY
Apr 18 12:59:25 SYSTEST-CNTLR-1 osafclmd[2328]: WA FAILED:
ncs_patricia_tree_add, client_id 70
Apr 18 12:59:25 SYSTEST-CNTLR-1 osafamfd[2338]: NO Node 'SC-2' left the cluster
Please note that, this type of issue is not seen earlier and failovers used to
run smoothly on this setup with 4.6 & 4.7 opensaf versions.
---
** [tickets:#1757] Standby controller failed to join the cluster probably
because of setup issues**
**Status:** unassigned
**Milestone:** 4.6.2
**Created:** Wed Apr 13, 2016 11:12 AM UTC by Ritu Raj
**Last Updated:** Fri Apr 15, 2016 06:32 AM UTC
**Owner:** nobody
*Setup:
Changeset- 7436
Version - opensaf 5.0FC
OS: SUSE 11SP2 x86_64
*Issue observed :
Standby controller failed to join the cluster with error message "ER Failed to
Initialize with CLM"
*Steps To Reproduce:
> OpenSAF is already up and running on controller1(SC-1)
> when OpenSAF started on controller2(SC-2), it failed with following mesage:
SCALE_SLOT-2:~ # /etc/init.d/opensafd start
Apr 26 20:11:28 SCALE_SLOT-2 opensafd: Starting OpenSAF Services(5.0.FC - )
(Using TIPC)
Starting OpenSAF Services (Using TIPC):Apr 26 20:11:28 SCALE_SLOT-2 kernel:
[1930938.251473] TIPC: Activated (version 2.0.0)
...
Apr 26 20:11:29 SCALE_SLOT-2 osafamfnd[29911]: Started
**Apr 26 20:11:29 SCALE_SLOT-2 osafamfnd[29911]: ER Failed to Initialize with
CLM: 8
Apr 26 20:11:29 SCALE_SLOT-2 osafamfnd[29911]: ER avnd_create failed**
Apr 26 20:11:29 SCALE_SLOT-2 osafamfnd[29911]: NO exiting
> The crossponding syslog of active controller(SC-1) at that time
Apr 26 20:08:51 SCALE_SLOT-1 osafclmd[31692]: WA FAILED:**
ncs_patricia_tree_add, client_id** 53
Apr 26 20:08:51 SCALE_SLOT-1 osafamfd[31702]: NO Node 'SC-2' left the cluster
>> It is also observed that, on active controller(SC-1) there in no log record
>> of osafclmd during which controller2(SC-2) failed, while other service have
>> log record at that time stamp
Below is the output of osafclmd (SC-1), during time stamp "Apr 26
20:08:51.237701" to "Apr 26 20:12:06.272871" osafclmd not logged anything.
Apr 26 20:08:51.237695 osafclmd [31692:clms_evt.c:1601] << process_api_evt
**Apr 26 20:08:51.237701 osafclmd [31692:clms_evt.c:1667] << clms_process_mbx
Apr 26 20:12:06.272871 osafclmd [31692:ava_mds.c:0179] >> ava_mds_cbk**
Apr 26 20:12:06.272923 osafclmd [31692:ava_mds.c:0530] >> ava_mds_flat_dec
Note:
1. This is random issue
2. The time gap between controller1(SC-1) and controller2(SC-2) is 3 min.
---
Sent from sourceforge.net because [email protected] 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.
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
