Setting up CTDB on OCFS2 and VMs ...
stefan at kania-online.de
Tue Dec 16 10:38:31 MST 2014
-----BEGIN PGP SIGNED MESSAGE-----
Am 16.12.14 um 15:27 schrieb Rowland Penny:
> On 16/12/14 13:12, Stefan Kania wrote: Hi Rowland,
> If these addresses should be your IPs vor Clients accessing the
> Cluster, you must put tese IPs in your public_addresses file
>> OK, they are in the public_addresses file
> and in your DNS the hostname vor your cluster should point to both
>> DOH! CNAME.
> Remeber that you have ti install "ethtool" on all nodes!
>> What do mean remember? I haven't seen it anywhere that you must
>> install ethtool, It is installed anyway :-D
I had an error-massage on the node without ethtool, and the nodes were
unhealty. After I installaed ethtool it worked for me and the
error-message was gone.
> So if you start the cluster the system will pick an IP-Address out
> of the file. If there is no public_addresses file your system will
> not get any IP. If there is no ethtool but a public_address file,
> the node cant set on of the IPs. If one node of your clusters fails
> the second not will get the IP address from the failed host. BUT
> REMEBER you wount see the IPs with "ifconfig" you MUST use "ip a
>> That is something else that I haven't seen anywhere! :-)
What I think ist that CTDB is assaigning the virtual IP over "ip" and
configuring the NIC with ethtool. So if you are setting an IP with the
"ip" command, this address is not shown with "ifconfig"
Did you get rid of the IP-Errormessage?
I think that's your main problem.
> Am 16.12.14 um 10:30 schrieb Rowland Penny:
>>>> On 16/12/14 07:53, Stefan Kania wrote:
>>>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>>>> Hi Rowland,
>>>>> did you see that you have som Problems with IPs on node 1?
>>>>> 2014/12/15 16:32:28.300370 [recoverd: 2497]: Failed to find
>>>>> node to cover ip 192.168.0.9 2014/12/15 16:32:28.300412
>>>>> [recoverd: 2497]: Failed to find node to cover ip
>>>>> 192.168.0.8 I also had some problems with IP and
>>>>> nameresolutions at the beginning. After I solved that
>>>>> problem everything was fine.
>>>> I did wonder about those lines, I do not have 192.168.0.8 &
>>>> 192.168.0.9, but Ronnie posted this:
>>>> No, you should not/need not create them on the system. Ctdbd
>>>> will create and assign these addresses automatically and
>>>> dynamically while the cluster is running.
>>>> So, do I need to create them and if so, where? This is one
>>>> of those areas of CTDB that doesn't seem to documented at
> -- Stefan Kania Landweg 13 25693 St. Michaelisdonn
> Signieren jeder E-Mail hilft Spam zu reduzieren. Signieren Sie
> ihre E-Mail. Weiter Informationen unter http://www.gnupg.org
> Mein Schlüssel liegt auf
25693 St. Michaelisdonn
Signieren jeder E-Mail hilft Spam zu reduzieren. Signieren Sie ihre
E-Mail. Weiter Informationen unter http://www.gnupg.org
Mein Schlüssel liegt auf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.16 (Darwin)
-----END PGP SIGNATURE-----
More information about the samba-technical