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
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
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
[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@xxxxxxxxxxxxxxxx> wrote:
Hi,
On 29/04/15 10:34, Sharad Shukla wrote:
SharadThanksThis application is a little urgent for me. I would really appreciate your help..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 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"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: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..
gluster volume set [VOLUME] auth.allow [IP ADDRESS]
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, and is
believed to be clean.
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx 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 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@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users