- **status**: unassigned --> duplicate
- **Comment**:
This is a duplicate of ticket #31.
The sync of SC2 can not start because there is a critical ccb that
needs to be resolved first.
Enhancement ticket #31 will fix so that critical ccbs can be sync'ed
while still being active.
The critical CCB can only be resolved by the PBE and the PBE is
apparently hung on something. The most likely problem is a file
system problem, i.e. the PBE is blocked waiting to read or write
to the file system. That problem will be resolved when the file
system becomes available.
In theory the PBE could be hung or looping due to some bug. That is
covered by enhancement ticket #59.
If the problem seems NOT to be the file system, then ticket #59
would be more urgent to fix. If the problem is the file system then
a fix of #59 will not help. A restarted PBE will simply get stuck
again on the hung file system.
Related tickets:
https://sourceforge.net/p/opensaf/tickets/31/
https://sourceforge.net/p/opensaf/tickets/59/
---
** [tickets:#876] sc2 doesnot join after reboot due to PBE hung**
**Status:** duplicate
**Milestone:** future
**Created:** Mon Apr 28, 2014 10:12 AM UTC by surender khetavath
**Last Updated:** Mon Apr 28, 2014 10:12 AM UTC
**Owner:** nobody
changeset : 5143
model : TWON
case:
1) Brinup up 2n model
2) Make sure components which receive active cbk call exit().
recovery=componentFailover
3) lock/unlock active Su.
Here SC-2 was active and SC-1 standby.
SC-2 went for reboot due to fault.
SC-2 never joined again.
syslog on sc-1
Apr 28 15:41:02 SC-1 osafimmd[2597]: NO ACT: New Epoch for IMMND process at
node 2030f old epoch: 47 new epoch:48
Apr 28 15:41:02 SC-1 osafimmd[2597]: NO ACT: New Epoch for IMMND process at
node 2050f old epoch: 47 new epoch:48
Apr 28 15:41:02 SC-1 osafimmd[2597]: NO ACT: New Epoch for IMMND process at
node 2040f old epoch: 47 new epoch:48
Apr 28 15:41:02 SC-1 osafimmd[2597]: WA IMMND on controller (not currently
coord) requests sync
Apr 28 15:41:02 SC-1 osafimmd[2597]: NO Node 2020f request sync sync-pid:3419
epoch:0
Apr 28 15:41:02 SC-1 osafimmnd[2607]: WA Timeout (6) on transaction in critical
state! ccb:181
Apr 28 15:41:02 SC-1 osafimmnd[2607]: WA PBE implementer 6 seems hung!
Apr 28 15:41:04 SC-1 osafimmnd[2607]: WA Timeout (6) on transaction in critical
state! ccb:181
Apr 28 15:41:04 SC-1 osafimmnd[2607]: WA PBE implementer 6 seems hung!
Apr 28 15:41:05 SC-1 osafimmnd[2607]: WA Timeout (6) on transaction in critical
state! ccb:181
Apr 28 15:41:05 SC-1 osafimmnd[2607]: WA PBE implementer 6 seems hung!
Apr 28 15:41:06 SC-1 osafimmnd[2607]: WA Timeout (6) on transaction in critical
state! ccb:181
Apr 28 15:41:06 SC-1 osafimmnd[2607]: WA PBE implementer 6 seems hung!
Apr 28 15:41:06 SC-1 osafimmnd[2607]: NO Announce sync, epoch:49
Apr 28 15:41:06 SC-1 osafimmnd[2607]: NO SERVER STATE: IMM_SERVER_READY -->
IMM_SERVER_SYNC_SERVER
Apr 28 15:41:06 SC-1 osafimmd[2597]: NO Successfully announced sync. New ruling
epoch:49
Apr 28 15:41:06 SC-1 osafimmnd[2607]: NO NODE STATE-> IMM_NODE_R_AVAILABLE
---
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
