Menu
▾
▴
Re: [users] clean up not called while locking SU
|
From: opensaf d. <ope...@gm...> - 2013-08-09 02:00:37
|
Could somebody look at the issue I am facing, on the cleanup not being
called while locking in a SU.
Thanks,
Dev
On Thu, Aug 8, 2013 at 8:20 AM, Hans Feldt <han...@er...> wrote:
> Ok maybe I misunderstood, Su lock-in needs to terminate all processes of
> all components in the su.
>
> That is the way it is supposed to work...
>
> Sent from my smart phone
>
> Hans Feldt <han...@er...> skrev:
>
>
> On 08/08/2013 04:13 PM, opensaf dev wrote:
> > Hi Hans,
> >
> > I wanted to bring down the components running in a particular SU. In my
> case, every time I do lock SU followed by a
> > lock-in SU, the CSIs are removed and components are terminated properly
> in opensaf context, however the running process
> > instances(ps aux | grep component) still exists with its PID. The next
> time I try to unlock-in the same SU, a new set of
> > process instances are created for the same components making the old as
> zombie process. Every iteration of doing so
> > creates a bunch of zombie process.
> >
> > My requirement is to bring down a SU with all its components(process
> instance killed and pid file removed like cleanup)
> > with out affecting the other running SUs in the node.
> >
> > Is this possible in some way in opensaf? I am using version 4.2.3.
>
> Yes just lock the SU you are interested in.
>
> The problem is your AMF CLC CLI scripts that does not handle this.
>
> for example removing a stale pid file in instantiate
>
> /Hans
>
>
> >
> > Thanks
> > Dev
> >
> >
> > On Thu, Aug 8, 2013 at 6:51 AM, Hans Feldt <han...@er...<mailto:
> han...@er...>> wrote:
> >
> >
> > On 08/08/2013 03:45 PM, opensaf dev wrote:
> >
> > Thanks a lot Hans.
> >
> > I was intending to bring down the SU for some maintenance
> purpose with all the components it consists of. In openSAF
> > context what would be the alternative to bring down a single SU
> in a payload node and all its components?
> > Bringing the
> >
> >
> > Not sure I understand, you can lock a single SU or a node. Your
> choice...
> > /Hans
> >
> > whole service down by doing service opensafd stop works, but it
> brings down all the SUs in that payload load.
> >
> > Thanks
> > Dev
> >
> >
> > On Thu, Aug 8, 2013 at 12:15 AM, Hans Feldt <
> han...@er... <mailto:han...@er...>
> > <mailto:hans.feldt@ericsson.__com <mailto:
> han...@er...>>> wrote:
> >
> > Hi,
> >
> > The cleanup command is not executed by AMF when an SU is
> LOCKED-IN. The cleanup command is only used when
> > there is
> > an error associated with a component.
> >
> > Thanks,
> > Hans
> >
> >
> > On 08/07/2013 08:43 PM, opensaf dev wrote:
> >
> > hi,
> >
> > Any suggestion on the below issue is greatly appreciated
> >
> > Issue: SA-Aware Component is not getting killed after a
> lock and lock-in
> > the SU with one component. The pid file created during
> instatiation of the
> > component is also not removed because of this.
> >
> > With a SU with initial admin state as
> LOCKED-INSTANTIATION as in amfdemo, I
> > did unlock-in and unlock. And then when I did a lock
> and lock-in on the
> > same SU,
> > the cleanup scrpt is not invoked from the Opensaf as
> defined in IMM. Is
> > this a correct behaviour or am I missing something in
> IMM which prevents
> > calling cleanup during lock and lock-in to bring back
> the SU to original
> > state.
> >
> >
> >
> > Enviroment:
> > One payload node
> > 1 SG and 1 SU and 1 component
> >
> > Component Logs
> > On Lock
> > 11:09:32.451 Setting CSI for componentName
> >
> (safComp=inet,safSu=inetSU,____safSg=inetSG,safApp=inetApp, QUIESCED)
> >
> > 11:09:32.451 CsiDescriptor flags:(TARGET_ALL)
> > 11:09:32.451 CSI Set for all CSI's
> > 11:09:32.533 Removing CSI for
> >
> {safComp=inet,safSu=inetSU,____safSg=inetSG,safApp=inetApp}
> >
> > 11:09:32.534 Responding {OK} to AMF.
> >
> > On Lock-in
> > 11:10:34.429 Terminating
> >
> {safComp=inet,safSu=inetSU,____safSg=inetSG,safApp=inetApp}
> >
> > 11:10:34.431 Responding {OK} to AMF.
> > 11:10:34.433 Terminated the component
> >
> {safComp=inet,safSu=inetSU,____safSg=inetSG,safApp=inetApp}
> >
> > 11:10:34.437 Dispatch terminated..
> >
> > /var/log/messages
> >
> > [root@payload1 bin]# amf-adm unlock-in
> > safSu=inetSU,safSg=inetSG,____safApp=inetApp
> >
> >
> > Aug 7 11:08:02 payload1 osafamfnd[1096]: IN
> >
> 'safComp=inet,safSu=inetSU,____safSg=inetSG,safApp=inetApp' Presence State
> >
> > UNINSTANTIATED => INSTANTIATING
> > Aug 7 11:08:02 payload1 osafamfnd[1096]: NO
> > 'safSu=inetSU,safSg=inetSG,____safApp=inetApp' Presence
> State UNINSTANTIATED =>
> >
> > INSTANTIATING
> > Aug 7 11:08:02 payload1 clc_cli_script: Running the
> CLC-CLI script for
> > component: inet
> > Aug 7 11:08:02 payload1 clc_cli_script: CLC-CLI
> arguments: instantiate
> > inet
> > Aug 7 11:08:02 payload1 clc_cli_script: Module name:
> inet !!
> > Aug 7 11:08:02 payload1 clc_cli_script: Inside
> Start|Instantiate Function!!
> > Aug 7 11:08:02 payload1 clc_cli_script: Starting inet
> !!
> > Aug 7 11:08:08 payload1 osafamfnd[1096]: IN
> >
> 'safComp=inet,safSu=inetSU,____safSg=inetSG,safApp=inetApp' Presence State
> >
> > INSTANTIATING => INSTANTIATED
> > Aug 7 11:08:08 payload1 osafamfnd[1096]: NO
> > 'safSu=inetSU,safSg=inetSG,____safApp=inetApp' Presence
> State INSTANTIATING =>
> > INSTANTIATED
> >
> > [root@payload1 bin]# amf-adm unlock
> safSu=inetSU,safSg=inetSG,____safApp=inetApp
> >
> >
> > Aug 7 11:08:30 payload1 osafimmnd[1064]: IN Create
> runtime object
> >
> 'safSISU=safSu=inetSU\#safSg=____inetSG\#safApp=inetApp,safSi=____inetSUSI,safApp=inetApp'
> >
> > by Impl id: 3
> > Aug 7 11:08:30 payload1 osafimmnd[1064]: IN Create
> runtime object
> >
> >
> 'safCSIComp=safComp=inet\#____safSu=inetSU\#safSg=inetSG\#____safApp=inetApp,safCsi=inet,____safSi=inetSUSI,safApp=inetApp'
> >
> > by Impl id: 3
> > Aug 7 11:08:30 payload1 osafamfnd[1096]: NO Assigning
> > 'safSi=inetSUSI,safApp=____inetApp' ACTIVE to
> > 'safSu=inetSU,safSg=inetSG,____safApp=inetApp'
> >
> > Aug 7 11:08:30 payload1 osafamfnd[1096]: IN Assigning
> > 'safCsi=inet,safSi=inetSUSI,____safApp=inetApp' ACTIVE
> to
> >
> 'safComp=inet,safSu=inetSU,____safSg=inetSG,safApp=inetApp'
> >
> > Aug 7 11:08:30 payload1 osafamfnd[1096]: IN Assigned
> > 'safCsi=inet,safSi=inetSUSI,____safApp=inetApp' ACTIVE
> to
> >
> 'safComp=inet,safSu=inetSU,____safSg=inetSG,safApp=inetApp'
> >
> > Aug 7 11:08:30 payload1 osafamfnd[1096]: NO Assigned
> > 'safSi=inetSUSI,safApp=____inetApp' ACTIVE to
> > 'safSu=inetSU,safSg=inetSG,____safApp=inetApp'
> >
> >
> > [root@payload1 bin]# amf-adm lock
> safSu=inetSU,safSg=inetSG,____safApp=inetApp
> >
> >
> > Aug 7 11:09:32 payload1 osafamfnd[1096]: NO Assigning
> > 'safSi=inetSUSI,safApp=____inetApp' QUIESCED to
> > 'safSu=inetSU,safSg=inetSG,____safApp=inetApp'
> >
> > Aug 7 11:09:32 payload1 osafamfnd[1096]: IN Assigning
> 'all CSIs' QUIESCED
> > to
> 'safComp=inet,safSu=inetSU,____safSg=inetSG,safApp=inetApp'
> >
> > Aug 7 11:09:32 payload1 osafamfnd[1096]: IN Assigned
> 'all CSIs' QUIESCED
> > to
> 'safComp=inet,safSu=inetSU,____safSg=inetSG,safApp=inetApp'
> >
> > Aug 7 11:09:32 payload1 osafamfnd[1096]: NO Assigned
> > 'safSi=inetSUSI,safApp=____inetApp' QUIESCED to
> > 'safSu=inetSU,safSg=inetSG,____safApp=inetApp'
> >
> > Aug 7 11:09:32 payload1 osafamfnd[1096]: NO Removing
> > 'safSi=inetSUSI,safApp=____inetApp' from
> > 'safSu=inetSU,safSg=inetSG,____safApp=inetApp'
> >
> > Aug 7 11:09:32 payload1 osafamfnd[1096]: IN Removing
> 'all CSIs' from
> >
> 'safComp=inet,safSu=inetSU,____safSg=inetSG,safApp=inetApp'
> >
> > Aug 7 11:09:32 payload1 osafamfnd[1096]: IN Removed
> 'all CSIs' from
> >
> 'safComp=inet,safSu=inetSU,____safSg=inetSG,safApp=inetApp'
> >
> > Aug 7 11:09:32 payload1 osafamfnd[1096]: NO Removed
> > 'safSi=inetSUSI,safApp=____inetApp' from
> > 'safSu=inetSU,safSg=inetSG,____safApp=inetApp'
> >
> > Aug 7 11:09:32 payload1 osafimmnd[1064]: IN Delete
> runtime object
> >
> >
> 'safCSIComp=safComp=inet\#____safSu=inetSU\#safSg=inetSG\#____safApp=inetApp,safCsi=inet,____safSi=inetSUSI,safApp=inetApp'
> >
> > by Impl-id: 3
> > Aug 7 11:09:32 payload1 osafimmnd[1064]: IN Delete
> runtime object
> >
> 'safSISU=safSu=inetSU\#safSg=____inetSG\#safApp=inetApp,safSi=____inetSUSI,safApp=inetApp'
> >
> > by Impl-id: 3
> >
> > [root@payload1 bin]# amf-adm lock-in
> > safSu=inetSU,safSg=inetSG,____safApp=inetApp
> >
> >
> > Aug 7 11:10:34 payload1 osafamfnd[1096]: IN
> >
> 'safComp=inet,safSu=inetSU,____safSg=inetSG,safApp=inetApp' Presence State
> >
> > INSTANTIATED => TERMINATING
> > Aug 7 11:10:34 payload1 osafamfnd[1096]: NO
> > 'safSu=inetSU,safSg=inetSG,____safApp=inetApp' Presence
> State INSTANTIATED =>
> >
> > TERMINATING
> > Aug 7 11:10:34 payload1 osafamfnd[1096]: IN
> >
> 'safComp=inet,safSu=inetSU,____safSg=inetSG,safApp=inetApp' Presence State
> >
> > TERMINATING => UNINSTANTIATED
> > Aug 7 11:10:34 payload1 osafamfnd[1096]: NO
> > 'safSu=inetSU,safSg=inetSG,____safApp=inetApp' Presence
> State TERMINATING =>
> > UNINSTANTIATED
> >
> > Thanks,
> > Dev
> >
> ------------------------------____----------------------------__--__------------------
> >
> > Get 100% visibility into Java/.NET code with
> AppDynamics Lite!
> > It's a free troubleshooting tool designed for
> production.
> > Get down to code-level detail for bottlenecks, with <2%
> overhead.
> > Download for free and get started troubleshooting in
> minutes.
> > http://pubads.g.doubleclick.
> ____net/gampad/clk?id=48897031&iu=____/4140/ostg.clktrk
> > <http://pubads.g.doubleclick.
> __net/gampad/clk?id=48897031&iu=__/4140/ostg.clktrk
> > <
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> >>
> > ___________________________________________________
> > Opensaf-users mailing list
> > Opensaf-users@lists.__sourcefo__rge.net <
> http://sourceforge.net>
> > <mailto:Opensaf-users@lists.__sourceforge.net <mailto:
> Ope...@li...>>
> > https://lists.sourceforge.net/____lists/listinfo/opensaf-users
> > <https://lists.sourceforge.net/__lists/listinfo/opensaf-users>
> > <https://lists.sourceforge.
> __net/lists/listinfo/opensaf-__users
> > <https://lists.sourceforge.net/lists/listinfo/opensaf-users>>
> >
> >
> >
> >
>
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> _______________________________________________
> Opensaf-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensaf-users
>
|