On Sat, Jul 23, 2016 at 7:10 AM, Ken Gaillot wrote:
> On 07/21/2016 07:46 PM, Andrew Beekhof wrote:
What do you mean by native restart action? Systemd restart?
>>
>> Whatever the agent supports.
>
> Are you suggesting that pacemaker starting checking whether the agent
>
On Mon, Jul 25, 2016 at 11:20 AM, Ken Gaillot wrote:
> On 07/23/2016 10:14 PM, Nate Clark wrote:
>> On Sat, Jul 23, 2016 at 1:06 AM, Andrei Borzenkov
>> wrote:
>>> 23.07.2016 01:37, Nate Clark пишет:
Hello,
I am running pacemaker 1.1.13
Thanks for the suggestions.
I basically uninstalled pacemaker and ripped every single file out of the
system that had "pacemaker" in its name, then reinstalled and it is now working
fine. I had already uninstalled and re-installed a few times, but the uninstall
left some orphaned files.
--
Onlyin backports
https://wiki.debian.org/Debian-HA/ClustersFromScratch
Mit freundlichen Grüßen / Best regards
Heiko Reimer
--
Heiko Reimer
IT / Entwicklung
-
Sport-Tiedje GmbH
International Headquarters
Flensburger Str. 55
D-24837 Schleswig
Tel.: +49 -
Hi,
is "Pacemaker" available on Debian 8.1?
Regards
T.
___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users
Project Home: http://www.clusterlabs.org
Getting started:
On 25/07/16 16:27, Klaus Wenninger wrote:
> On 07/25/2016 04:56 PM, Thomas Lamprecht wrote:
>> Thanks for the fast reply :)
>>
>>
>> On 07/25/2016 03:51 PM, Christine Caulfield wrote:
>>> On 25/07/16 14:29, Thomas Lamprecht wrote:
Hi all,
I'm currently testing the new features of
Hi, everyone. You might’ve noticed a few emails from me in the last couple of
weeks that chronicle my struggle to get an HA iSCSI Target configured in AWS.
After stumbling through this setup (and struggling all the way), I think I’ve
finally gotten to the point where I’m ready to create the
On 07/25/2016 04:56 PM, Thomas Lamprecht wrote:
> Thanks for the fast reply :)
>
>
> On 07/25/2016 03:51 PM, Christine Caulfield wrote:
>> On 25/07/16 14:29, Thomas Lamprecht wrote:
>>> Hi all,
>>>
>>> I'm currently testing the new features of corosync 2.4, especially
>>> qdevices.
>>> First tests
On 25/07/16 14:51, Christine Caulfield wrote:
> On 25/07/16 14:29, Thomas Lamprecht wrote:
>> Hi all,
>>
>> I'm currently testing the new features of corosync 2.4, especially
>> qdevices.
>> First tests show quite nice results, like having quorum on a single node
>> left out of a three node
On 25/07/16 14:29, Thomas Lamprecht wrote:
> Hi all,
>
> I'm currently testing the new features of corosync 2.4, especially
> qdevices.
> First tests show quite nice results, like having quorum on a single node
> left out of a three node cluster.
>
> But what I'm a bit worrying about is what
Hi all,
I'm currently testing the new features of corosync 2.4, especially qdevices.
First tests show quite nice results, like having quorum on a single node
left out of a three node cluster.
But what I'm a bit worrying about is what happens if the server where
qnetd runs, or the qdevice
On Mon, Jul 25, 2016 at 9:07 AM, Ulrich Windl
wrote:
Andrei Borzenkov schrieb am 22.07.2016 um 17:14 in
> Nachricht <4f17c57b-7458-2ec8-cd74-3daaf9c89...@gmail.com>:
>> 22.07.2016 09:52, Ulrich Windl пишет:
>>> That could be. Should
>>> Andrei Borzenkov schrieb am 22.07.2016 um 17:14 in
Nachricht <4f17c57b-7458-2ec8-cd74-3daaf9c89...@gmail.com>:
> 22.07.2016 09:52, Ulrich Windl пишет:
>> That could be. Should there be a node list to configure, or can't the
agent
>> find out itself (for SBD)?
>>
>
> It
13 matches
Mail list logo