Re: [ClusterLabs] Ugrading Ubuntu 14.04 to 16.04 with corosync/pacemaker failed

2020-02-20 Thread Rasca Gmelch
e 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/

Re: [ClusterLabs] Ugrading Ubuntu 14.04 to 16.04 with corosync/pacemaker failed

2020-02-20 Thread Rasca Gmelch
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

[ClusterLabs] Ugrading Ubuntu 14.04 to 16.04 with corosync/pacemaker failed

2020-02-19 Thread Rasca
, 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://lists.clusterlabs.org/mailman/listinfo

Re: [ClusterLabs] Q: What is the default default-resource-stickiness? ; -)

2018-09-03 Thread RaSca
he 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 move back or

Re: [ClusterLabs] HAProxy resource agent

2018-04-13 Thread RaSca
ismitch/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.org http://www

Re: [ClusterLabs] Pacemaker kill does not cause node fault ???

2017-02-03 Thread RaSca
ailure Looking at [1] it is explained: systemd restarts immediately the process if it ends for some unexpected reason (like a forced kill). [1] https://www.freedesktop.org/software/systemd/man/systemd.service.html -- RaSca ra...@miamammausalinux.org _

Re: [ClusterLabs] Simple Clarification's regarding pacemaker

2016-04-26 Thread RaSca
, > 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 lot I mean a LOT).

Re: [ClusterLabs] kvm live migration, resource moving

2016-02-04 Thread RaSca
or 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 VirtualDo

Re: [ClusterLabs] kvm live migration, resource moving

2016-02-03 Thread RaSca
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