Hello all,
I'm seeing a problem when gracefully shutting down opensaf (4.3.1).
I have a proxy/proxied setup which works great, except for the
graceful shutdown of opensaf. The proxy is in a different service group
(NoRed) than the proxied (2N).
Here's what I'm seeing.
1. CSI remove for the proxy component.
2. CSI remove for the proxied component.
3. These succeed according to AMF.
4. Cleanup request for the proxied component (via the ProxiedCleanup
callback in the proxy)
5. At the same time as this, AMF sends a cleanup request to the proxy
(via its CLC-CLI cleanup). This doesn't look right.
This is the problem because the cleanup of the proxy terminates the
proxy, even though it is still servicing the cleanup of the proxied
component. As a result, AMF thinks the termination of the proxied
component fails (never finishes), and reboots the blade.
I even tried putting a signal handler into the proxy, so that when
it receives the SIGTERM from the CLC-CLI CLEANUP, it will at least wait
to terminate until it finishes servicing the cleanup of the proxied
component. I know in this case the saAmfResponse (in the ProxiedCleanup
callback) goes out with success, but it doesn't look like AMF gets it
because it still does the same thing.
Is this expected behavior? Or do I have some configuration error
somewhere?
I'm happy to provide tracing output from amfnd or /var/log/messages....
Thanks.
Alex
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-users
