Hello,
I'm experiencing issue with corosync/pacemaker running on Debian Buster.
Cluster has three nodes running in VMWare virtual machine and the
cluster fails when VEEAM backups the virtual machine (I know it's doing
bad things, like freezing completely the VM for a few minutes to make
Hello,
I'm struggling to understand if it's possible to create some kind of
constraint to avoid two different resources to be running on the same host.
Basically, I'd like to have floating IP "1" and floating IP "2" always
being assigned to DIFFERENT nodes.
Is that something possible ?
On 9/27/23 16:02, Ken Gaillot wrote:
On Wed, 2023-09-27 at 15:42 +0300, Andrei Borzenkov wrote:
On Wed, Sep 27, 2023 at 3:21 PM Adam Cecile
wrote:
Hello,
I'm struggling to understand if it's possible to create some kind
of constraint to avoid two different resources to be running on the
same
On 2/16/23 20:54, Ken Gaillot wrote:
On Thu, 2023-02-16 at 11:13 +0100, Adam Cecile wrote:
On 2/16/23 07:57, Ulrich Windl wrote:
Adam Cecile schrieb am 15.02.2023 um
10:49 in
Nachricht
:
Hello,
Just had some issue with unexpected server behavior after reboot.
This
node was powered off, so
On 2/15/23 12:16, Andrei Borzenkov wrote:
On Wed, Feb 15, 2023 at 12:49 PM Adam Cecile wrote:
Hello,
Just had some issue with unexpected server behavior after reboot. This node was
powered off, so cluster was running fine with this tomcat9 resource running on
a different machine.
After
On 2/16/23 07:57, Ulrich Windl wrote:
Adam Cecile schrieb am 15.02.2023 um 10:49 in
Nachricht
:
Hello,
Just had some issue with unexpected server behavior after reboot. This
node was powered off, so cluster was running fine with this tomcat9
resource running on a different machine.
After
Hello,
I might be stupid but I'm completely stuck with this requirement. We
just figured out DNSMasq proxy is not working correctly after shared IP
address is moved from one host to another because it does not listen on
the new address.
My need is to issue a reload statement to DNSMasq to
Hello,
Just had some issue with unexpected server behavior after reboot. This
node was powered off, so cluster was running fine with this tomcat9
resource running on a different machine.
After powering on this node again, it briefly started tomcat before
joining the cluster and decided to
Hello,
Crm_mon show these errors on my cluster, while everything is working as
expected:
Failed Resource Actions:
* Default-Public-IPv4-Is-Default-Src probe on gw-3.domain returned
'error' ([findif] failed) at Wed Feb 7 08:00:22 2024 after 49ms
* Default-Public-IPv4-Is-Default-Src
On 2/7/24 09:49, Oyvind Albrigtsen wrote:
On 07/02/24 09:35 +0100, Adam Cecile wrote:
Hello,
Crm_mon show these errors on my cluster, while everything is working
as expected:
Failed Resource Actions:
* Default-Public-IPv4-Is-Default-Src probe on gw-3.domain returned
'error' ([findif
On 1/17/24 16:33, Ken Gaillot wrote:
On Wed, 2024-01-17 at 14:23 +0100, Adam Cécile wrote:
Hello,
I'm trying to achieve the following setup with 3 hosts:
* One master gets a shared IP, then remove default gw, add another
gw,
start a service
* Two slaves should have none of them but add a
11 matches
Mail list logo
