Re: [Pacemaker] Loosing corosync communication clusterwide

2014-11-12 Thread Daniel Dehennin
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. It was already reported on Ubuntu tracker[1] Regards. Footnotes: [1] https://bugs.launchpad.net/ubuntu/+source/libqb/+bug/1341496 -

Re: [Pacemaker] Loosing corosync communication clusterwide

2014-11-11 Thread Andrew Beekhof
> On 11 Nov 2014, at 10:12 pm, Daniel Dehennin > wrote: > > Andrew Beekhof writes: > > > [...] > >>> 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 both part of >> the same cluster? > > Yes,

Re: [Pacemaker] Loosing corosync communication clusterwide

2014-11-11 Thread Daniel Dehennin
Andrew Beekhof writes: [...] >> 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 both part of > the same cluster? Yes, one of the VM needs to access the GFS2 filesystem like the nodes, the other VM is

Re: [Pacemaker] Loosing corosync communication clusterwide

2014-11-10 Thread Andrew Beekhof
> 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

Re: [Pacemaker] Loosing corosync communication clusterwide

2014-11-10 Thread Daniel Dehennin
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

Re: [Pacemaker] Loosing corosync communication clusterwide

2014-11-10 Thread Daniel Dehennin
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

Re: [Pacemaker] Loosing corosync communication clusterwide

2014-11-10 Thread Tomasz Kontusz
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”.

Re: [Pacemaker] Loosing corosync communication clusterwide

2014-11-10 Thread emmanuel segura
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

Re: [Pacemaker] Loosing corosync communication clusterwide

2014-11-10 Thread 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 happened again: root@nebula2:~# dlm_tool ls dlm lockspaces name datastores id0x1b6