connect(/var/lib/ctdb/ctdb.socket) failed: Connection refused
steve
steve at steve-ss.com
Sun Aug 10 08:49:49 MDT 2014
On Sun, 2014-08-10 at 12:10 +0100, Rowland Penny wrote:
> On 10/08/14 10:38, steve wrote:
> > On Sun, 2014-08-10 at 19:31 +1000, Martin Schwenke wrote:
> >> On Sun, 10 Aug 2014 09:48:26 +0200, steve <steve at steve-ss.com> wrote:
> >>
> >>> Unfortunately, none of the ctdbd defaults is set. man ctdbd(1) still has
> >>> e.g.
> >>> '--dbdir=<directory>
> >>> [...]
> >>> This directory would usually be /var/ctdb .'
> >> Unfortunately that manpage has bit-rotted. Patches are always
> >> accepted.
> >>
> >> If you look in ctdbd.conf(5), which was added in 2.5 but
> >> only installed from 2.5.2, then you would see the truth. Similarly,
> >> ctdb(7) provides an overview of CTDB. We've worked hard to improve the
> >> documentation.
> >>> We assume that this is why the distros have stepped in big time. It
> >>> looks as though every option has to be passed on the command line. There
> >>> are no defaults.
> >> There are most certainly defaults for the databases. It
> >> is /usr/local/var/lib/ctdb. Unfortunately, you need to set CTDB_VARDIR
> >> in configuration to get the scripts to play along. We'll try to fix
> >> this.
> >>
> >>> Unfortunately too, no man pages are installed from the
> >>> source ./configure, make make install. It looks like an option from
> >>> configure. We really could use some default values. I wonder if this man
> >>> page is current: http://linux.die.net/man/1/ctdbd
> >> What version is this? I just downloaded ctdb-2.5.3.tar.gz from:
> >>
> >> https://ftp.samba.org/pub/ctdb/
> > ftp.samba.org/pub/ctdb/ctdb-2.5.tar.gz
> > There was already a configure shell.
> >
> > It looks as though we have an old version:(
> >> Before:
> >>
> >> $ find /usr/local/share/man -type f
> >> [Nothing]
> >>
> >> After (./autogen.sh && ./configure && make && sudo make install):
> >>
> >> $ find /usr/local/share/man -type f
> >> /usr/local/share/man/man1/ctdbd.1
> >> /usr/local/share/man/man1/onnode.1
> >> /usr/local/share/man/man1/ping_pong.1
> >> /usr/local/share/man/man1/ctdbd_wrapper.1
> >> /usr/local/share/man/man1/ctdb.1
> >> /usr/local/share/man/man1/ltdbtool.1
> >> /usr/local/share/man/man5/ctdbd.conf.5
> >> /usr/local/share/man/man7/ctdb-tunables.7
> >> /usr/local/share/man/man7/ctdb.7
> >>
> >> In particular, see ctdbd_wrapper(1). ctdbd_wrapper(1) can be used to
> >> start/stop CTDB without an initscript. You can put configuration
> >> in /etc/ctdb/ctdbd.conf (or any of the distro defaults,
> >> like /etc/sysconfig/ctdb or /etc/default/ctdb).
> >>
> >> peace & happiness,
> >> martin
> >
> OK, just back from USA (Uther side of Accrington), so I downloaded
> latest ctdb and extracted it, a quick scan and it seems to have the
> required conf files etc, they all seem to be there but not necessarily
> in the right place ;-) .
>
> Rowland
>
>
>
Hi
OK, this is where we are:
ctdbd is up:
ctdbd --dbdir=/usr/local/var/lib/ctdb
--dbdir-persistent=/usr/local/var/lib/ctdb/persistent
--event-script-dir=/usr/local/etc/ctdb/events.d
--public-addresses=/usr/local/etc/ctdb/public_addresses
--socket=/usr/local/var/lib/ctdb/ctdbd.socket --logfile=/var/log/syslog
winbind and smbd are running and we have joined node 1 to the domain:
2014/08/10 16:30:58.013272 [recoverd: 4050]: Trigger takeoverrun
2014/08/10 16:30:59.991246 [ 3913]: Monitoring event was cancelled
Aug 10 16:31:01 uc1 ntpd[2078]: Listen normally on 10 bond0 192.168.1.81
UDP 123
Aug 10 16:31:01 uc1 ntpd[2078]: Listen normally on 11 bond0 192.168.1.80
UDP 123
Aug 10 16:31:01 uc1 ntpd[2078]: peers refreshed
Aug 10 16:31:01 uc1 ntpd[2078]: new interface(s) found: waking up
resolver
2014/08/10 16:31:02.920250 [ 3913]: Node became HEALTHY. Ask recovery
master 0 to perform ip reallocation
ps aux|grep ctdbd
root 3913 1.4 0.8 4824 4224 ? SLs 16:30 0:06 ctdbd
--dbdir=/usr/local/var/lib/ctdb
--dbdir-persistent=/usr/local/var/lib/ctdb/persistent
--event-script-dir=/usr/local/etc/ctdb/events.d
--public-addresses=/usr/local/etc/ctdb/public_addresses
--socket=/usr/local/var/lib/ctdb/ctdbd.socket --logfile=/var/log/syslog
root 4050 0.7 0.2 4428 1064 ? S 16:30 0:03 ctdbd
--dbdir=/usr/local/var/lib/ctdb
--dbdir-persistent=/usr/local/var/lib/ctdb/persistent
--event-script-dir=/usr/local/etc/ctdb/events.d
--public-addresses=/usr/local/etc/ctdb/public_addresses
--socket=/usr/local/var/lib/ctdb/ctdbd.socket --logfile=/var/log/syslog
root 6950 0.0 0.1 7124 836 pts/3 S+ 16:37 0:00 grep
--color=auto ctdbd
which ctdb
/usr/local/bin/ctdb
ctdb errors out:
ctdb status
2014/08/10 16:38:59.619340 [ 7383]: client/ctdb_client.c:267 Failed to
connect client socket to daemon. Errno:Connection refused(111)
common/cmdline.c:156 Failed to connect to daemon
2014/08/10 16:38:59.626991 [ 7383]: Failed to init ctdb
Is the socket there?
ls -l /usr/local/var/lib/ctdb
total 8
srwx------ 1 root root 0 ago 10 16:41 ctdbd.socket
drwx------ 2 root root 4096 ago 10 14:14 persistent
drwx------ 2 root root 4096 ago 10 16:41 state
smb.conf
[global]
workgroup = ALTEA
realm = ALTEA.SITE
security = ADS
#kerberos method = secrets only
netbios name = SMBCLUSTER
winbind enum users = Yes
winbind enum groups = Yes
winbind use default domain = Yes
winbind nss info = rfc2307
idmap config * : backend = tdb
idmap config * : range = 19900-19999
idmap config ALTEA : backend = ad
idmap config ALTEA : range = 20000-4000000
idmap config ALTEA : schema_mode = rfc2307
clustering = Yes
ctdbd socket = /usr/local/var/lib/ctdb/ctdbd.socket
[users]
path = /cluster/users
read only = No
[profiles]
path = /cluster/profiles
read only = No
/usr/local/etc/ctdb/nodes
192.168.0.10
192.168.0.11
/usr/local/etc/ctdb/public_addresses
192.168.1.80/24 bond0
192.168.1.81/24 bond0
DNS is round robin and the entries are present:
host smbcluster
smbcluster.altea.site has address 192.168.1.81
smbcluster.altea.site has address 192.168.1.80
BUT, smbcluster is on the IP of the node itself: 192.168.1.82 and NOT
either of the cluster nodes:
Kerberos: Looking for PKINIT pa-data -- SMBCLUSTER$@ALTEA.SITE
Kerberos: Looking for ENC-TS pa-data -- SMBCLUSTER$@ALTEA.SITE
Kerberos: No preauth found, returning PREAUTH-REQUIRED -- SMBCLUSTER
$@ALTEA.SITE
Kerberos: AS-REQ SMBCLUSTER$@ALTEA.SITE from ipv4:192.168.1.82:53758 for
krbtgt/ALTEA.SITE at ALTEA.SITE
Kerberos: Client sent patypes: encrypted-timestamp, 149
Kerberos: Looking for PKINIT pa-data -- SMBCLUSTER$@ALTEA.SITE
Kerberos: Looking for ENC-TS pa-data -- SMBCLUSTER$@ALTEA.SITE
Kerberos: ENC-TS Pre-authentication succeeded -- SMBCLUSTER$@ALTEA.SITE
using arcfour-hmac-md5
Question: why is ctdb status failing?
More information about the samba-technical
mailing list