On Mon, Apr 11, 2016 at 08:23:03AM +0200, Jan Friesse wrote:
...
>>> bond0: mtu 1500 qdisc noqueue state UP
>>> link/ether 74:e6:e2:73:e5:61 brd ff:ff:ff:ff:ff:ff
>>> inet 10.150.20.91/24 brd 10.150.20.55 scope global bond0
>>> inet
08.04.2016 17:51, Jan Friesse пишет:
On 04/08/16 13:01, Jan Friesse wrote:
>> pacemaker 1.1.12-11.12
>> openais 1.1.4-5.24.5
>> corosync 1.4.7-0.23.5
>>
>> Its a two node active/passive cluster and we just upgraded the
SLES 11
>> SP 3 to SLES 11 SP 4(nothing else) but when we try to
On 04/08/16 19:51, Jan Friesse wrote:
>> >> /var/log/messages:
>> >> Apr 6 17:51:49 prd1 corosync[8672]: [TOTEM ] Initializing
transport
>> >> (UDP/IP Unicast).
>> >> Apr 6 17:51:49 prd1 corosync[8672]: [TOTEM ] Initializing
>> >> transmit/receive security: libtomcrypt
08.04.2016 17:51, Jan Friesse пишет:
>> On 04/08/16 13:01, Jan Friesse wrote:
>> >> pacemaker 1.1.12-11.12
>> >> openais 1.1.4-5.24.5
>> >> corosync 1.4.7-0.23.5
>> >>
>> >> Its a two node active/passive cluster and we just upgraded the
>> SLES 11
>> >> SP 3 to SLES 11 SP 4(nothing else)
On 04/08/16 13:01, Jan Friesse wrote:
>> pacemaker 1.1.12-11.12
>> openais 1.1.4-5.24.5
>> corosync 1.4.7-0.23.5
>>
>> Its a two node active/passive cluster and we just upgraded the SLES 11
>> SP 3 to SLES 11 SP 4(nothing else) but when we try to start the cluster
>> service we get the following
pacemaker 1.1.12-11.12
openais 1.1.4-5.24.5
corosync 1.4.7-0.23.5
Its a two node active/passive cluster and we just upgraded the SLES 11
SP 3 to SLES 11 SP 4(nothing else) but when we try to start the cluster
service we get the following error:
"Totem is unable to form a cluster because of an
pacemaker 1.1.12-11.12
openais 1.1.4-5.24.5
corosync 1.4.7-0.23.5
Its a two node active/passive cluster and we just upgraded the SLES 11
SP 3 to SLES 11 SP 4(nothing else) but when we try to start the cluster
service we get the following error:
"Totem is unable to form a cluster because of