Hi,
DocumentRoot is still set to /var/www/html
ls -al /var/www/html shows different things on the 2 nodes
node01:
total 28
drwxr-xr-x. 3 root root 4096 Nov 11 12:25 .
drwxr-xr-x. 6 root root 4096 Jul 23 22:18 ..
-rw-r--r--. 1 root root50 Oct 28 18:00 index.html
drwx--. 2 root root 16384
> On 11 Nov 2014, at 4:39 am, Daniel Dehennin
> wrote:
>
> emmanuel segura writes:
>
>> I think, you don't have fencing configured in your cluster.
>
> I have fencing configured and working, modulo fencing VMs on dead host[1].
Are you saying that the host and the VMs running inside it are b
Tomasz Kontusz writes:
> Hanging corosync sounds like libqb problems: trusty comes with 0.16,
> which likes to hang from time to time. Try building libqb 0.17.
Thanks, I'll look at this.
Is there a way to get back to normal state without rebooting all
machines and interrupting services?
I thou
emmanuel segura writes:
> I think, you don't have fencing configured in your cluster.
I have fencing configured and working, modulo fencing VMs on dead host[1].
Regards.
Footnotes:
[1] http://oss.clusterlabs.org/pipermail/pacemaker/2014-November/022965.html
--
Daniel Dehennin
Récupérer ma
Hanging corosync sounds like libqb problems: trusty comes with 0.16, which
likes to hang from time to time. Try building libqb 0.17.
Daniel Dehennin napisał:
>Hello,
>
>I just have an issue on my pacemaker setup, my dlm/clvm/gfs2 was
>blocked.
>
>The “dlm_tool ls” command told me “wait ringid”.
В Mon, 10 Nov 2014 10:07:18 +0100
Tomasz Kontusz пишет:
> I think the suggestion was to put shooting the host in the fencing path of a
> VM. This way if you can't get the host to fence the VM (as the host is
> already dead) you just check if the host was fenced.
>
Exactly. One thing I do not
I think, you don't have fencing configured in your cluster.
2014-11-10 17:02 GMT+01:00 Daniel Dehennin :
> Daniel Dehennin writes:
>
>> Hello,
>
> Hello,
>
>> I just have an issue on my pacemaker setup, my dlm/clvm/gfs2 was
>> blocked.
>>
>> The “dlm_tool ls” command told me “wait ringid”.
>
> It
Daniel Dehennin writes:
> Hello,
Hello,
> I just have an issue on my pacemaker setup, my dlm/clvm/gfs2 was
> blocked.
>
> The “dlm_tool ls” command told me “wait ringid”.
It happened again:
root@nebula2:~# dlm_tool ls
dlm lockspaces
name datastores
id0x1b6
Hey Team,
I'm receiving some strange intermittent failovers on a two-node cluster
(happens once every week or two). When this happens, both nodes are
unavailable; one node will be marked offline and the other will be shown as
unclean. Any help on this would be massively appreciated. Thanks.
Ru
On Sat, Nov 08, 2014 at 12:58:36AM +, aridh bose wrote:
> Hi,
> While using heartbeat and pacemaker, is it possible to bringup first
> node which can go as Master, followed by second node which should go
> as Slave without causing any issues to the first node? Currently, I
> see a couple of pr
Hello,
I just have an issue on my pacemaker setup, my dlm/clvm/gfs2 was
blocked.
The “dlm_tool ls” command told me “wait ringid”.
The corosync-* commands hangs (like corosync-quorumtool).
The pacemaker “crm_mon” display nothing wrong.
I'm using Ubuntu Trusty Tahr:
- corosync 2.3.3-1ubuntu1
-
I think the suggestion was to put shooting the host in the fencing path of a
VM. This way if you can't get the host to fence the VM (as the host is already
dead) you just check if the host was fenced.
Daniel Dehennin napisał:
>Andrei Borzenkov writes:
>
>
>[...]
>
>>> Now I have one issue, whe
Andrei Borzenkov writes:
[...]
>> Now I have one issue, when the bare metal host on which the VM is
>> running die, the VM is lost and can not be fenced.
>>
>> Is there a way to make pacemaker ACK the fencing of the VM running on a
>> host when the host is fenced itself?
>>
>
> Yes, you can d
13 matches
Mail list logo
