[Pacemaker] cluster deadlock/malfunctioning
Raoul Bhatia [IPAX]
r.bhatia at ipax.at
Fri Nov 14 15:25:41 UTC 2008
dear list,
i again encounter my cluster malfunctioning.
i upgraded my configuration to use pam-ldap and libnss-ldap, which
did not work out of the box.
pacemaker tried to recover some errors and then stonithed both
hosts.
i now have only got:
> Node: wc01 (31de4ab3-2d05-476e-8f9a-627ad6cd94ca): online
> Node: wc02 (f36760d8-d84a-46b2-b452-4c8cac8b3396): online
>
> Clone Set: clone_nfs-common
> Resource Group: group_nfs-common:0
> nfs-common:0 (lsb:nfs-common): Started wc02
> Resource Group: group_nfs-common:1
> nfs-common:1 (lsb:nfs-common): Started wc01
> Clone Set: DoFencing
> stonith_rackpdu:0 (stonith:external/rackpdu): Started wc02
> stonith_rackpdu:1 (stonith:external/rackpdu): Started wc01
and pacemaker seems happy :)
(please note, that i normally have several groups, clones and
master/slave resources active.
i took a look at pe-warn-12143.bz2 but do not know how to interpret the
three different threads i see in the corresponding .dot file.
can any1 explain how i may debug such a deadlock?
cheers,
raoul
--
____________________________________________________________________
DI (FH) Raoul Bhatia M.Sc. email. r.bhatia at ipax.at
Technischer Leiter
IPAX - Aloy Bhatia Hava OEG web. http://www.ipax.at
Barawitzkagasse 10/2/2/11 email. office at ipax.at
1190 Wien tel. +43 1 3670030
FN 277995t HG Wien fax. +43 1 3670030 15
____________________________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pacemaker_lockup.tar.gz
Type: application/x-gzip
Size: 73880 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20081114/c32babfe/attachment-0001.bin>
More information about the Pacemaker
mailing list