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

[Jelmer Vernooij]

It depends on the init script you're using. The init script shipped with ctdb upstream seems to load different files depending on the distribution. You might have to manually create those files, such as /etc/sysconfig/ctdb.

Jelmer

On 9 August 2014 15:24:39 BST, steve <steve at steve-ss.com> wrote:
>On Sat, 2014-08-09 at 15:47 +0200, Jelmer Vernooij wrote:
>> On Sat, Aug 09, 2014 at 03:29:23PM +0200, steve wrote:
>> > On Sat, 2014-08-09 at 19:25 +1000, Martin Schwenke wrote:
>> > > On Sun, 27 Jul 2014 13:26:56 +0200, steve <steve at steve-ss.com>
>wrote:
>> > > 
>> > > > The strange thing is, ctdb seems to be working in 2 folders.
>/var/ctdb
>> > > > and /var/lib/lib/ctdb
>> > > 
>> > > Yeah, the way we set CTDB_VARDIR (if it is unset) is very weak. 
>We
>> > > really should do something smarter.
>> > > 
>> > > Try setting it in /etc/sysconfig/ctdb to point to wherever you
>expect it
>> > > to be. I guess that is probably "/var/lib/lib/ctdb".
>> > > 
>> > > peace & happiness,
>> > > martin
>> > 
>> > Hi
>> > If we build from source, we don't have /etc/sysconfig/ctdb. If we
>build
>> > on Ubuntu, we don't even have /etc/sysconfig.
>> > 
>> 
>> /etc/sysconfig is a RedHat-ism. On Debian-based systems the
>equivalent is probably /etc/default/ctdb.
>> 
>> Cheers,
>> 
>> Jelmer 
>Neither are either created nor documented on a build and make install
>from source.