connect(/var/lib/ctdb/ctdb.socket) failed: Connection refused

[steve]

On Sun, 2014-08-10 at 19:36 +1000, Martin Schwenke wrote:
> On Sun, 10 Aug 2014 11:13:24 +0200, steve <steve at steve-ss.com> wrote:
> 
> > For now. All sorts of anomalies already. Even though the binaries have
> > gone in under /usr/local, the event scripts have ended up in distroland
> > under /etc
> 
> Not sure what's happening at your end.  For me, on a Debian system with
> out-of-the-box ctdb-2.5.3:
> 
>   $ find /usr/local/etc -type f 
>   /usr/local/etc/ctdb/notify.sh
>   /usr/local/etc/ctdb/ctdb-crash-cleanup.sh
>   /usr/local/etc/ctdb/nfs-rpc-checks.d/10.statd.check
>   /usr/local/etc/ctdb/nfs-rpc-checks.d/50.rquotad.check
>   /usr/local/etc/ctdb/nfs-rpc-checks.d/20.nfsd.check
>   /usr/local/etc/ctdb/nfs-rpc-checks.d/40.mountd.check
>   /usr/local/etc/ctdb/nfs-rpc-checks.d/30.lockd.check
>   /usr/local/etc/ctdb/functions
>   /usr/local/etc/ctdb/debug_locks.sh
>   /usr/local/etc/ctdb/gcore_trace.sh
>   /usr/local/etc/ctdb/debug-hung-script.sh
>   /usr/local/etc/ctdb/events.d/99.timeout
>   /usr/local/etc/ctdb/events.d/11.natgw
>   /usr/local/etc/ctdb/events.d/20.multipathd
>   /usr/local/etc/ctdb/events.d/60.ganesha
>   /usr/local/etc/ctdb/events.d/40.fs_use
>   /usr/local/etc/ctdb/events.d/10.interface
>   /usr/local/etc/ctdb/events.d/13.per_ip_routing
>   /usr/local/etc/ctdb/events.d/91.lvs
>   /usr/local/etc/ctdb/events.d/01.reclock
>   /usr/local/etc/ctdb/events.d/49.winbind
>   /usr/local/etc/ctdb/events.d/60.nfs
>   /usr/local/etc/ctdb/events.d/31.clamd
>   /usr/local/etc/ctdb/events.d/00.ctdb
>   /usr/local/etc/ctdb/events.d/40.vsftpd
>   /usr/local/etc/ctdb/events.d/50.samba
>   /usr/local/etc/ctdb/events.d/41.httpd
>   /usr/local/etc/ctdb/events.d/62.cnfs
>   /usr/local/etc/ctdb/events.d/70.iscsi
>   /usr/local/etc/ctdb/events.d/11.routing
>   /usr/local/etc/ctdb/statd-callout
>   /usr/local/etc/sudoers.d/ctdb
> 
> I suppose it could be Ubuntu strangeness.
> 
> If you set CTDB_BASE somewhere (/etc/profile.d/ctdb.sh ?) before
> running ctdbd_wrapper then you could even have
> /usr/local/etc/ctdb/ctdbd.conf.
> 
> We clearly need to fix the default "make install" so that it just
> works. 

Hi Martin
It shouldn't be this hard. Maybe you know where the stuff goes but we
have to work it out for ourselves. The usual rule for tarballs is to
use /usr/local/x for everything to keep it separate from distroland rpms
and dpkgs. If you the start putting stuff from make install at e.g. /etc
instead of /usr/local/etc it makes it a nightmare for your end users. We
tried 2.5.3 before. On Ubuntu 14.04, nothing appeared at /usr/local/etc
and no man pages were installed. We then went with 2.5 thinking the new
stuff may have introduced errors. This was we had the problem with
the /var /var/lib and /var/lib/lib stuff from the other post when we
expected /usr/local/var/lib. . .

> peace & happiness,
> martin