Hi Santosh, If premature return of admin lock/unlock is the concern, you can pick the following patch for #372
changeset: 5631:a35f4aff6652 branch: opensaf-4.4.x parent: 5629:caabfba704e8 user: Nagendra Kumar<[email protected]> date: Thu Aug 21 14:50:16 2014 +0530 summary: amfd: return admin op when csi assign/remove is over [#372] Thanks -Nagu > -----Original Message----- > From: santosh satapathy [mailto:[email protected]] > Sent: 25 February 2015 03:50 > To: [email protected] > Subject: [users] Incorrect command status from amf-adm unlock > > Hi, > > While starting one SU with SA aware components I see the command "amf-adm > -t 120 unlock SU Name" returns success(0) even though I see the CSI > assignments are not complete. amf-adm -t 120 unlock-in is success in this > case. Because of a persistent failure in the node, the component and hence > the SU is expected to fail/restart many times and during such scenario, the > amf-adm commands simply returns > without a timeout or error code other than 0. This gives a wrong perception > to the user that the SU has successfully started while it not. Underlying > it is still restarting/doing recovery/error > escalation trying to make it up. > > */var/log/messages *(One failure instance from the continuous > restart/repetition of logs): > Feb 24 16:48:53 node2 osafamfnd[4351]: NO > 'safSu=node2.SU,safSg=node2.SU,safApp=TestApp' Presence State > TERMINATING > => INSTANTIATED > Feb 24 16:48:53 node2 osafamfnd[4351]: NO Assigning > 'safSi=node2.SU,safApp=TestApp' ACTIVE to > 'safSu=node2.SU,safSg=node2.SU,safApp=TestApp' > > Feb 24 16:40:18 node2.xxx.lab [node2.SU-comp1] [AMF] ERROR - 90011 - > Failed > to start application.com.xxxx.xx.dao.exception.DaoException: A failure > occurred selecting from the database > Feb 24 16:40:18 node2 osafamfnd[4351]: NO > 'safComp=node2.SU.comp1,safSu=node2.SU,safSg=node2.SU,safApp=TestApp' > faulted due to 'errorReport' : Recovery is 'suFailover' > Feb 24 16:40:18 node2 osafamfnd[4351]: NO > 'safSu=node2.SU,safSg=node2.SU,safApp=TestApp' Presence State > INSTANTIATED > => TERMINATING > > Feb 24 16:40:18 node2 osafamfnd[4351]: NO > 'safComp=node2.SU.comp1,safSu=node2.SU,safSg=node2.SU,safApp=TestApp' > faulted due to 'errorReport' : Recovery is 'suFailover' > Feb 24 16:40:18 node2 osafamfnd[4351]: NO Assigned > 'safSi=node2.SU,safApp=TestApp' QUIESCED to > 'safSu=node2.SU,safSg=node2.SU,safApp=TestApp' > Feb 24 16:40:18 node2 startSAScript: Running the CLC-CLI script for > component: comp1 > Feb 24 16:40:18 node2 osafamfnd[4351]: NO Removed > 'safSi=node2.SU,safApp=TestApp' from > 'safSu=node2.SU,safSg=node2.SU,safApp=TestApp' > > Any help is much appreciated. > > -- > Best Regards, > Santosh > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > Opensaf-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/opensaf-users ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Opensaf-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-users
