If you have a fail-over time longer than 6 seconds then you are likely going to
get more serious problems than an ugly printout.
To be precise, It is time to fail-over services plus time for the new active
AMFD to attach. The registration of the new active AMFD as OI is visible in
the syslogs.
Could be that there is some deeper issue that needs resolving here.
Perhaps the TRY_AGAIN loop in the AMFD for re-attaching as OI has a
sleep that is too large o a back off that is too quick to add time.
---
** [tickets:#1384] amf-state print out error if it is called during failover**
**Status:** unassigned
**Milestone:** 4.5.2
**Created:** Tue Jun 09, 2015 07:28 AM UTC by Thuan
**Last Updated:** Wed Jun 10, 2015 11:17 AM UTC
**Owner:** nobody
When failover was trigger, there are some problems (maybe implementer
disconnect) with immlist tool in short time. So, immlist tool can’t get value
of variables or an empty value (ex: saAmfCSICompHAState=<Empty>). Then,
amf-state did not handle well with these empty values.
/usr/bin/amf-state: line 62: [: <Empty>: integer expression expected
Reproduction
====================
- Create a while loop for amf-state on Standby SC.
- Reboot the Active SC.
- Failover event occurs and problem occurs also.
---
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.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
