So,
first problem is, that both of corosync nodes have same ip addrs.
Corosync nodes MUST have different addresses (so let's say 192.168.58.1
and 192.168.58.2). You must configure them in so, so:
interface {
member {
memberaddr: 192.168.58.1
}
member {
memberaddr: 192.168.58.2
}
ringnumber: 0
bindnetaddr: 192.168.58.0
mcastport: 5405
}
I believe that main problem is, that you think that corosync is
responsible for keeping service IP (so let's say 192.168.58.10). It's
not, this is job for pacemaker and resource scripts.
So first, ensure you have really 2 different IPs on your nodes, you can
ping them, then configure corosync correctly and I believe everything
will start working as expected.
Honza
Adrian Gibanel napsal(a):
Short description
---------------------
...
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss
