The pbe was on one of the payloads because the new IMMND coord was there.
~~~
May 23 15:04:25 REG-S1 osafimmd[9959]: NO First Veteran IMMND found (payload)
at 2040f this IMMD at 2010f. Apparent IMMD lapse, *not* 2PBE => designating
that IMMND as coordinator
~~~
The problem here is pbe OI was not connected after the cluster was back from
headless. We expect this
~~~
NO Implementer disconnected XX <XX, XXXX> (OpenSafImmPBE)
~~~
immnd_fevs_local_checks() rejected the object-modify request with ERR_TRY_AGAIN
because immModel_pbeNotWritable() returned true.
Please provide the log on PL-4 (2040f) for further investigation.
---
** [tickets:#1846] Imm Headless: Imm service is not working when all SC's
joined back to the headless cluster.**
**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Tue May 24, 2016 07:19 AM UTC by Madhurika Koppula
**Last Updated:** Tue May 24, 2016 07:19 AM UTC
**Owner:** nobody
**Attachments:**
- [pbe.tgz](https://sourceforge.net/p/opensaf/tickets/1846/attachment/pbe.tgz)
(26.5 MB; application/octet-stream)
Setup:
1) Brought up cluster with Active SC, Standby SC, Spare SC and two payloads
PL-4 and PL-5 with headless feature enabled and with single PBE enabled.
May 23 14:28:29 REG-S1 osaffmd[8814]: Started
May 23 14:28:29 REG-S1 osafimmd[8824]: Started
May 23 14:28:29 REG-S1 osafimmd[8824]: NO ******* SC_ABSENCE_ALLOWED (Headless
Hydra) is configured: 900 ***********
May 23 14:28:29 REG-S1 osafimmnd[8835]: Started
2) Brought down all the controllers (Active, standby, spare SC's) without role
change and made the cluster as headless cluster. Payloads did not go for reboot.
3) But when all controllers joined back to the headless cluster, could not find
PBE process on any SC and immcfg operations got failed with TRY_AGAINS.
Below is the snippet:
REG-S1:/home/immPBE # immcfg -a saAmfSGCompRestartMax=1000
safSg=NoRed,safApp=OpenSAF
error - saImmOmCcbObjectModify_2 FAILED: SA_AIS_ERR_TRY_AGAIN (6)
Attaching Imm logs and syslog of Active and Standby controllers.
---
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.
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
