Default term time during OpenSAF stop is (nid.conf):
\# Specifies how long "rootd stop" should wait before stop has considered to
fail
OPENSAF_TERMTIMEOUT=60
In AppConfig-nwayactive.xml for clean up script saAmfCtDefClcCliTimeout is 10
seconds.
Are these values same?
AMFND is exiting even if comp fails:
avnd_comp_clc_terming_cleanfail_hdler() {
...
avnd_comp_curr_info_del(cb, comp);
if ((cb->term_state == AVND_TERM_STATE_OPENSAF_SHUTDOWN_STARTED) &&
all_comps_terminated()) {
LOG_WA("Terminated all AMF components (with failures)");
LOG_NO("Shutdown completed, exiting");
cb->nodeid_mdsdest_db.deleteAll();
cb->hctypedb.deleteAll();
exit(0);
}
}
---
** [tickets:#2098] amfnd: amfnd doesn't exit at opensafd stop**
**Status:** unassigned
**Milestone:** 5.2.FC
**Created:** Thu Oct 06, 2016 09:02 AM UTC by Hans Nordebäck
**Last Updated:** Thu Oct 06, 2016 09:02 AM UTC
**Owner:** nobody
amfnd doesn't exit at opensafd stop. This problem can be reproduced in UML
using the AmfDemo application, nwayactive:
1) Change the AppConfig-nwayactive.xml file to:
<attr>
<name>saAmfCtCompCategory</name>
<value>8</value>
</attr>
2) Do the following changes to the amf_demo_script to:
start()
{
return 0
}
build_uml install_testprog
opensaf start
3) unlock-in, unlock all 5 amf demo SUs
4) At PL-3 modify /opt/amf_demo_script :
stop()
{
while true
do
sleep 2
done
}
run /etc/init.d/opensafd stop and the following problem occurs:
Oct 6 10:45:37 PL-3 local0.notice osafamfnd[423]: NO Reason:'Script did not
exit within time'
Oct 6 10:45:37 PL-3 local0.warn osafamfnd[423]: WA
'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo2' Presence State
TERMINATING => TERMINATION_FAILED
Oct 6 10:45:37 PL-3 local0.notice osafamfnd[423]: NO
'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo2' Presence State TERMINATING =>
TERMINATION_FAILED
Oct 6 10:46:18 PL-3 user.notice opensafd: amfnd has not yet exited, killing it
forcibly.
Oct 6 10:46:18 PL-3 local0.alert osafclmna[414]: AL AMF Node Director is down,
terminate this process
Oct 6 10:46:18 PL-3 local0.crit osafamfwd[489]: Rebooting OpenSAF NodeId = 0
EE Name = No EE Mapped, Reason: AMF unexpectedly crashed, OwnNodeId = 131855,
SupervisionTime = 60
Oct 6 10:46:18 PL-3 user.notice opensaf_reboot: Rebooting local node;
timeout=60
O
---
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.------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
