- **Version**: --> 4.2.2RC1
---
** [tickets:#425] amf: Opensaf failed to comeup on controller after node went
for reboot**
**Status:** unassigned
**Created:** Fri May 31, 2013 06:29 AM UTC by Praveen
**Last Updated:** Fri May 31, 2013 06:30 AM UTC
**Owner:** nobody
Migrated from http://devel.opensaf.org/ticket/2843.
The issue is seen on SLES 64bit VM setup.
PBE is enabled and loaded with 9k obkects.
Post http://devel.opensaf.org/ticket/2842, when the active controller went for
reboot, opensaf failed to comeup. Following are the messages seen in the syslog:
Oct 6 19:44:38 SLES-SLOT-1 osafclmna[2781]:
safNode=SC-1,safCluster=myClmCluster Joined cluster, nodeid=2010f
Oct 6 19:44:38 SLES-SLOT-1 osafamfd[2790]: Started
Oct 6 19:44:38 SLES-SLOT-1 osafamfd[2790]: Required attribute
saAmfCtDefQuiescingCompleteTimeout not configured for
'safVersion=4.4.0,safCompType=Comp_nwayApp_demo'
Oct 6 19:44:38 SLES-SLOT-1 osafamfd[2790]: Required attribute
saAmfCtDefQuiescingCompleteTimeout not configured for
'safVersion=4.0.0,safCompType=Comp_NwayApp_n_1_1'
Oct 6 19:44:38 SLES-SLOT-1 osafamfd[2790]:
'safSupportedCsType=safVersion=4.1.0\,safCSType=nd_cs_bt1,safVersion=4.0.0,safCompType=Comp_NwayApp_n_1_1'
does not exist in model
Oct 6 19:44:38 SLES-SLOT-1 osafamfd[2790]: Failed to read configuration, AMF
will not start
Oct 6 19:44:38 SLES-SLOT-1 osafamfd[2790]: avd_imm_config_get FAILED
Oct 6 19:44:38 SLES-SLOT-1 osafamfd[2790]: avd_standby_role_initialization
FAILED
Oct 6 19:44:38 SLES-SLOT-1 osafamfd[2790]: main: avd_initialize FAILED,
exiting...
Oct 6 19:44:38 SLES-SLOT-1 opensafd[2594]: Failed DESC:AMFD
Oct 6 19:44:38 SLES-SLOT-1 opensafd[2594]: Going for recovery
Oct 6 19:44:39 SLES-SLOT-1 kernel: eth0: no IPv6 routers present
Oct 6 19:44:39 SLES-SLOT-1 opensafd: warning: TIPC module unloading failed
Oct 6 19:44:39 SLES-SLOT-1 opensafd: Starting OpenSAF failed
Traces from the active controller are attached.
Changed 8 months ago by allasirisha
This is observed if
safSupportedCsType=safVersion=4.1.0\,safCSType=nd_cs_bt1,safVersion=4.0.0,safCompType=Comp_NwayApp_n_1_1
is deleted before the node goes for reboot. If the cluster is reset at this
point, the cluster fails to come up.
Changed 8 months ago by praveenmalviya
â– priority changed from critical to major
This ticket is similar to #2013, #2120 & #2083 and they are not critical. All
these tickets are not stopping anyone from using opensaf. So changing it to
major.
---
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.
------------------------------------------------------------------------------
Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resources for efficient Application Performance Management.
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
