[Gluster-users] Shared IP address

Wed May 6 16:59:24 UTC 2015

How are you Creating the Mount?
Using Fuse or NFS?
The server hosting the BRICK must have the volume mounted before CTDB can use it. From the look of the Error message its failing to find the mount, AND-OR, file

See if you can start the server without CTDB starting.
Then see if the file system is mounting.

From there I would suggest that you see why the Mount is failing, I think that the System is not fully up when a NFS mount is tried, so I would use the LINKDELAY in the interface scripts. Ifcfg-eth0

Thomas Holkenbrink / Systems Architect, Cloud
Green House Data

From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of Raghavendra Talur
Sent: Monday, May 4, 2015 12:27 PM
To: Sharad Shukla
Cc: gluster-users
Subject: Re: [Gluster-users] Shared IP address

On Mon, May 4, 2015 at 5:19 PM, Sharad Shukla <sharadshukla19 at gmail.com<mailto:sharadshukla19 at gmail.com>> wrote:
Hi Thomas,
Thank you so much for your reply.
I tried the steps which you advised but unfortunately the issue still persists. Please find the below details..

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Ctdb config:

CTDB_RECOVERY_LOCK="/mnt/datavaol/lock/lockfile"
CTDB_PUBLIC_ADDRESSES=/mnt/datavol/lock/public_addresses
CTDB_MANAGES_SAMBA=yes
CTDB_NODES=/mnt/datavol/lock/nodes
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

/var/log/log.ctdb
-------------------------

2015/05/04 13:21:42.521866 [24966]: Freeze priority 2
2015/05/04 13:21:42.522969 [24966]: Freeze priority 3
2015/05/04 13:21:42.716936 [24966]: Freeze priority 1
2015/05/04 13:21:42.717029 [24966]: Freeze priority 2
2015/05/04 13:21:42.717092 [24966]: Freeze priority 3
2015/05/04 13:21:45.721344 [recoverd:25127]: Taking out recovery lock from recovery daemon
2015/05/04 13:21:45.721441 [recoverd:25127]: Take the recovery lock
2015/05/04 13:21:45.721496 [recoverd:25127]: ctdb_recovery_lock: Unable to open /mnt/datavaol/lock/lockfile - (No such file or directory)
2015/05/04 13:21:45.721517 [recoverd:25127]: Unable to get recovery lock - aborting recovery and ban ourself for 300 seconds
2015/05/04 13:21:45.721569 [24966]: Banning this node for 300 seconds
2015/05/04 13:23:42.718113 [24966]: server/ctdb_recover.c:562 Been in recovery mode for too long. Dropping all IPS
2015/05/04 13:26:45.722369 [24966]: Banning timedout
2015/05/04 13:26:46.169915 [recoverd:25127]: server/ctdb_recoverd.c:3699 Current recmaster node 1 does not have CAP_RECMASTER, but we (node 0) have - force an election
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

# ctdb status
Number of nodes:2
pnn:0 192.168.3.131    BANNED|UNHEALTHY|INACTIVE (THIS NODE)
pnn:1 192.168.3.132    DISCONNECTED|UNHEALTHY|INACTIVE
Generation:INVALID
Size:2
hash:0 lmaster:0
hash:1 lmaster:1
Recovery mode:RECOVERY (1)
Recovery master:0

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
So it directly goes to the recovery mode.  Please help with this...  Please let me know if you need any other details..

There is a typo in the config file

CTDB_RECOVERY_LOCK="/mnt/datavaol/lock/lockfile"
CTDB_PUBLIC_ADDRESSES=/mnt/datavol/lock/public_addresses

s/datavaol/datavol

Thanks
Sharad

On Thu, Apr 30, 2015 at 8:36 PM, Thomas Holkenbrink <tholkenbrink at greenhousedata.com<mailto:tholkenbrink at greenhousedata.com>> wrote:
Forgot to add…
In your Interface config file Add a LINK DELAY which will assure that the network is online before Gluster comes online.  CTDB is dependent on the mount to be there so that its Config files can be seen.
In my /etc/sysconfig/network-scripts/ifcfg-eth0  I add this

LINKDELAY=10

Thomas Holkenbrink / Systems Architect, Cloud

