[Openais] Problem stoping Corosync+Pacemaker

Adrián Ebay achapela.rexistros at gmail.com
Wed Nov 4 15:57:36 PST 2009 

2009/11/4 Michael Schwartzkopff <misch at multinet.de>

> Am Mittwoch, 4. November 2009 15:32:43 schrieb Adrian Chapela:
> > Hello,
> >
> > when I try to stop corosync+pacemaker I could stop all process. Always
> > remain active lrmd and pengine. This happens if I have configured the
> > next pingd clone:
> > <clone id="Connected">
> >     <primitive id="ping" provider="pacemaker" class="ocf" type="ping">
> >       <instance_attributes id="ping-attrs">
> >         <nvpair id="pingd-dampen" name="dampen" value="5s"/>
> >         <nvpair id="pingd-multiplier" name="multiplier" value="1000"/>
> >         <nvpair id="pingd-hosts" name="host_list" value="192.168.18.210
> > 192.168.18.254"/>
> >       </instance_attributes>
> >       <operations>
> >         <op id="ping-monitor-60s" interval="60s" name="monitor"/>
> >       </operations>
> >     </primitive>
> >   </clone>
> >
> > Log messages:
> > *****************************************************
> > Nov  4 15:23:09 correo3 lrmd: [26452]: debug: a stonith RA operation
> > queue to run, call_id=26453.
> > Nov  4 15:23:09 correo3 lrmd: [26452]: debug:
> > stonithd_receive_ops_result: begin
> > Nov  4 15:23:09 correo3 stonithd: [26453]: debug: external_status:
> called.
> > Nov  4 15:23:09 correo3 stonithd: [26453]: debug: external_run_cmd:
> > Calling '/usr/lib64/stonith/plugins/external/ssh status'
> > Nov  4 15:23:09 correo3 stonithd: [26453]: debug: external_run_cmd:
> > '/usr/lib64/stonith/plugins/external/ssh status' output:
> > Nov  4 15:23:09 correo3 stonithd: [26453]: debug: external_status:
> > running 'ssh status' returned 0
> > Nov  4 15:23:09 correo3 stonithd: [25454]: debug: Child process
> > external_stonithclone:1_monitor [26453] exited, its exit code: 0 when
> > signo=0.
> > Nov  4 15:23:09 correo3 stonithd: [25454]: debug: stonithclone:1's
> > (external/ssh) op monitor finished. op_result=0
> > Nov  4 15:23:09 correo3 stonithd: [25454]: debug: client
> > STONITH_RA_EXEC_26452 (pid=26452) signed off
> > Nov  4 15:23:09 correo3 attrd: [25457]: ERROR: ais_dispatch: Receiving
> > message body failed: (2) Library error: Resource temporarily unavailable
> > (11)
> > Nov  4 15:23:09 correo3 attrd: [25457]: ERROR: ais_dispatch: AIS
> > connection failed
> > Nov  4 15:23:09 correo3 attrd: [25457]: CRIT: attrd_ais_destroy: Lost
> > connection to OpenAIS service!
> > Nov  4 15:23:09 correo3 attrd: [25457]: info: main: Exiting...
> > Nov  4 15:23:09 correo3 attrd: [25457]: debug: cib_native_signoff:
> > Signing out of the CIB Service
> > Nov  4 15:23:09 correo3 attrd: [25457]: ERROR:
> > attrd_cib_connection_destroy: Connection to the CIB terminated...
> > Nov  4 15:23:09 correo3 cib: [25455]: ERROR: ais_dispatch: Receiving
> > message body failed: (2) Library error: Resource temporarily unavailable
> > (11)
> > Nov  4 15:23:09 correo3 cib: [25455]: ERROR: ais_dispatch: AIS
> > connection failed
> > Nov  4 15:23:09 correo3 cib: [25455]: ERROR: cib_ais_destroy: AIS
> > connection terminated
> > Nov  4 15:23:09 correo3 crmd: [25459]: ERROR: ais_dispatch: Receiving
> > message body failed: (2) Library error: Resource temporarily unavailable
> > (11)
> > Nov  4 15:23:09 correo3 crmd: [25459]: ERROR: ais_dispatch: AIS
> > connection failed
> > Nov  4 15:23:09 correo3 crmd: [25459]: ERROR: crm_ais_destroy: AIS
> > connection terminated
> > Nov  4 15:23:09 correo3 lrmd: [25456]: debug: on_receive_cmd: the IPC to
> > client [pid:25459] disconnected.
> > Nov  4 15:23:09 correo3 lrmd: [25456]: debug: unregister_client: client
> > crmd [pid:25459] is unregistered
> > Nov  4 15:23:09 correo3 stonithd: [25454]: ERROR: ais_dispatch:
> > Receiving message body failed: (2) Library error: No such file or
> > directory (2)
> > Nov  4 15:23:09 correo3 stonithd: [25454]: ERROR: ais_dispatch: AIS
> > connection failed
> > Nov  4 15:23:09 correo3 stonithd: [25454]: ERROR: AIS connection
> terminated
> > Nov  4 15:23:13 correo3 attrd_updater: [26471]: info: Invoked:
> > attrd_updater -n pingd -v 2000 -d 5s
> > Nov  4 15:23:13 correo3 attrd_updater: [26471]: info: attrd_lazy_update:
> > Connecting to cluster... 5 retries remaining
> > Nov  4 15:23:13 correo3 attrd_updater: [26471]: debug:
> > init_client_ipc_comms_nodispatch: Attempting to talk on:
> > /usr/var/run/crm/attrd
> > Nov  4 15:23:13 correo3 attrd_updater: [26471]: debug:
> > init_client_ipc_comms_nodispatch: Could not init comms on:
> > /usr/var/run/crm/attrd
> > Nov  4 15:23:15 correo3 attrd_updater: [26471]: info: attrd_lazy_update:
> > Connecting to cluster... 4 retries remaining
> > Nov  4 15:23:15 correo3 attrd_updater: [26471]: debug:
> > init_client_ipc_comms_nodispatch: Attempting to talk on:
> > /usr/var/run/crm/attrd
> > Nov  4 15:23:15 correo3 attrd_updater: [26471]: debug:
> > init_client_ipc_comms_nodispatch: Could not init comms on:
> > /usr/var/run/crm/attrd
> > Nov  4 15:23:17 correo3 attrd_updater: [26471]: info: attrd_lazy_update:
> > Connecting to cluster... 3 retries remaining
> > Nov  4 15:23:17 correo3 attrd_updater: [26471]: debug:
> > init_client_ipc_comms_nodispatch: Attempting to talk on:
> > /usr/var/run/crm/attrd
> > Nov  4 15:23:17 correo3 attrd_updater: [26471]: debug:
> > init_client_ipc_comms_nodispatch: Could not init comms on:
> > /usr/var/run/crm/attrd
> > Nov  4 15:23:19 correo3 attrd_updater: [26471]: info: attrd_lazy_update:
> > Connecting to cluster... 2 retries remaining
> > Nov  4 15:23:19 correo3 attrd_updater: [26471]: debug:
> > init_client_ipc_comms_nodispatch: Attempting to talk on:
> > /usr/var/run/crm/attrd
> > Nov  4 15:23:19 correo3 attrd_updater: [26471]: debug:
> > init_client_ipc_comms_nodispatch: Could not init comms on:
> > /usr/var/run/crm/attrd
> > Nov  4 15:23:21 correo3 attrd_updater: [26471]: info: attrd_lazy_update:
> > Connecting to cluster... 1 retries remaining
> > Nov  4 15:23:21 correo3 attrd_updater: [26471]: debug:
> > init_client_ipc_comms_nodispatch: Attempting to talk on:
> > /usr/var/run/crm/attrd
> > Nov  4 15:23:21 correo3 attrd_updater: [26471]: debug:
> > init_client_ipc_comms_nodispatch: Could not init comms on:
> > /usr/var/run/crm/attrd
> > Nov  4 15:23:23 correo3 lrmd: [25456]: info: RA output:
> > (ping:1:stop:stderr) Could not update pingd=2000
> > Nov  4 15:23:23 correo3 lrmd: [25456]: info: RA output:
> > (ping:1:stop:stderr) rm: missing operand#012Try `rm --help' for more
> > information.
> > Nov  4 15:23:23 correo3 attrd_updater: [26479]: info: Invoked:
> > attrd_updater -D -n pingd -d 5s
> > Nov  4 15:23:23 correo3 attrd_updater: [26479]: info: attrd_lazy_update:
> > Connecting to cluster... 5 retries remaining
> > Nov  4 15:23:23 correo3 attrd_updater: [26479]: debug:
> > init_client_ipc_comms_nodispatch: Attempting to talk on:
> > /usr/var/run/crm/attrd
> > Nov  4 15:23:23 correo3 attrd_updater: [26479]: debug:
> > init_client_ipc_comms_nodispatch: Could not init comms on:
> > /usr/var/run/crm/attrd
> > Nov  4 15:23:24 correo3 lrmd: [25456]: WARN: ping:1:stop process (PID
> > 26272) timed out (try 1).  Killing with signal SIGTERM (15).
> > Nov  4 15:23:24 correo3 lrmd: [25456]: info: RA output:
> > (ping:1:stop:stderr) Terminated
> > Nov  4 15:23:24 correo3 ping[26272]: INFO: They use TERM to bring us
> > down. No such luck.
> > Nov  4 15:23:24 correo3 lrmd: [25456]: info: RA output:
> > (ping:1:stop:stderr) 2009/11/04_15:23:24 INFO: They use TERM to bring us
> > down. No such luck.
> > Nov  4 15:23:24 correo3 lrmd: [25456]: info: Managed ping:1:stop process
> > 26272 exited with return code 0.
> > Nov  4 15:23:24 correo3 lrmd: [25456]: debug: record_op_completion:
> > cannot record operation stop[15] on ocf::ping::ping:1 for client 25459:
> > client is gone.
> > Nov  4 15:23:24 correo3 lrmd: [25456]: ERROR: notify_client: client for
> > the operation operation stop[15] on ocf::ping::ping:1 for client 25459,
> > its parameters: multiplier=[1000] CRM_meta_op_target_rc=[7] dampen=[5s]
> > CRM_meta_timeout=[20000] CRM_meta_clone_max=[2] crm_feature_set=[3.0.1]
> > host_list=[192.168.18.210 192.168.18.254]
> > CRM_meta_globally_unique=[false] CRM_meta_clone=[1]  does not exist and
> > client requested notification.
>
> Hi,
>
> what version of corosync do you use? There was a bug that only was fixed in
> version 1.1.2.
>

I am using this version 1.1.2 combined with Pacemaker 1.0.6 (With 1.0.5
happens the same)


>
> Greetings,
> --
> Dr. Michael Schwartzkopff
> MultiNET Services GmbH
> Addresse: Bretonischer Ring 7; 85630 Grasbrunn; Germany
> Tel: +49 - 89 - 45 69 11 0
> Fax: +49 - 89 - 45 69 11 21
> mob: +49 - 174 - 343 28 75
>
> mail: misch at multinet.de
> web: www.multinet.de
>
> Sitz der Gesellschaft: 85630 Grasbrunn
> Registergericht: Amtsgericht München HRB 114375
> Geschäftsführer: Günter Jurgeneit, Hubert Martens
>
> ---
>
> PGP Fingerprint: F919 3919 FF12 ED5A 2801 DEA6 AA77 57A4 EDD8 979B
> Skype: misch42
> _______________________________________________
> Openais mailing list
> Openais at lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/openais
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.linux-foundation.org/pipermail/openais/attachments/20091105/f321c48d/attachment.htm

More information about the Openais mailing list