July 2019 Archives by author

• Messages sorted by: [ thread ] [ subject ] [ date ]
• More info on this list...

Starting: Mon Jul 1 05:13:49 EDT 2019
Ending: Wed Jul 31 02:26:26 EDT 2019
Messages: 169

• [ClusterLabs] Resource won't start, crm_resource -Y does not help   Oyvind Albrigtsen
• [ClusterLabs] Reusing resource set in multiple constraints   Vladislav Bogdanov
• [ClusterLabs] Problems with master/slave failovers   Andrei Borzenkov
• [ClusterLabs] Problems with master/slave failovers   Andrei Borzenkov
• [ClusterLabs] "node is unclean" leads to gratuitous reboot   Andrei Borzenkov
• [ClusterLabs] Fwd: Postgres pacemaker cluster failure   Andrei Borzenkov
• [ClusterLabs] Fwd: Postgres pacemaker cluster failure   Andrei Borzenkov
• [ClusterLabs] Fwd: Postgres pacemaker cluster failure   Andrei Borzenkov
• [ClusterLabs] [EXTERNAL] Re: "node is unclean" leads to gratuitous reboot   Andrei Borzenkov
• [ClusterLabs] Antw: Interacting with Pacemaker from my code   Andrei Borzenkov
• [ClusterLabs] Antw: Interacting with Pacemaker from my code   Andrei Borzenkov
• [ClusterLabs] Feedback wanted: Node reaction to fabric fencing   Andrei Borzenkov
• [ClusterLabs] Reusing resource set in multiple constraints   Andrei Borzenkov
• [ClusterLabs] Reusing resource set in multiple constraints   Andrei Borzenkov
• [ClusterLabs] corosync.service (and sbd.service) are not stopper on pacemaker shutdown when corosync-qdevice is used   Andrei Borzenkov
• [ClusterLabs] Node reset on shutdown by SBD watchdog with corosync-qdevice   Andrei Borzenkov
• [ClusterLabs] corosync.service (and sbd.service) are not stopper on pacemaker shutdown when corosync-qdevice is used   Andrei Borzenkov
• [ClusterLabs] How to avoid starting resource where another resource has started   Digimer
• [ClusterLabs] [EXTERNAL] Re: "node is unclean" leads to gratuitous reboot   Lars Ellenberg
• [ClusterLabs] 2 nodes split brain with token timeout   Jan Friesse
• [ClusterLabs] Corosync 3.x and Pacemaker 2.x supported OS versions   Jan Friesse
• [ClusterLabs] corosync.service (and sbd.service) are not stopper on pacemaker shutdown when corosync-qdevice is used   Jan Friesse
• [ClusterLabs] Node reset on shutdown by SBD watchdog with corosync-qdevice   Jan Friesse
• [ClusterLabs] Corosync 2.4.5 is available at corosync.org!   Jan Friesse
• [ClusterLabs] Problems with master/slave failovers   Ken Gaillot
• [ClusterLabs] Problems with master/slave failovers   Ken Gaillot
• [ClusterLabs] Problems with master/slave failovers   Ken Gaillot
• [ClusterLabs] two virtual domains start and stop every 15 minutes   Ken Gaillot
• [ClusterLabs] two virtual domains start and stop every 15 minutes   Ken Gaillot
• [ClusterLabs] colocation - but do not stop resources on failure   Ken Gaillot
• [ClusterLabs] "node is unclean" leads to gratuitous reboot   Ken Gaillot
• [ClusterLabs] I have a question.   Ken Gaillot
• [ClusterLabs] colocation - but do not stop resources on failure   Ken Gaillot
• [ClusterLabs] failed resource resurection - failcount/cleanup etc ?   Ken Gaillot
• [ClusterLabs] failed resource resurection - failcount/cleanup etc ?   Ken Gaillot
• [ClusterLabs] failed resource resurection - failcount/cleanup etc ?   Ken Gaillot
• [ClusterLabs] pacemaker geo redundancy - 2 nodes   Ken Gaillot
• [ClusterLabs] resource location preference vs utilization   Ken Gaillot
• [ClusterLabs] Antw: Interacting with Pacemaker from my code   Ken Gaillot
• [ClusterLabs] pacemaker alerts list   Ken Gaillot
• [ClusterLabs] Antw: Re: Resource won't start, crm_resource -Y does not help   Ken Gaillot
• [ClusterLabs] [ClusterLabs Developers] pacemaker geo redundancy - 2 nodes   Ken Gaillot
• [ClusterLabs] Antw: Re: Antw: Re: Resource won't start, crm_resource -Y does not help   Ken Gaillot
• [ClusterLabs] On the semantics of ocf_exit_reason()   Ken Gaillot
• [ClusterLabs] Which shell definitions to include?   Ken Gaillot
• [ClusterLabs] 2 nodes split brain with token timeout   Ken Gaillot
• [ClusterLabs] Feedback wanted: Node reaction to fabric fencing   Ken Gaillot
• [ClusterLabs] Adding HAProxy as a Resource   Ken Gaillot
• [ClusterLabs] Feedback wanted: Node reaction to fabric fencing   Ken Gaillot
• [ClusterLabs] Reusing resource set in multiple constraints   Ken Gaillot
• [ClusterLabs] Strange behaviour of group resource   Ken Gaillot
• [ClusterLabs] Adding HAProxy as a Resource   Ken Gaillot
• [ClusterLabs] Strange behaviour of group resource   Ken Gaillot
• [ClusterLabs] Adding HAProxy as a Resource   Ken Gaillot
• [ClusterLabs] "resource cleanup" - but error message does not dissapear   Ken Gaillot
• [ClusterLabs] pacemaker alerts list   Gershman, Vladimir
• [ClusterLabs] EXTERNAL: Re: pacemaker alerts list   Gershman, Vladimir
• [ClusterLabs] Adding HAProxy as a Resource   Kristoffer Grönlund
• [ClusterLabs] Fwd: Fwd: Postgres pacemaker cluster failure   Danka Ivanovic
• [ClusterLabs] Fwd: Postgres pacemaker cluster failure   Danka Ivanovic
• [ClusterLabs] Fwd: Postgres pacemaker cluster failure   Danka Ivanović
• [ClusterLabs] Adding HAProxy as a Resource   Somanath Jeeva
• [ClusterLabs] Adding HAProxy as a Resource   Somanath Jeeva
• [ClusterLabs] Adding HAProxy as a Resource   Somanath Jeeva
• [ClusterLabs] Adding HAProxy as a Resource   Somanath Jeeva
• [ClusterLabs] Corosync 3.x and Pacemaker 2.x supported OS versions   Somanath Jeeva
• [ClusterLabs] Adding HAProxy as a Resource   Somanath Jeeva
• [ClusterLabs] "node is unclean" leads to gratuitous reboot   Tomas Jelinek
• [ClusterLabs] [EXTERNAL] What's the best practice to scale-out/increase the cluster size?   Tomas Jelinek
• [ClusterLabs] Adding HAProxy as a Resource   Tomas Jelinek
• [ClusterLabs] Adding HAProxy as a Resource   Tomas Jelinek
• [ClusterLabs] two virtual domains start and stop every 15 minutes   Lentes, Bernd
• [ClusterLabs] tracing stop of clvm resource - but only having one logfile   Lentes, Bernd
• [ClusterLabs] "resource cleanup" - but error message does not dissapear   Lentes, Bernd
• [ClusterLabs] "resource cleanup" - but error message does not dissapear   Lentes, Bernd
• [ClusterLabs] Strange behaviour of group resource   Dileep V Nair
• [ClusterLabs] Strange behaviour of group resource   Dileep V Nair
• [ClusterLabs] Interacting with Pacemaker from my code   Nishant Nakate
• [ClusterLabs] Antw: Interacting with Pacemaker from my code   Nishant Nakate
• [ClusterLabs] Antw: Interacting with Pacemaker from my code   Nishant Nakate
• [ClusterLabs] Feedback wanted: Node reaction to fabric fencing   Ondrej
• [ClusterLabs] Add Resource Environment Variables   Patrick
• [ClusterLabs] Antw: Re: Two node cluster goes into split brain scenario during CPU intensive tasks   Jan Pokorný
• [ClusterLabs] Strange monitor return code log for LSB resource   Jan Pokorný
• [ClusterLabs] Strange monitor return code log for LSB resource   Jan Pokorný
• [ClusterLabs] Question about associating with ClusterLabs wrt. a local community (Was: I have a question.)   Jan Pokorný
• [ClusterLabs] pacemaker alerts list   Jan Pokorný
• [ClusterLabs] [Question] About clufter's Corosync 3 support   Jan Pokorný
• [ClusterLabs] Which shell definitions to include?   Jan Pokorný
• [ClusterLabs] Feedback wanted: Node reaction to fabric fencing   Jan Pokorný
• [ClusterLabs] 2 nodes split brain with token timeout   Jean-Jacques Pons
• [ClusterLabs] 2 nodes split brain with token timeout   Jean-Jacques Pons
• [ClusterLabs] "node is unclean" leads to gratuitous reboot   Michael Powell
• [ClusterLabs] [EXTERNAL] Re: "node is unclean" leads to gratuitous reboot   Michael Powell
• [ClusterLabs] [EXTERNAL] What's the best practice to scale-out/increase the cluster size? (was: "node is unclean" leads to gratuitous reboot)   Michael Powell
• [ClusterLabs] PAF fails to promote slave: Can not get current node LSN location   Jehan-Guillaume de Rorthais
• [ClusterLabs] PAF fails to promote slave: Can not get current node LSN location   Jehan-Guillaume de Rorthais
• [ClusterLabs] PAF fails to promote slave: Can not get current node LSN location   Jehan-Guillaume de Rorthais
• [ClusterLabs] PAF fails to promote slave: Can not get current node LSN location   Jehan-Guillaume de Rorthais
• [ClusterLabs] PAF fails to promote slave: Can not get current node LSN location   Jehan-Guillaume de Rorthais
• [ClusterLabs] Fwd: Postgres pacemaker cluster failure   Jehan-Guillaume de Rorthais
• [ClusterLabs] Fwd: Postgres pacemaker cluster failure   Jehan-Guillaume de Rorthais
• [ClusterLabs] Antw: Re: Fwd: Postgres pacemaker cluster failure   Jehan-Guillaume de Rorthais
• [ClusterLabs] PAF fails to promote slave: Can not get current node LSN location   Jehan-Guillaume de Rorthais
• [ClusterLabs] Fwd: Postgres pacemaker cluster failure   Jehan-Guillaume de Rorthais
• [ClusterLabs] PAF fails to promote slave: Can not get current node LSN location   Jehan-Guillaume de Rorthais
• [ClusterLabs] Fwd: Postgres pacemaker cluster failure   Jehan-Guillaume de Rorthais
• [ClusterLabs] PAF fails to promote slave: Can not get current node LSN location   Tiemen Ruiten
• [ClusterLabs] PAF fails to promote slave: Can not get current node LSN location   Tiemen Ruiten
• [ClusterLabs] PAF fails to promote slave: Can not get current node LSN location   Tiemen Ruiten
• [ClusterLabs] PAF fails to promote slave: Can not get current node LSN location   Tiemen Ruiten
• [ClusterLabs] PAF fails to promote slave: Can not get current node LSN location   Tiemen Ruiten
• [ClusterLabs] PAF fails to promote slave: Can not get current node LSN location   Tiemen Ruiten
• [ClusterLabs] PAF fails to promote slave: Can not get current node LSN location   Tiemen Ruiten
• [ClusterLabs] Add Resource Environment Variables   Tiemen Ruiten
• [ClusterLabs] Add Resource Environment Variables   Tiemen Ruiten
• [ClusterLabs] pacemaker geo redundancy - 2 nodes   Rohit Saini
• [ClusterLabs] pacemaker geo redundancy - 2 nodes   Rohit Saini
• [ClusterLabs] pacemaker geo redundancy - 2 nodes   Rohit Saini
• [ClusterLabs] Fwd: [lca-announce] linux.conf.au 2020 - Call for Sessions and Miniconfs final week!   Tim Serong
• [ClusterLabs] Fwd: [lca-announce] linux.conf.au 2020 - Call for Sessions and Miniconfs final week!   Tim Serong
• [ClusterLabs] Problems with master/slave failovers   Harvey Shepherd
• [ClusterLabs] Problems with master/slave failovers   Harvey Shepherd
• [ClusterLabs] Strange monitor return code log for LSB resource   Harvey Shepherd
• [ClusterLabs] Problems with master/slave failovers   Harvey Shepherd
• [ClusterLabs] Stop action called after reboot and on all nodes   Thomas Singleton
• [ClusterLabs] How to avoid starting resource where another resource has started   Josep Maria Viñolas
• [ClusterLabs] How to avoid starting resource where another resource has started   Josep Maria Viñolas
• [ClusterLabs] [EXTERNAL] Re: "node is unclean" leads to gratuitous reboot   Chris Walker
• [ClusterLabs] Antw: Interacting with Pacemaker from my code   Klaus Wenninger
• [ClusterLabs] pacemaker geo redundancy - 2 nodes   Klaus Wenninger
• [ClusterLabs] Node reset on shutdown by SBD watchdog with corosync-qdevice   Klaus Wenninger
• [ClusterLabs] Stop action called after reboot and on all nodes   Klaus Wenninger
• [ClusterLabs] Antw: Re: PostgreSQL PAF failover issue   Ulrich Windl
• [ClusterLabs] Antw: Re: two virtual domains start and stop every 15 minutes   Ulrich Windl
• [ClusterLabs] Antw: Re: Two node cluster goes into split brain scenario during CPU intensive tasks   Ulrich Windl
• [ClusterLabs] Antw: Re: Two node cluster goes into split brain scenario during CPU intensive tasks   Ulrich Windl
• [ClusterLabs] Antw: Re: Two node cluster goes into split brain scenario during CPU intensive tasks   Ulrich Windl
• [ClusterLabs] Antw: Re: Two node cluster goes into split brain scenario during CPU intensive tasks   Ulrich Windl
• [ClusterLabs] Antw: Re: PCSD - High Memory Usage   Ulrich Windl
• [ClusterLabs] Antw: Re: Antw: Re: Two node cluster goes into split brain scenario during CPU intensive tasks   Ulrich Windl
• [ClusterLabs] Antw: Re: Fwd: Postgres pacemaker cluster failure   Ulrich Windl
• [ClusterLabs] Antw: resource location preference vs utilization   Ulrich Windl
• [ClusterLabs] Antw: Interacting with Pacemaker from my code   Ulrich Windl
• [ClusterLabs] Antw: Re: Antw: Interacting with Pacemaker from my code   Ulrich Windl
• [ClusterLabs] Antw: Re: Antw: Interacting with Pacemaker from my code   Ulrich Windl
• [ClusterLabs] Antw: Re: resource location preference vs utilization   Ulrich Windl
• [ClusterLabs] Resource won't start, crm_resource -Y does not help   Ulrich Windl
• [ClusterLabs] Antw: Re: Resource won't start, crm_resource -Y does not help   Ulrich Windl
• [ClusterLabs] Antw: Re: Antw: Re: Resource won't start, crm_resource -Y does not help   Ulrich Windl
• [ClusterLabs] On the semantics of ocf_exit_reason()   Ulrich Windl
• [ClusterLabs] Which shell definitions to include?   Ulrich Windl
• [ClusterLabs] Antw: Re: Which shell definitions to include?   Ulrich Windl
• [ClusterLabs] Antw: Re: Reusing resource set in multiple constraints   Ulrich Windl
• [ClusterLabs] Antw: tracing stop of clvm resource - but only having one logfile   Ulrich Windl
• [ClusterLabs] Antw: "resource cleanup" - but error message does not dissapear   Ulrich Windl
• [ClusterLabs] What's the best practice to scale-out/increase the cluster size? (was: "node is unclean" leads to gratuitous reboot)   Roger Zhou
• [ClusterLabs] Feedback wanted: Node reaction to fabric fencing   Roger Zhou
• [ClusterLabs] colocation - but do not stop resources on failure   lejeczek
• [ClusterLabs] colocation - but do not stop resources on failure   lejeczek
• [ClusterLabs] failed resource resurection - failcount/cleanup etc ?   lejeczek
• [ClusterLabs] failed resource resurection - failcount/cleanup etc ?   lejeczek
• [ClusterLabs] colocation - but do not stop resources on failure   lejeczek
• [ClusterLabs] failed resource resurection - failcount/cleanup etc ?   lejeczek
• [ClusterLabs] resource location preference vs utilization   wferi at niif.hu
• [ClusterLabs] resource location preference vs utilization   wferi at niif.hu
• [ClusterLabs] [Question] About clufter's Corosync 3 support   井上和徳
• [ClusterLabs] [Question] About clufter's Corosync 3 support   井上和徳
• [ClusterLabs] I have a question.   김동현

Last message date: Wed Jul 31 02:26:26 EDT 2019
Archived on: Wed Jul 31 02:26:29 EDT 2019

• Messages sorted by: [ thread ] [ subject ] [ date ]
• More info on this list...