[Samba] smbd does not start under ctdb

steve steve at steve-ss.com
Thu Jul 10 03:41:23 MDT 2014


On Wed, 2014-07-09 at 12:38 +0200, David Disseldorp wrote:
> On Tue, 08 Jul 2014 14:02:06 +0200, steve wrote:
> 
> > All seems OK with ctdb:
> > n1:
> > ctdb status
> > Number of nodes:2
> > pnn:0 192.168.0.10     OK (THIS NODE)
> > pnn:1 192.168.0.11     OK
> > Generation:1187222392
> > Size:2
> > hash:0 lmaster:0
> > hash:1 lmaster:1
> > Recovery mode:NORMAL (0)
> > Recovery master:0
> > 
> > n2:
> > ctdb status
> > Number of nodes:2
> > pnn:0 192.168.0.10     OK
> > pnn:1 192.168.0.11     OK (THIS NODE)
> > Generation:1187222392
> > Size:2
> > hash:0 lmaster:0
> > hash:1 lmaster:1
> > Recovery mode:NORMAL (0)
> > Recovery master:0
> > 
> > But we cannot start smbd:
> > Maximum core file size limits now 16777216(soft) -1(hard)
> > smbd version 4.1.9-3.22.1-3256-SUSE-oS13.1-i386 started.
> > Copyright Andrew Tridgell and the Samba Team 1992-2013
> > uid=0 gid=0 euid=0 egid=0
> > lp_load_ex: refreshing parameters
> > Initialising global parameters
> > rlimit_max: increasing rlimit_max (1024) to minimum Windows limit
> > (16384)
> > params.c:pm_process() - Processing configuration file
> > "/etc/samba/smb.conf"
> > Processing section "[global]"
> > connect(/var/lib/ctdb/ctdb.socket) failed: Connection refused
> > messaging_ctdbd_init failed: NT_STATUS_CONNECTION_REFUSED
> > 
> > We tried changing the socket to /tmp but the same errors occur.
> > Any ideas?
> 
> If you're not running ctdb under pacemaker, then you probably want
> ctdb to manage the samba resource (start and stop smbd), the same goes
> for winbind.
> 
> This should be possible with the following in /etc/sysconfig/ctdb:
> CTDB_MANAGES_SAMBA=yes
> 
> Enable the event script with:
> # ctdb enablescript 50.samba
Hi. OK. We've now tried that. We're on openSUSE 13.1. With the stock 2.3
ctdb:
Nothing is started.

With 2.5.3 from the ha repo indeed, smb starts, but both nodes are
reported as UNHEALTHY. Always.

We have drbd primary:primary and want both nodes live and running smbd.
If one goes down, we still have the other.
Qn. Is this possible?
Cheers,
Steve


> 
> > Thanks,
> > Steve
> > 
> > smb.conf:
> > [global]
> > realm = HH3.SITE
> > security = ADS
> > kerberos method = system keytab
> > netbios name = smbcluster
> > clustering = Yes
> > private dir = /cluster/ctdb
> 
> I'd recommend also explicitly setting the ctdb socket path here...
> ctdbd socket = /var/lib/ctdb/ctdb.socket
> 
> > [users]
> > path = /cluster/users
> > read only = No
> > 
> > The nodes are mounted at both ends:
> > /dev/drbd1 on /cluster type ocfs2
> > (rw,relatime,_netdev,heartbeat=local,nointr,data=ordered,errors=remount-ro,atime_quantum=60,coherency=full,user_xattr,acl)
> > 
> > 
> > /etc/sysconfig/ctdb
> > 
> > CTDB_RECOVERY_LOCK="/cluster/ctdb/lockfile"
> > CTDB_PUBLIC_INTERFACE=enp0s3
> > CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses
> > CTDB_LVS_PUBLIC_IP=
> > CTDB_SAMBA_SKIP_SHARE_CHECK=yes
> > CTDB_MANAGES_ISCSI=yes
> > CTDB_INIT_STYLE=
> > CTDB_NODES=/etc/ctdb/nodes
> > CTDB_NOTIFY_SCRIPT=/etc/ctdb/notify.sh
> > CTDB_DBDIR=/var/lib/ctdb
> > CTDB_DBDIR_PERSISTENT=/var/lib/ctdb/persistent
> > CTDB_EVENT_SCRIPT_DIR=/etc/ctdb/events.d
> > CTDB_SOCKET=/var/lib/ctdb/ctdb.socket
> > CTDB_TRANSPORT="tcp"
> > CTDB_MONITOR_FREE_MEMORY=100
> > CTDB_START_AS_DISABLED="yes"
> > CTDB_CAPABILITY_RECMASTER=yes
> > CTDB_CAPABILITY_LMASTER=yes
> > NATGW_PUBLIC_IP=
> > NATGW_PUBLIC_IFACE=
> > NATGW_DEFAULT_GATEWAY=
> > NATGW_PRIVATE_IFACE=
> > NATGW_PRIVATE_NETWORK=
> > NATGW_NODES=/etc/ctdb/natgw_nodes
> > CTDB_LOGFILE=/var/log/ctdb/log.ctdb
> > CTDB_DEBUGLEVEL=2
> > CTDB_OPTIONS=
> > 
> > 
> 




More information about the samba mailing list