On Thu, 2018-06-07 at 08:37 +0800, Albert Weng wrote:
> Hi Andrei,
>
> Thanks for your quickly reply. Still need help as below :
>
> On Wed, Jun 6, 2018 at 11:58 AM, Andrei Borzenkov m> wrote:
> > 06.06.2018 04:27, Albert Weng пишет:
> > > Hi All,
> > >
> > > I have created active/passive
On 07/06/18 11:08 -0400, Styopa Semenukha wrote:
> Thank you for your thoughts, Jan! I agree with the importance of the
> topics you raised, and I'd like to comment on them in the light of
> our project (and configuration management approach in general).
>
> On 06/06/2018 08:26 PM, Jan Pokorný
Jan Pokorný wrote:
While I see why Ansible is compelling, I feel it's important to
challenge this trend of trying to bend/rebrand _machine-local
configuration management tool_ as _distributed system management tool_
(pacemaker is distributed application/framework of sorts), which Ansible
alone
On 07/06/18 15:53, Prasad Nagaraj wrote:
> Hi - As you can see in the corosync.conf details - i have already kept
> debug: on
>
But only in the (disabled) AMF subsystem, not for corosync as a whole :)
logger_subsys {
subsys: AMF
debug: on
}
Chrissie
>
> On Thu, 7 Jun 2018,
Thank you for your thoughts, Jan! I agree with the importance of the
topics you raised, and I'd like to comment on them in the light of our
project (and configuration management approach in general).
On 06/06/2018 08:26 PM, Jan Pokorný wrote:
On 07/06/18 02:19 +0200, Jan Pokorný wrote:
While
Hi - As you can see in the corosync.conf details - i have already kept
debug: on
Thanks!
On Thu, 7 Jun 2018, 8:03 pm Christine Caulfield,
wrote:
> On 07/06/18 15:24, Prasad Nagaraj wrote:
> >
> > No iptables or otherwise firewalls are setup on these nodes.
> >
> > One observation is that each
On 07/06/18 15:24, Prasad Nagaraj wrote:
>
> No iptables or otherwise firewalls are setup on these nodes.
>
> One observation is that each node sends messages on with its own ring
> sequence number which is not converging.. I have seen that in a good
> cluster, when nodes respond with same
No iptables or otherwise firewalls are setup on these nodes.
One observation is that each node sends messages on with its own ring
sequence number which is not converging.. I have seen that in a good
cluster, when nodes respond with same sequence number, the membership is
automatically formed.
On 07/06/18 12:00, Prasad Nagaraj wrote:
> And here is how startup log looks on one of the nodes.
> Its pretty much same on the other nodes as well
>
That all looks fine to me (from a corosync POV anyway). Have you checked
for any iptables rules getting in the way?
Chrissie
> Jun 07 10:41:37
Jan Pokorný writes:
> 1. [X] Do you edit CIB by hand (as opposed to relying on crm/pcs or
> their UI counterparts)?
For debugging one has to understand the CIB anyway, so why learn
additional syntaxes? :) Most of our configuration changes are scripted
via a home-grown domain-specific
And here is how startup log looks on one of the nodes.
Its pretty much same on the other nodes as well
Jun 07 10:41:37 corosync [MAIN ] Corosync Cluster Engine ('UNKNOWN'):
started and ready to provide service.
Jun 07 10:41:37 corosync [MAIN ] Corosync built-in features: nss
Jun 07 10:41:37
Hi Christine -
Thanks for looking into this and here are the details.
All the nodes are pingable from each other and actively exchanging corosync
packets from each other as seen from tcpdump
Here is the ifconfig out from each of the node
# ifconfig
eth0 Link encap:Ethernet HWaddr
On 07/06/18 09:21, Prasad Nagaraj wrote:
> Hi - I am running corosync on 3 nodes of CentOS release 6.9 (Final).
> Corosync version is corosync-1.4.7.
> The nodes are not seeing each other and not able to form memberships.
> What I see is continuous message about " A processor joined or left the
Hi,
On 31.05.2018 15:48, Jan Pokorný wrote:
Hello,
I am soliciting feedback on these CIB features related questions,
please reply (preferably on-list so we have the shared collective
knowledge) if at least one of the questions is answered positively
in your case (just tick the respective "[ ]"
Hi - I am running corosync on 3 nodes of CentOS release 6.9 (Final).
Corosync version is corosync-1.4.7.
The nodes are not seeing each other and not able to form memberships.
What I see is continuous message about " A processor joined or left the
membership and a new membership was formed."
For
15 matches
Mail list logo
