[Pacemaker] Corosync starts after system reboot but fails to load/start any resources
Parshvi
parshvi.17 at gmail.com
Mon May 28 14:09:40 UTC 2012
Parshvi <parshvi.17 at ...> writes:
>
> Hi,
>
> Observations:
> -> When Node-2 is up after reboot, the following issues are observed:
>
> 1) NONE of the resources start on Node-2: The 5 non-sticky resources do not
> fail-back on Node-2.
> 2) The slave instance is not started on Node-2.
>
> The system is rebooted at 8:38 a.m.
> A restart of corosync engine is initiated at 9:50 a.m. which fails to fix the
> issue.
> At 10:24 a.m. the system is rebooted again. This time the resources are
started
> normally.
>
> crm_mon on Node-1: shows Node-2 as offline.
> crm_mon on Node-2: shows Node-1 as online.
>
> An hb_report could not be captured. Although I have logs (corosync logs + sys
> logs)and pe-input files. Where can I publish them ? pastebin seems to be
blocked
>
_______________________________________________
I have shared a tarball of:
1) Node-1 and Node-2's corosync logs and pengine-inputs. PLease follow link
below:
http://www.qfpost.com/file/d?g=Y6kHRlpX7
More information about the Pacemaker
mailing list