- **status**: unassigned --> invalid
- **Comment**:
There are enough stale/junk tickets that needs review. Please avoid raising a
ticket if you are not sure of the behaviour. Check with the maintainer first
before raising a ticket.
Invalid ticket!
---
** [tickets:#915] differences seen among OPENSAF_MANAGE_TIPC and application
using tipc**
**Status:** invalid
**Milestone:** future
**Created:** Mon May 19, 2014 12:48 PM UTC by surender khetavath
**Last Updated:** Mon May 19, 2014 12:48 PM UTC
**Owner:** nobody
changeset : 5270
case 1 : OPENSAF_MANAGE_TIPC=yes on both controller nodes
a) run any non-amf application (imm application in specific )on sc-2
b) stop and start opensaf on sc-1. sc-2 will be active and sc-1 standby.
c) stop opensaf on sc-2. Now sc-1 doesn't take active role, since tipc
unloading failed on sc-2 because application was using tipc
SC-1 later reboots with below syslog
May 19 17:30:44 SC-1 osafimmnd[5360]: NO No IMMD service => cluster restart
May 19 17:30:44 SC-1 osafamfnd[5422]: NO
'safComp=IMMND,safSu=SC-1,safSg=NoRed,safApp=OpenSAF' faulted due to 'avaDown'
: Recovery is 'componentRestart'
May 19 17:30:44 SC-1 osafntfimcnd[5386]: ER saImmOiDispatch() Fail
SA_AIS_ERR_BAD_HANDLE (9)
May 19 17:30:44 SC-1 osafamfd[5412]: NO Re-initializing with IMM
May 19 17:30:44 SC-1 osafimmnd[5658]: Started
May 19 17:30:44 SC-1 osafimmnd[5658]: NO Persistent Back-End capability
configured, Pbe file:imm.db
May 19 17:30:46 SC-1 osafamfnd[5422]: ER AMF director unexpectedly crashed
May 19 17:30:46 SC-1 osafamfnd[5422]: Rebooting OpenSAF NodeId = 131343 EE Name
= , Reason: local AVD down(Adest) or both AVD down(Vdest) received, OwnNodeId =
131343, SupervisionTime = 60
May 19 17:30:46 SC-1 opensaf_reboot: Rebooting local node; timeout=60
May 19 17:30:49 SC-1 kernel: [ 497.913444] md: stopping all md devices.
May 19 17:30:49 SC-1 kernel: [ 498.916932] sd 0:0:0:0: [sda] Synchronizing
SCSI cache
case 2: OPENSAF_MANAGE_TIPC=yes on sc-1 and OPENSAF_MANAGE_TIPC=no on sc-2
a) run the same non-amf app/imm app on sc-2.
b) stop opensaf on sc-2, tipc unloading is not taken care by opensaf as
OPENSAF_MANAGE_TIPC=no.
c) start opensaf on sc-2. opensaf start fails with syslog below
May 19 17:59:50 SC-2 osafclmna[18568]: Started
May 19 17:59:50 SC-2 osafclmna[18568]: ER safNode=SC-2,safCluster=myClmCluster
is already up. Specify a unique name in/etc/opensaf/node_name
May 19 17:59:50 SC-2 opensafd[18425]: ER Could Not RESPAWN CLMNA
May 19 17:59:50 SC-2 opensafd[18425]: ER Failed DESC:CLMNA
May 19 17:59:50 SC-2 opensafd[18425]: ER FAILED TO RESPAWN
May 19 17:59:50 SC-2 osafntfimcnd[18514]: ER saImmOiDispatch() Fail
SA_AIS_ERR_BAD_HANDLE (9)
May 19 17:59:51 SC-2 osafntfd[18506]: NO exiting on signal 15
May 19 17:59:53 SC-2 osafntfd[18506]: NO stop_ntfimcn osafntfimcnd process
terminated
failed
May 19 17:59:53 SC-2 opensafd: Starting OpenSAF failed
The variable OPENSAF_MANAGE_TIPC when set to 'no' should enable the
applications to use tipc and should also facilitate controller switchover.
if not, how to ensure that application continue to use tipc and still opensaf
facilitate controller switchover?
---
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.------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
