If you set trace_ra=1 as an instance attribute of the primitive (rather than of the stop operation), it should capture a trace of all operations, including stop. I know this isn't exactly what you're asking, since tracing every operation will result in more logs.
With that being said, I tested on an ocf:heartbeat:Dummy resource. When I added trace_ra=1 as an instance attribute of the monitor operation, it **did** capture a trace of recurring monitors. When I added trace_ra=1 as an instance attribute of the stop operation, it **did not** capture a trace of the stop. I don't know off the top of my head how Pacemaker handles <instance_attributes> that are nested within an <op>, so I'm not sure why there's a discrepancy between monitor and stop operations. On Mon, Sep 28, 2020 at 12:43 PM Lentes, Bernd <bernd.len...@helmholtz-muenchen.de> wrote: > > Hi, > > currently i have a VirtualDomains resource which sometimes fails to stop. > To investigate further i'm tracing the stop operation of this resource. > But although i stopped it already now several times, nothing appears in > /var/lib/heartbeat/trace_ra/. > > This is my config: > primitive vm_amok VirtualDomain \ > params config="/mnt/share/vm_amok.xml" \ > params hypervisor="qemu:///system" \ > params migration_transport=ssh \ > params migrate_options="--p2p --tunnelled" \ > op start interval=0 timeout=120 \ > op monitor interval=30 timeout=25 \ > op migrate_from interval=0 timeout=300 \ > op migrate_to interval=0 timeout=300 \ > op stop interval=0 timeout=180 \ > op_params trace_ra=1 \ > meta allow-migrate=true target-role=Started is-managed=true > maintenance=false \ > > <primitive id="vm_amok" class="ocf" provider="heartbeat" > type="VirtualDomain"> > <instance_attributes id="vm_amok-instance_attributes"> > <nvpair name="config" value="/mnt/share/vm_amok.xml" > id="vm_amok-instance_attributes-config"/> > </instance_attributes> > <instance_attributes id="vm_amok-instance_attributes-0"> > <nvpair name="hypervisor" value="qemu:///system" > id="vm_amok-instance_attributes-0-hypervisor"/> > </instance_attributes> > <instance_attributes id="vm_amok-instance_attributes-1"> > <nvpair name="migration_transport" value="ssh" > id="vm_amok-instance_attributes-1-migration_transport"/> > </instance_attributes> > <instance_attributes id="vm_amok-instance_attributes-2"> > <nvpair name="migrate_options" value="--p2p --tunnelled" > id="vm_amok-instance_attributes-2-migrate_options"/> > </instance_attributes> > <operations> > <op name="start" interval="0" timeout="120" id="vm_amok-start-0"/> > <op name="monitor" interval="30" timeout="25" > id="vm_amok-monitor-30"/> > <op name="migrate_from" interval="0" timeout="300" > id="vm_amok-migrate_from-0"/> > <op name="migrate_to" interval="0" timeout="300" > id="vm_amok-migrate_to-0"/> > <op name="stop" interval="0" timeout="180" id="vm_amok-stop-0"> > <instance_attributes id="vm_amok-stop-0-instance_attributes"> > <nvpair name="trace_ra" value="1" > id="vm_amok-stop-0-instance_attributes-trace_ra"/> > </instance_attributes> > </op> > </operations> > > Any ideas ? > SLES 12 SP4, pacemaker-1.1.19+20181105.ccd6b5b10-3.13.1.x86_64 > > Bernd > > -- > > Bernd Lentes > Systemadministration > Institute for Metabolism and Cell Death (MCD) > Building 25 - office 122 > HelmholtzZentrum München > bernd.len...@helmholtz-muenchen.de > phone: +49 89 3187 1241 > phone: +49 89 3187 3827 > fax: +49 89 3187 2294 > http://www.helmholtz-muenchen.de/mcd > > stay healthy > Helmholtz Zentrum München > > Helmholtz Zentrum München > > _______________________________________________ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users > > ClusterLabs home: https://www.clusterlabs.org/ -- Regards, Reid Wahl, RHCA Senior Software Maintenance Engineer, Red Hat CEE - Platform Support Delivery - ClusterHA _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/