Please see inline. Thanks, Praveen On 10-Jul-13 6:21 AM, opensaf dev wrote: > Hi, > > > While instantiating an SA-Aware component from command line using below > command in the payload node failed > > #amf-adm unlock-in safSu=SU3,safSg=AmfDemo,safApp=AmfDemo2 > #error - command timed out (alarm) > > > Payload Node Logs: > payload1 osafamfnd[41959]: NO Instantiation of > 'safComp=AmfDemo,safSu=SU3,safSg=AmfDemo,safApp=AmfDemo2' failed > payload1 osafamfnd[41959]: NO Reason: component registration timer expired > payload1 osafamfnd[41959]: NO 'safSu=SU3,safSg=AmfDemo,safApp=AmfDemo2' > Presence State INSTANTIATING => INSTANTIATION_FAILED > payload1 osafimmnd[41923]: WA Continuation for AdminOp was lost, probably > due to timeout > > Controller Node Logs: > Active Controller Log: > NO safApp=safAmfService "Admin op "UNLOCK_INSTANTIATION" initiated for > 'safSu=SU3,safSg=AmfDemo,safApp=AmfDemo2', invocation: 12884901889 > NO safApp=safAmfService "safSu=SU3,safSg=AmfDemo,safApp=AmfDemo2 AdmState > LOCKED_INSTANTIATION => LOCKED > NO safApp=safAmfService "Admin op done for invocation: 12884901889, result > 29 > NO safApp=safAmfService "safSu=SU3,safSg=AmfDemo,safApp=AmfDemo2 OperState > ENABLED => DISABLED > > While initial saAmfCtDefClcCliTimeout was 10000000000, I changed to 60 sec > and same result. When I took a dump of the running imm, it showed the model > information I had configured. > > Please let me know > > 1. How to enable log for all/debug levels in both controller and payload > nodes. Var log messages are kind of not enough. Enabling log for all levels can be done in amfnd.conf and amfd.conf at the location /etc/opensaf/. > 2. How do I know if script is called or not? Where do I find the logs > present in the CLC-CLI script? Please check: 1) If CLC_CLI script is invoking the binary of the component or not. 2) All links are resolved in the component binary and it is placed at the path given in CLC_CLI script. SU will move to INSTANTIATION_FAILED because component moved to INSTANTIATION_FAILED state as it could not be instantiated successfully. For a component it happens when CLC_CLI script exits improperly or component does not register itself within saAmfCtDefClcCliTimeout. > Apprecitate if any help or direction provided. > > Thanks, > Dev > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Opensaf-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/opensaf-users
------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Opensaf-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-users