From: gluster-users-bounces at gluster.org<mailto:gluster-users-bounces at gluster.org> [mailto:gluster-users-bounces at gluster.org<mailto:gluster-users-bounces at gluster.org>] On Behalf Of Sharad Shukla
Sent: Thursday, April 30, 2015 9:56 AM
To: Alex Crow
Cc: gluster-users
Subject: Re: [Gluster-users] Shared IP address

Hi Alex and friends,
I have installed CTDB and all related packages . I did all the required steps to configure ctdb and samba configuration, but somehow the lockfile functionality does not work.
Following is the ctdb configuration:
CTDB_RECOVERY_LOCK="/mnt/datavaol/lock/lockfile"
CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses
CTDB_MANAGES_SAMBA=yes
CTDB_NODES=/etc/ctdb/nodes
Having the above config I was getting the error "Unable to find lockfile". So the problem was with CTDB_RECOVERY_LOCK, so I commented it. After this I again started ctdb services but now the Samba starting was a big problem....  I was getting the following error:
Starting SMB services: /bin/bash: line 1:  4339 Aborted                 (core dumped) smbd -D
Following is the smb.conf:
[global]
        clustering = yes
        idmap backend = tdb2
        private dir = /mnt/datavol/lock

[share]
        comment = Gluster and CTDB based shared volume
        path = /mnt/datavol/share
        read only = no
        guest ok = yes
I tried every possible way to start Samba daemon but failed to do so ..
I would really appreciate if you can look into this configuration and suggest me some tips to make ctdb running without any errors..
Thanks & Regards
Sharad

On Wed, Apr 29, 2015 at 11:45 AM, Alex Crow <acrow at integrafin.co.uk<mailto:acrow at integrafin.co.uk>> wrote:

On 29/04/15 10:34, Sharad Shukla wrote:
Hi Susant,
I have installed Glusterfs in 2 machines which I want to use for establishing cluster. I am using CentOs 6.6. The gluster volume is set up and running fine. I am manually creating the files onto the mounted volume and they are replicating..
So far looks like everything is working. Now I have configured a shared ip address for reaching the replicated volume by using the following command:
gluster volume set [VOLUME] auth.allow [IP ADDRESS]

This IP address is visible to me under "gluster volume info", but I am unable to ping this ip address. I am getting the message that "Host is unreachable"
I need this ip address reachable so that I can connect my application which needs to use this shared ip to connect to cluster.
This application is a little urgent for me. I would really appreciate your help..
Thanks
Sharad

Hi,

That command is just setting an acl for that IP to connect to the gluster daemon.

Normally you don't need to add any IP addresses as glusterfs clients will know about both servers as soon as they connect to one of them. If you're using Samba or NFS the preferred option is to use CTDB to spread a pool of virtual IP addresses over the servers.

Cheers

Alex

--
This message has been scanned for viruses and
dangerous content by MailScanner<http://www.mailscanner.info/>, and is
believed to be clean.

_______________________________________________

Gluster-users mailing list

Gluster-users at gluster.org<mailto:Gluster-users at gluster.org>

http://www.gluster.org/mailman/listinfo/gluster-users

--

This message is intended only for the addressee and may contain

confidential information. Unless you are that person, you may not

disclose its contents or use it in any way and are requested to delete

the message along with any attachments and notify us immediately.

"Transact" is operated by Integrated Financial Arrangements plc. 29

Clement's Lane, London EC4N 7AE. Tel: (020) 7608 4900<tel:%28020%29%207608%204900> Fax: (020) 7608

5300. (Registered office: as above; Registered in England and Wales

under number: 3727592). Authorised and regulated by the Financial

Conduct Authority (entered on the Financial Services Register; no. 190856).

_______________________________________________
Gluster-users mailing list
Gluster-users at gluster.org<mailto:Gluster-users at gluster.org>
http://www.gluster.org/mailman/listinfo/gluster-users

_______________________________________________
Gluster-users mailing list
Gluster-users at gluster.org<mailto:Gluster-users at gluster.org>
http://www.gluster.org/mailman/listinfo/gluster-users

--
Raghavendra Talur

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20150506/a13f72d4/attachment.html>