users
Thread
Date
Earlier messages
Later messages
Messages by Thread
[ClusterLabs] Postgres clone resource does not get "notice" events
vitaly
Re: [ClusterLabs] Postgres clone resource does not get "notice" events
vitaly
Re: [ClusterLabs] Postgres clone resource does not get "notice" events
Reid Wahl
Re: [ClusterLabs] Postgres clone resource does not get "notice" events
Reid Wahl
Re: [ClusterLabs] Postgres clone resource does not get "notice" events
vitaly
Re: [ClusterLabs] Postgres clone resource does not get "notice" events
Reid Wahl
Re: [ClusterLabs] Postgres clone resource does not get "notice" events
vitaly
Re: [ClusterLabs] Postgres clone resource does not get "notice" events
Reid Wahl
Re: [ClusterLabs] Postgres clone resource does not get "notice" events
vitaly via Users
Re: [ClusterLabs] Postgres clone resource does not get "notice" events
Reid Wahl
Re: [ClusterLabs] Postgres clone resource does not get "notice" events
vitaly
Re: [ClusterLabs] corosync not starting
Christine caulfield
Re: [ClusterLabs] corosync not starting
Sridhar K
[ClusterLabs] FYI: one more regression introduced in Pacemaker 2.1.3
Ken Gaillot
Re: [ClusterLabs] FYI: one more regression introduced in Pacemaker 2.1.3
Ken Gaillot
[ClusterLabs] Antw: [EXT] FYI: one more regression introduced in Pacemaker 2.1.3
Ulrich Windl
[ClusterLabs] modified RA can't be used
Lentes, Bernd
Re: [ClusterLabs] modified RA can't be used
Oyvind Albrigtsen
Re: [ClusterLabs] modified RA can't be used
Lentes, Bernd
Re: [ClusterLabs] modified RA can't be used
Ken Gaillot
Re: [ClusterLabs] modified RA can't be used
Lentes, Bernd
[ClusterLabs] Antw: [EXT] modified RA can't be used
Ulrich Windl
[ClusterLabs] pcs 0.11.3 released
Tomas Jelinek
[ClusterLabs] pcs 0.10.14 released
Tomas Jelinek
[ClusterLabs] pacemaker-fenced[11637]: warning: Can't create a sane reply
Priyanka Balotra
Re: [ClusterLabs] pacemaker-fenced[11637]: warning: Can't create a sane reply
Klaus Wenninger
Re: [ClusterLabs] pacemaker-fenced[11637]: warning: Can't create a sane reply
Priyanka Balotra
Re: [ClusterLabs] pacemaker-fenced[11637]: warning: Can't create a sane reply
Ken Gaillot
[ClusterLabs] Question regarding the security of corosync
Mario Freytag
Re: [ClusterLabs] Question regarding the security of corosync
Jan Friesse
Re: [ClusterLabs] Question regarding the security of corosync
Antony Stone
Re: [ClusterLabs] Question regarding the security of corosync
Andrei Borzenkov
Re: [ClusterLabs] Question regarding the security of corosync
Jan Friesse
[ClusterLabs] Antw: [EXT] Question regarding the security of corosync
Ulrich Windl
[ClusterLabs] related to fencing in general , docker containers
Sridhar K
Re: [ClusterLabs] related to fencing in general , docker containers
Andrei Borzenkov
Re: [ClusterLabs] related to fencing in general , docker containers
Ken Gaillot
Re: [ClusterLabs] related to fencing in general , docker containers
Sridhar K
Re: [ClusterLabs] related to fencing in general , docker containers
Andrei Borzenkov
[ClusterLabs] Antw: [EXT] related to fencing in general , docker containers
Ulrich Windl
Re: [ClusterLabs] Antw: [EXT] related to fencing in general , docker containers
Sridhar K
[ClusterLabs] Pacemaker 2.1.4 final release now available
Ken Gaillot
[ClusterLabs] Why not retry a monitor (pacemaker-execd) that got a segmentation fault?
Ulrich Windl
Re: [ClusterLabs] Why not retry a monitor (pacemaker-execd) that got a segmentation fault?
Ken Gaillot
[ClusterLabs] Antw: [EXT] Re: Why not retry a monitor (pacemaker‑execd) that got a segmentation fault?
Ulrich Windl
Re: [ClusterLabs] Antw: [EXT] Re: Why not retry a monitor (pacemaker‑execd) that got a segmentation fault?
Ken Gaillot
[ClusterLabs] Antw: [EXT] Re: Why not retry a monitor (pacemaker‑execd) that got a segmentation fault?
Ulrich Windl
Re: [ClusterLabs] Antw: [EXT] Re: Why not retry a monitor (pacemaker‑execd) that got a segmentation fault?
Klaus Wenninger
[ClusterLabs] Antw: Re: Antw: [EXT] Re: Why not retry a monitor (pacemaker‑execd) that got a segmentation fault?
Ulrich Windl
Re: [ClusterLabs] Antw: Re: Antw: [EXT] Re: Why not retry a monitor (pacemaker‑execd) that got a segmentation fault?
Klaus Wenninger
[ClusterLabs] Antw: Re: Antw: Re: Antw: [EXT] Re: Why not retry a monitor (pacemaker‑execd) that got a segmentation fault?
Ulrich Windl
Re: [ClusterLabs] Antw: Re: Antw: Re: Antw: [EXT] Re: Why not retry a monitor (pacemaker‑execd) that got a segmentation fault?
Klaus Wenninger
[ClusterLabs] crm status shows CURRENT DC as None
Priyanka Balotra
[ClusterLabs] Antw: [EXT] crm status shows CURRENT DC as None
Ulrich Windl via Users
Re: [ClusterLabs] crm status shows CURRENT DC as None
Ken Gaillot
Re: [ClusterLabs] Required guidance w.r.t pacemaker
Andrei Borzenkov
Re: [ClusterLabs] Required guidance w.r.t pacemaker
Sridhar K
Re: [ClusterLabs] Required guidance w.r.t pacemaker
Andrei Borzenkov
Re: [ClusterLabs] Required guidance w.r.t pacemaker
Ken Gaillot
Re: [ClusterLabs] Required guidance w.r.t pacemaker
Andrei Borzenkov
Re: [ClusterLabs] Required guidance w.r.t pacemaker
Sridhar K
Re: [ClusterLabs] Required guidance w.r.t pacemaker
Ken Gaillot
Re: [ClusterLabs] Required guidance w.r.t pacemaker
Sridhar K
[ClusterLabs] Fwd: ANNOUNCE: Linux Distributed Lock Manager Viewer
Andrew Price
[ClusterLabs] fencing configuration
Zoran Bošnjak
Re: [ClusterLabs] fencing configuration
Klaus Wenninger
Re: [ClusterLabs] fencing configuration
Andrei Borzenkov
[ClusterLabs] Antw: [EXT] fencing configuration
Ulrich Windl
Re: [ClusterLabs] fencing configuration
Andrei Borzenkov
[ClusterLabs] Pacemaker 2.1.4-rc1 now available
Ken Gaillot
[ClusterLabs] Pacemaker 2.1.3 release has regression, 2.1.4 coming soon
Ken Gaillot
[ClusterLabs] normal reboot with active sbd does not work
Zoran Bošnjak
[ClusterLabs] Antw: [EXT] normal reboot with active sbd does not work
Ulrich Windl
Re: [ClusterLabs] Antw: [EXT] normal reboot with active sbd does not work
Zoran Bošnjak
[ClusterLabs] Antw: Re: Antw: [EXT] normal reboot with active sbd does not work
Ulrich Windl
Re: [ClusterLabs] normal reboot with active sbd does not work
Klaus Wenninger
Re: [ClusterLabs] normal reboot with active sbd does not work
Klaus Wenninger
[ClusterLabs] Antw: [EXT] Re: normal reboot with active sbd does not work
Ulrich Windl
Re: [ClusterLabs] normal reboot with active sbd does not work
Andrei Borzenkov
Re: [ClusterLabs] normal reboot with active sbd does not work
Zoran Bošnjak
Re: [ClusterLabs] normal reboot with active sbd does not work
Klaus Wenninger
Re: [ClusterLabs] normal reboot with active sbd does not work
Zoran Bošnjak
Re: [ClusterLabs] normal reboot with active sbd does not work
Andrei Borzenkov
[ClusterLabs] Antw: [EXT] Re: normal reboot with active sbd does not work
Ulrich Windl
Re: [ClusterLabs] Antw: [EXT] Re: normal reboot with active sbd does not work
Klaus Wenninger
[ClusterLabs] Q: "Multiple attributes match name=target-role"
Ulrich Windl
Re: [ClusterLabs] Q: "Multiple attributes match name=target-role"
Xin Liang via Users
Re: [ClusterLabs] Q: "Multiple attributes match name=target-role"
Xin Liang via Users
[ClusterLabs] Pacemaker 2.1.3 final release now available
Ken Gaillot
[ClusterLabs] What's the number in "Servant pcmk is outdated (age: 682915)"
Ulrich Windl
Re: [ClusterLabs] What's the number in "Servant pcmk is outdated (age: 682915)"
Gao,Yan via Users
[ClusterLabs] No node name in corosync-cmapctl output
Andreas Hasenack
Re: [ClusterLabs] No node name in corosync-cmapctl output
Jan Friesse
Re: [ClusterLabs] No node name in corosync-cmapctl output
Tomas Jelinek
Re: [ClusterLabs] No node name in corosync-cmapctl output
Andreas Hasenack
Re: [ClusterLabs] No node name in corosync-cmapctl output
Jan Friesse
Re: [ClusterLabs] No node name in corosync-cmapctl output
Christine caulfield
Re: [ClusterLabs] No node name in corosync-cmapctl output
Andreas Hasenack
[ClusterLabs] Antw: [EXT] No node name in corosync‑cmapctl output
Ulrich Windl
Re: [ClusterLabs] No node name in corosync-cmapctl output
Ken Gaillot
Re: [ClusterLabs] No node name in corosync-cmapctl output
Jan Friesse
[ClusterLabs] kronosnet v1.24 released
Fabio M. Di Nitto
[ClusterLabs] More pacemaker oddities while stopping DC
Ulrich Windl
Re: [ClusterLabs] More pacemaker oddities while stopping DC
Gao,Yan via Users
Re: [ClusterLabs] More pacemaker oddities while stopping DC
Andrei Borzenkov
[ClusterLabs] What/how to clean up when bootstrapping new cluster (or: I have a phantom node)
Andreas Hasenack
Re: [ClusterLabs] What/how to clean up when bootstrapping new cluster (or: I have a phantom node)
Ken Gaillot
[ClusterLabs] Antw: [EXT] What/how to clean up when bootstrapping new cluster (or: I have a phantom node)
Ulrich Windl
Re: [ClusterLabs] Antw: [EXT] What/how to clean up when bootstrapping new cluster (or: I have a phantom node)
Andreas Hasenack
[ClusterLabs] corosync-cfgtool -s shows all links not connected for one particular node
Dirk Gassen
Re: [ClusterLabs] corosync-cfgtool -s shows all links not connected for one particular node
Jan Friesse
[ClusterLabs] Cluster unable to find back together
Leditzky, Fabian via Users
[ClusterLabs] Antw: [EXT] Cluster unable to find back together
Ulrich Windl
Re: [ClusterLabs] Cluster unable to find back together
Jan Friesse
Re: [ClusterLabs] Cluster unable to find back together
Ken Gaillot
[ClusterLabs] Antw: [EXT] Re: Cluster unable to find back together
Ulrich Windl
Re: [ClusterLabs] Antw: [EXT] Re: Cluster unable to find back together
Klaus Wenninger
[ClusterLabs] Antw: Re: Antw: [EXT] Re: Cluster unable to find back together
Ulrich Windl
[ClusterLabs] Pacemaker 2.1.3-rc2 now available
Ken Gaillot
[ClusterLabs] how does the VirtualDomain RA know with which options it's called ?
Lentes, Bernd
Re: [ClusterLabs] how does the VirtualDomain RA know with which options it's called ?
Andrei Borzenkov
[ClusterLabs] Antw: [EXT] how does the VirtualDomain RA know with which options it's called ?
Ulrich Windl
[ClusterLabs] Q: How to clean up a failed fencing operation?
Ulrich Windl
Re: [ClusterLabs] Q: How to clean up a failed fencing operation?
Reid Wahl
[ClusterLabs] Antw: [EXT] Re: Q: How to clean up a failed fencing operation?
Ulrich Windl
Re: [ClusterLabs] Antw: [EXT] Re: Q: How to clean up a failed fencing operation?
Klaus Wenninger
[ClusterLabs] Antw: Re: Antw: [EXT] Re: Q: How to clean up a failed fencing operation?
Ulrich Windl
Re: [ClusterLabs] Antw: Re: Antw: [EXT] Re: Q: How to clean up a failed fencing operation?
Klaus Wenninger
[ClusterLabs] Help understanding recover of promotable resource after a "pcs cluster stop --all"
Salatiel Filho
Re: [ClusterLabs] Help understanding recover of promotable resource after a "pcs cluster stop --all"
Ken Gaillot
Re: [ClusterLabs] Help understanding recover of promotable resource after a "pcs cluster stop --all"
Salatiel Filho
Re: [ClusterLabs] Help understanding recover of promotable resource after a "pcs cluster stop --all"
Ken Gaillot
Re: [ClusterLabs] Help understanding recover of promotable resource after a "pcs cluster stop --all"
Strahil Nikolov via Users
[ClusterLabs] Antw: [EXT] Re: Help understanding recover of promotable resource after a "pcs cluster stop ‑‑all"
Ulrich Windl
Re: [ClusterLabs] Help understanding recover of promotable resource after a "pcs cluster stop --all"
Andrei Borzenkov
[ClusterLabs] Antw: [EXT] Re: Help understanding recover of promotable resource after a "pcs cluster stop ‑‑all"
Ulrich Windl
Re: [ClusterLabs] Antw: [EXT] Re: Help understanding recover of promotable resource after a "pcs cluster stop ‑‑all"
Andrei Borzenkov
[ClusterLabs] OT: Linstor/DRBD Problem
Eric Robinson
Re: [ClusterLabs] OT: Linstor/DRBD Problem
Strahil Nikolov via Users
Re: [ClusterLabs] OT: Linstor/DRBD Problem
Eric Robinson
[ClusterLabs] How many nodes redhat cluster does supports
Umar Draz
Re: [ClusterLabs] How many nodes redhat cluster does supports
Valentin Vidić via Users
Re: [ClusterLabs] How many nodes redhat cluster does supports
Ken Gaillot
Re: [ClusterLabs] How many nodes redhat cluster does supports
Umar Draz
Re: [ClusterLabs] How many nodes redhat cluster does supports
Umar Draz
[ClusterLabs] Antw: [EXT] Re: How many nodes redhat cluster does supports
Ulrich Windl
[ClusterLabs] gfs2 in cloud environments [was: Re: How many nodes redhat cluster does supports]
Andrew Price
Re: [ClusterLabs] How many nodes redhat cluster does supports
Strahil Nikolov via Users
[ClusterLabs] OCF_TIMEOUT - Does it recover by itself?
Salatiel Filho
Re: [ClusterLabs] OCF_TIMEOUT - Does it recover by itself?
Ken Gaillot
Re: [ClusterLabs] OCF_TIMEOUT - Does it recover by itself?
Hayden, Robert via Users
Re: [ClusterLabs] OCF_TIMEOUT - Does it recover by itself?
Strahil Nikolov via Users
[ClusterLabs] Antw: [EXT] Re: OCF_TIMEOUT ‑ Does it recover by itself?
Ulrich Windl
Re: [ClusterLabs] Antw: [EXT] Re: OCF_TIMEOUT ‑ Does it recover by itself?
Ken Gaillot
[ClusterLabs] Running Arbitrator on Kubernetes Setup
Gitesh Hulke
[ClusterLabs] Pacemaker 2.1.3-rc1 now available
Ken Gaillot
[ClusterLabs] Can a two node cluster start resources if only one node is booted?
john tillman
Re: [ClusterLabs] Can a two node cluster start resources if only one node is booted?
Andrei Borzenkov
Re: [ClusterLabs] Can a two node cluster start resources if only one node is booted?
john tillman
Re: [ClusterLabs] Can a two node cluster start resources if only one node is booted?
Tomas Jelinek
Re: [ClusterLabs] Can a two node cluster start resources if only one node is booted?
john tillman
Re: [ClusterLabs] Can a two node cluster start resources if only one node is booted?
Andrei Borzenkov
Re: [ClusterLabs] Can a two node cluster start resources if only one node is booted?
john tillman
Re: [ClusterLabs] Can a two node cluster start resources if only one node is booted?
Klaus Wenninger
[ClusterLabs] Antw: [EXT] Re: Can a two node cluster start resources if only one node is booted?
Ulrich Windl
Re: [ClusterLabs] Can a two node cluster start resources if only one node is booted?
Tomas Jelinek
Re: [ClusterLabs] Can a two node cluster start resources if only one node is booted?
Andrei Borzenkov
Re: [ClusterLabs] Can a two node cluster start resources if only one node is booted?
john tillman
Re: [ClusterLabs] Can a two node cluster start resources if only one node is booted?
Andrei Borzenkov
Re: [ClusterLabs] Can a two node cluster start resources if only one node is booted?
john tillman
Re: [ClusterLabs] Can a two node cluster start resources if only one node is booted?
Ken Gaillot
Re: [ClusterLabs] Can a two node cluster start resources if only one node is booted?
john tillman
[ClusterLabs] Can a two node cluster start with only one node?
john tillman
Re: [ClusterLabs] Can a two node cluster start with only one node?
Ken Gaillot
Re: [ClusterLabs] Can a two node cluster start with only one node?
john tillman
[ClusterLabs] I_DC_TIMEOUT and node fenced when it joins the cluster
vitaly
Re: [ClusterLabs] I_DC_TIMEOUT and node fenced when it joins the cluster
Strahil Nikolov via Users
[ClusterLabs] Antw: [EXT] I_DC_TIMEOUT and node fenced when it joins the cluster
Ulrich Windl
[ClusterLabs] Coming in 2.1.3: node health monitoring improvements
Ken Gaillot
[ClusterLabs] Antw: [EXT] Coming in 2.1.3: node health monitoring improvements
Ulrich Windl
Re: [ClusterLabs] Antw: [EXT] Coming in 2.1.3: node health monitoring improvements
Ken Gaillot
[ClusterLabs] Antw: Re: Antw: [EXT] Coming in 2.1.3: node health monitoring improvements
Ulrich Windl
Re: [ClusterLabs] Antw: Re: Antw: [EXT] Coming in 2.1.3: node health monitoring improvements
Klaus Wenninger
[ClusterLabs] colocation/order for cloned resource + group being ignored
Salatiel Filho
Re: [ClusterLabs] colocation/order for cloned resource + group being ignored
Andrei Borzenkov
Re: [ClusterLabs] colocation/order for cloned resource + group being ignored
Salatiel Filho
[ClusterLabs] Coming in Pacemaker 2.1.3: multiple-active=stop_unexpected
Ken Gaillot
Re: [ClusterLabs] Coming in Pacemaker 2.1.3: multiple-active=stop_unexpected
Andrei Borzenkov
[ClusterLabs] Antw: [EXT] Re: Coming in Pacemaker 2.1.3: multiple‑active=stop_unexpected
Ulrich Windl
Re: [ClusterLabs] Antw: [EXT] Re: Coming in Pacemaker 2.1.3: multiple‑active=stop_unexpected
Ken Gaillot
[ClusterLabs] Antw: [EXT] Coming in Pacemaker 2.1.3: multiple‑active=stop_unexpected
Ulrich Windl
[ClusterLabs] Restarting parent of ordered clone resources on specific node causes restart of all resources in the ordering constraint on all nodes of the cluster
ChittaNagaraj, Raghav
[ClusterLabs] Antw: [EXT] Restarting parent of ordered clone resources on specific node causes restart of all resources in the ordering constraint on all nodes of the cluster
Ulrich Windl
Re: [ClusterLabs] Restarting parent of ordered clone resources on specific node causes restart of all resources in the ordering constraint on all nodes of the cluster
Strahil Nikolov via Users
Re: [ClusterLabs] Restarting parent of ordered clone resources on specific node causes restart of all resources in the ordering constraint on all nodes of the cluster
ChittaNagaraj, Raghav
Re: [ClusterLabs] Restarting parent of ordered clone resources on specific node causes restart of all resources in the ordering constraint on all nodes of the cluster
ChittaNagaraj, Raghav
[ClusterLabs] SAP HANA monitor fails - Error performing operation: No such device or address
Aj Revelino
[ClusterLabs] Antw: [EXT] SAP HANA monitor fails ‑ Error performing operation: No such device or address
Ulrich Windl
Re: [ClusterLabs] Antw: [EXT] SAP HANA monitor fails ‑ Error performing operation: No such device or address
Aj Revelino
Re: [ClusterLabs] Antw: [EXT] SAP HANA monitor fails ‑ Error performing operation: No such device or address
Strahil Nikolov via Users
Earlier messages
Later messages