[ClusterLabs] Antw: Different Times in the Corosync Log?
Ulrich Windl
Ulrich.Windl at rz.uni-regensburg.de
Tue Aug 21 02:03:47 EDT 2018
Hi!
I could guess that the processes run with different timezone settings (for
whatever reason).
Regards,
Ulrich
>>> Eric Robinson <eric.robinson at psmnv.com> schrieb am 21.08.2018 um 02:43 in
Nachricht
<CY1PR03MB14051F7FCD4E6A8C69C00E4EFA310 at CY1PR03MB1405.namprd03.prod.outlook.com>
> The corosync log show different times for lrmd messages than for cib or crmd
> messages. Note the 4 hour difference. What?
>
>
> Aug 20 13:08:27 [107884] 001store01a cib: info: cib_perform_op:
> +
>
/cib/status/node_state[@id='1']/lrm[@id='1']/lrm_resources/lrm_resource[@id='
> p_replicator']/lrm_rsc_op[@id='p_replicator_monitor_60000']:
> @transition‑magic=0:0;9:251:0:283f3d6c‑2e91‑4f61‑95dd‑306d3e1eb052,
@call‑id=361,
> @rc‑code=0, @op‑status=0, @exec‑time=5
> Aug 20 13:08:27 [107884] 001store01a cib: info:
> cib_process_request: Completed cib_modify operation for section status: OK
> (rc=0, origin=001store01a/crmd/2451, version=0.30.5)
> Aug 20 13:08:32 [107884] 001store01a cib: info: cib_process_ping:
> Reporting our current digest to 001store01b:
> f33ca1999ceeb68d22f3171f03be2638 for 0.30.5 (0x55b38bd96280 0)
> Aug 20 17:08:45 [107886] 001store01a lrmd: warning:
> child_timeout_callback: p_azip_ftpclust01_monitor_0 process (PID 52488)
> timed out
> Aug 20 17:08:45 [107886] 001store01a lrmd: warning:
> operation_finished: p_azip_ftpclust01_monitor_0:52488 ‑ timed out after
> 20000ms
> Aug 20 13:08:45 [107889] 001store01a crmd: error:
> process_lrm_event: Result of probe operation for p_azip_ftpclust01 on
> 001store01a: Timed Out | call=359 key=p_azip_ftpclust01_monitor_0
> timeout=20000ms
> Aug 20 13:08:45 [107884] 001store01a cib: info:
> cib_process_request: Forwarding cib_modify operation for section status to
> all (origin=local/crmd/2452)
> Aug 20 13:08:45 [107884] 001store01a cib: info: cib_perform_op:
> Diff: ‑‑‑ 0.30.5 2
> Aug 20 13:08:45 [107884] 001store01a cib: info: cib_perform_op:
> Diff: +++ 0.30.6 (null)
> Aug 20 13:08:45 [107884] 001store01a cib: info: cib_perform_op:
> + /cib: @num_updates=6
> Aug 20 13:08:45 [107884] 001store01a cib: info: cib_perform_op:
> +
>
/cib/status/node_state[@id='1']/lrm[@id='1']/lrm_resources/lrm_resource[@id='
> p_azip_ftpclust01']/lrm_rsc_op[@id='p_azip_ftpclust01_last_0']:
> @transition‑magic=2:1;3:251:7:283f3d6c‑2e91‑4f61‑95dd‑306d3e1eb052,
@call‑id=359,
> @rc‑code=1, @op‑status=2, @exec‑time=20002
> Aug 20 13:08:45 [107884] 001store01a cib: info: cib_perform_op:
> ++
>
/cib/status/node_state[@id='1']/lrm[@id='1']/lrm_resources/lrm_resource[@id='
> p_azip_ftpclust01']: <lrm_rsc_op id="p_azip_ftpclust01_last_failure_0"
> operation_key="p_azip_ftpclust01_monitor_0" operation="monitor"
> crm‑debug‑origin="do_update_resource" crm_feature_set="3.0.14"
> transition‑key="3:251:7:283f3d6c‑2e91‑4f61‑95dd‑306d3e1eb052"
> transition‑magic="2:1;3:251:7:283f3d6c‑2e91‑4f61‑95dd‑306d3e1eb052"
> exit‑reason="" on_node="001
> Aug 20 13:08:45 [107884] 001store01a cib: info:
> cib_process_request: Completed cib_modify operation for section status: OK
> (rc=0, origin=001store01a/crmd/2452, version=0.30.6)
> Aug 20 13:08:45 [107889] 001store01a crmd: info: do_lrm_rsc_op:
> Performing key=3:252:0:283f3d6c‑2e91‑4f61‑95dd‑306d3e1eb052
> op=p_azip_ftpclust01_stop_0
> Aug 20 13:08:45 [107884] 001store01a cib: info:
> cib_process_request: Forwarding cib_modify operation for section status to
> all (origin=local/crmd/2453)
> Aug 20 17:08:45 [107886] 001store01a lrmd: info: log_execute:
> executing ‑ rsc:p_azip_ftpclust01 action:stop call_id:362
> Aug 20 13:08:45 [107884] 001store01a cib: info: cib_perform_op:
> Diff: ‑‑‑ 0.30.6 2
> Aug 20 13:08:45 [107884] 001store01a cib: info: cib_perform_op:
> Diff: +++ 0.30.7 (null)
>
> [sig]
More information about the Users
mailing list