Hello Andrew,
El 27/06/13 14:44, Andrew Beekhof escribió:
You should see additional logs sent to /var/log/pacemaker.log
Finally yesterday issue happened again. This time, node selavi was DC,
and node turifel joined the cluster. Cluster was in status unmanaged.
Unfortunately, I have no
On 28/06/2013, at 8:10 PM, Andrew Beekhof and...@beekhof.net wrote:
On 28/06/2013, at 6:42 PM, Bernardo Cabezas Serra bcabe...@apsl.net wrote:
Hello Andrew,
El 27/06/13 14:44, Andrew Beekhof escribió:
You should see additional logs sent to /var/log/pacemaker.log
Finally yesterday
On 28/06/2013, at 9:16 PM, Andrew Beekhof and...@beekhof.net wrote:
On 28/06/2013, at 8:10 PM, Andrew Beekhof and...@beekhof.net wrote:
On 28/06/2013, at 6:42 PM, Bernardo Cabezas Serra bcabe...@apsl.net wrote:
Hello Andrew,
El 27/06/13 14:44, Andrew Beekhof escribió:
You should
Hello Bernardo
I don't know if this is the problem, but try this option
clear_node_high_bit
This configuration option is optional and is only relevant
when no nodeid is specified. Some openais clients require a signed 32
bit nodeid that is
greater than
On 27/06/2013, at 8:20 PM, Bernardo Cabezas Serra bcabe...@apsl.net wrote:
¿Do you think it's a configuration problem?
No, more likely a bug. Which is concerning since I thought I had this
particular kind ironed out.
Could you set PCMK_trace_functions=crm_get_peer on selavi and repeat the
Hello,
Ohhh, sorry, but I have deleted node selavi and restarted, and now works
OK and I can't reproduce the bug :(
El 27/06/13 12:32, Andrew Beekhof escribió:
o, more likely a bug. Which is concerning since I thought I had this
particular kind ironed out.
Could you set
Hi Emmanuel,
El 27/06/13 12:26, emmanuel segura escribió:
Hello Bernardo
I don't know if this is the problem, but try this option
clear_node_high_bit
Thanks so much, but as i stated to Andrew I can't reproduce issue any
more. Now works fine after some rebooting and node deleting.
Best
On 27/06/2013, at 10:29 PM, Bernardo Cabezas Serra bcabe...@apsl.net wrote:
Hello,
Ohhh, sorry, but I have deleted node selavi and restarted, and now works
OK and I can't reproduce the bug :(
That is unfortunate
El 27/06/13 12:32, Andrew Beekhof escribió:
o, more likely a bug. Which
