The error does not seems to be related to the topology, it's a matter of
something else. Like permissions or network connectivity.
You need to check the logs to understand the reason of the failure.
Bye,
--
RaSca
Mia Mamma Usa Linux: Niente è impossibile da capire, se lo spieghi ben
It is not clear to me why you need to do things by hand. Why are you
using virsh once you could do a resource move within the cluster?
--
RaSca
Mia Mamma Usa Linux: Niente è impossibile da capire, se lo spieghi bene!
ra...@miamammausalinux.org
http://www.miamammausalinux.org
Il giorno 3/2/2016
The VirtualDomain resource agent supports live migration as well as
virsh command, that's because it actually USE virsh, so again, why
aren't you using directly VirtualDomain?
--
RaSca
Mia Mamma Usa Linux: Niente è impossibile da capire, se lo spieghi bene!
ra...@miamammausalinu
details on guest migration.
Hope this helps,
--
RaSca
Mia Mamma Usa Linux: Niente è impossibile da capire, se lo spieghi bene!
ra...@miamammausalinux.org
http://www.miamammausalinux.org
Il giorno 4/2/2016 12:09:19, Kyle O'Donnell ha scritto:
> I explicitly stated I was using the Virt
, specifying a time when migrating.
--
RaSca
Mia Mamma Usa Linux: Niente è impossibile da capire, se lo spieghi bene!
ra...@miamammausalinux.org
http://www.miamammausalinux.org
Il giorno 4/2/2016 14:52:52, Kyle O'Donnell ha scritto:
> you mean instead of inf: ##: I thought the number wa
ion beings ,
> When an election is done
> Thanks
> Aravind
Just in the logs, but you can setup something like email notification
for each action. I don't know how things are now, but in the past those
were a lot of mail (and when I say a
>> pacemaker".
>
> What exactly is "quickly enough"?
What Ken is saying is that Pacemaker, as a service managed by systemd,
have in its service definition file
(/usr/lib/systemd/system/pacemaker.service) this option:
Restart=on-failure
Looking at [1] it is explained: s
ontent.com/thisismitch/cluster-agents/master/haproxy
> I can always use the systemd service RA
> What is your recommendation?
Systemd is fine for a service like haproxy, go for it!
--
RaSca
Mia Mamma Usa Linux: Niente è impossibile da capire, se lo spieghi bene!
ra...@miamammausalinux
the node it was running on:
1 - RES1 is running on NODE1
2 - NODE1 fails
3 - RES1 move to NODE2
4 - NODE1 resurrect
5 - RES1 go back to NODE1
with a default-resource-stickiness of INFINITY you'll not get step 5,
with any other value the cluster will deal with node weights while
deciding to mo
status=Not
installed, exitreason='none',
last-rc-change='Wed Feb 19 14:13:20 2020', queued=0ms, exec=1ms
[..]
Any suggestions, ideas? Is the a nice HowTo for this upgrade situation?
Regards,
Rasca
___
Manage your subscription:
https:
Am 19.02.20 um 19:20 schrieb Strahil Nikolov:
> On February 19, 2020 6:31:19 PM GMT+02:00, Rasca
> wrote:
>> Hi,
>>
>> we run a 2-system cluster for Samba with Ubuntu 14.04 and Samba,
>> Corosync and Pacemaker from the Ubuntu repos. We wanted to update
>> to
14.04.
>>>> Any suggestions, ideas? Is the a nice HowTo for this upgrade situation?
>
> Yes
>
> 1) stop what you are doing, do it from the ground.
>
> 2) Take 1 of the servers and configure it appropriately using the proper
> resource agent. Before configuring the resources, make sure the rings
> are in good shape and the cluster has the proper votes.
Thanks for all these notes and cents but I'm too less experienced
to do this while the production node is online.
I've to do more tests with my two virtualbox VMs to become more
familuar with the corosync/pacemaker setup.
Regards,
Rasca
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
12 matches
Mail list logo
