Ulrich Windl wrote:
>
> and this ring configuration:
> interface {
> bindnetaddr: 172.20.0.0
> mcastaddr: 239.192.3.9
> mcastport: 5405
> ringnumber: 0
> }
>
We got the same problem
but first, you should put :
bindnetaddr: 172.20.3.0
instead of :
bindnetaddr: 172.20.0.0
to settle better in the eth0
Ulrich Windl wrote:
>
> I get:
> # corosync-cfgtool -s
> Printing ring status.
> Local node ID 16777343
> RING ID 0
> id = 127.0.0.1
> status = ring 0 active with no faults
> RING ID 1
> id = 192.168.0.61
> status = ring 1 active with no faults
>
then I had to put a delay in /etc/sysconfig/network :
NETWORKDELAY=30
so that LSB service use it :
[ -n "${NETWORKDELAY}" ] && /bin/sleep ${NETWORKDELAY}
-> end of start() function
and corosync.service must be adjusted to start afterwhile network script
and then corosync binds on eth0 correctly.
--
View this message in context:
http://old.nabble.com/corosync-binding-to-127.0.0.1-instead-of-correct-interface-tp34290633p34402258.html
Sent from the Linux-HA mailing list archive at Nabble.com.
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
