On Thu, Oct 21, 2010 at 6:46 PM, Stephan-Frank Henry
wrote:
>> Andrew Beekhof
>> Mon, 13 Sep 2010 06:25:48 -0700
>>
>> Looks like corosync can't talk to itself - ie. it never sees the
>> multicast messages it sends out.
>> This would result in the pacemaker errors you're seeing.
>>
>> Almost alway
Original-Nachricht
> Datum: Thu, 21 Oct 2010 18:46:32 +0200
> Von: "Stephan-Frank Henry"
> > Andrew Beekhof
> > Mon, 13 Sep 2010 06:25:48 -0700
> >
> > Looks like corosync can't talk to itself - ie. it never sees the
> > multicast messages it sends out.
> > This would result in
> Andrew Beekhof
> Mon, 13 Sep 2010 06:25:48 -0700
>
> Looks like corosync can't talk to itself - ie. it never sees the
> multicast messages it sends out.
> This would result in the pacemaker errors you're seeing.
>
> Almost always this is a firewall issue :-)
> Perhaps try disabling it completel
On Fri, Sep 10, 2010 at 1:15 PM, Stephan-Frank Henry
wrote:
> Hello again,
>
> new week new problem. :D
>
> Setup:
> Single node setup (default via my installer)
> /etc/hosts
> 127.0.0.1 localhost
> 172.16.0.1 cmsserver001
>
> the installer basically already takes care of setting everyt
Hello again,
new week new problem. :D
Setup:
Single node setup (default via my installer)
/etc/hosts
127.0.0.1 localhost
172.16.0.1 cmsserver001
the installer basically already takes care of setting everything up for a
single node by using both above as nodes in the drbd.conf. This h
