[Bucardo-general] Stalled sync status

Jonathan Brinkman jb at blackskytech.com
Wed Nov 19 15:19:21 UTC 2014


Agree this is frustrating. We're contemplating downgrading to Bucardo4 until
this is resolved... :(
We found you need to deactivate the sync, then activate it, then kick it
Then maybe do that again. Then stop and start bucardo. 
Then it seems to wake up and behave. 
It does NOT like postgres to stop!
And like he said the Status shows good although the "Last Good" doesn't
change (b/c it's stalled). Status should read "Stalled" at a minimum
(it does if you do bucardo status syncnamehere)



-----Original Message-----
From: bucardo-general-bounces at bucardo.org
[mailto:bucardo-general-bounces at bucardo.org] On Behalf Of
bucardo-general-request at bucardo.org
Sent: Tuesday, November 18, 2014 12:38 AM
To: bucardo-general at bucardo.org
Subject: Bucardo-general Digest, Vol 86, Issue 5

Send Bucardo-general mailing list submissions to
	bucardo-general at bucardo.org

To subscribe or unsubscribe via the World Wide Web, visit
	https://mail.endcrypt.com/mailman/listinfo/bucardo-general
or, via email, send a message with subject or body 'help' to
	bucardo-general-request at bucardo.org

You can reach the person managing the list at
	bucardo-general-owner at bucardo.org

When replying, please edit your Subject line so it is more specific than
"Re: Contents of Bucardo-general digest..."


Today's Topics:

   1. Stalled sync status (Hans van der Riet)
   2. Re: Stalled sync status (Greg Sabino Mullane)
   3. Bucardo unable to authenticate password when	running.
      (Hadri Rahman)
   4. (no subject) (Hadri Rahman)
   5. Re: (no subject) (Hans van der Riet)
   6. Re: (no subject) (Hadri Rahman)


----------------------------------------------------------------------

Message: 1
Date: Tue, 11 Nov 2014 23:23:27 +0100
From: Hans van der Riet <hans at electude.nl>
To: bucardo-general at bucardo.org
Subject: [Bucardo-general] Stalled sync status
Message-ID: <54628C5F.4050900 at electude.nl>
Content-Type: text/plain; charset=utf-8; format=flowed

Hi,

Running Bucardo 5.1.1, I understand syncs now can get 'stalled' so a broken
sync no longer blocks the other syncs from being updated. Doing some
experiments I noticed the following:

When I shut down PostgreSQL on one of the nodes in a sync, the KID exits and
the MCP marks the affected db and sync as stalled. New KIDs get started, and
exit as long as PostgreSQL is down. Running 'bucardo status' says the state
of the sync is bad.

Then I start PostgreSQL again. The KID finished the syncrun and 'bucardo
status' says the state of the sync is good.

Bucardo keeps on running, but nothing happens anymore because the sync is
still stalled. 'bucardo status' reports the state of the sync as good. Doing
a restart marks the sync and db again as active and everything returns to
normal.

Is restarting the only way to 'unstall' a sync? Is the best/only way to
monitor if a sync is stalled doing a 'select status from sync'?

Kind regards
--
Hans van der Riet


------------------------------

Message: 2
Date: Tue, 11 Nov 2014 21:08:28 -0500
From: Greg Sabino Mullane <greg at endpoint.com>
To: Hans van der Riet <hans at electude.nl>
Cc: bucardo-general at bucardo.org
Subject: Re: [Bucardo-general] Stalled sync status
Message-ID: <20141112020827.GC18797 at broken.home>
Content-Type: text/plain; charset="us-ascii"

On Tue, Nov 11, 2014 at 11:23:27PM +0100, Hans van der Riet wrote:
> Running Bucardo 5.1.1, I understand syncs now can get 'stalled' so a
> broken sync no longer blocks the other syncs from being updated.
...
> Bucardo keeps on running, but nothing happens anymore because the
> sync is still stalled. 'bucardo status' reports the state of the
> sync as good. Doing a restart marks the sync and db again as active
> and everything returns to normal.
> 
> Is restarting the only way to 'unstall' a sync? Is the best/only way
> to monitor if a sync is stalled doing a 'select status from sync'?

A sync should 'resurrect' itself after a certain time period, but 
there are some bugs in that part of the code: I'm working on that 
at the moment. As far as detection, yes, but other suggestions 
welcome as we've not really considered good ways to do that yet.

-- 
Greg Sabino Mullane greg at endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: Digital signature
URL:
<https://mail.endcrypt.com/pipermail/bucardo-general/attachments/20141111/58
d60fe1/attachment-0001.sig>

------------------------------

Message: 3
Date: Wed, 12 Nov 2014 16:42:34 +0800
From: Hadri Rahman <hadri90 at gmail.com>
To: "bucardo-general at bucardo.org" <bucardo-general at bucardo.org>
Subject: [Bucardo-general] Bucardo unable to authenticate password
	when	running.
Message-ID:
	<CALwTMdq=h5=pi8vUnRTXXVLPg=VF8ejSFd=djcxU1Wgjm+s3UQ at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

So, I was able to install Bucardo on computer, but when I tried to run it
by typing "bucardo start" or when I try to perform synchronization, I would
get this error message:

DBI connect('dbname=bucardo;host=localhost;port5432', 'bucardo',...)
failed: FATAL: password authentication failed for user "bucardo"
FATAL: password authentication failed for user "bucardo" at
/usr/local/bin/bucardo line 296

I've changed my password for user bucardo, and I'm sure that the .pgpass
file has been edited to reflect the changes and was given the sufficient
permissions, but I'm still getting this error message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://mail.endcrypt.com/pipermail/bucardo-general/attachments/20141112/e4
951e2d/attachment-0001.html>

------------------------------

Message: 4
Date: Mon, 17 Nov 2014 16:08:19 +0800
From: Hadri Rahman <hadri90 at gmail.com>
To: "bucardo-general at bucardo.org" <bucardo-general at bucardo.org>
Subject: [Bucardo-general] (no subject)
Message-ID:
	<CALwTMdoGB=arjHBBLWYABaLanoQ2LCdyiqrUwRa3DBaCxY_j+g at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

So I've installed Bucardo onto my system, but whenever I try to perform a
sync or running it in general, I would get the error message:

DBI connect('dbname=bucardo;host=localhost;port5432', 'bucardo',...)
failed: FATAL: password authentication failed for user "bucardo"
FATAL: password authentication failed for user "bucardo" at
/usr/local/bin/bucardo line 296

I've checked and confirmed that the user "Bucardo" is in the PostgreSQL
database, and that the passwords in both the database and .pgpass are
correct. I've searched online and it was suggested that there might be a
problem in my pg_hba.conf file. The contents of the file are as follows:

#Database administrative login by Unix domain socket
local     all        postgres         peer
#"local" is for Unix domain socket connections only
local     all        all              peer
#IPv4
local     all        all     127.0.0.1/32         md5
#IPv6
local     all        all     ::1/128         peer
#Allow replication connections from localhost:
host     replication rep     192.168.0.111/32     md5
local    bucardo     bucardo                      md5

I've tried changing the authentication method for user "bucardo" from md5
to trust and ident, but I'm still getting the same error. Any help and
suggestion would be appreciated.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://mail.endcrypt.com/pipermail/bucardo-general/attachments/20141117/c3
0c8a0e/attachment-0001.html>

------------------------------

Message: 5
Date: Mon, 17 Nov 2014 22:40:19 +0100
From: Hans van der Riet <hans at electude.nl>
To: bucardo-general at bucardo.org
Subject: Re: [Bucardo-general] (no subject)
Message-ID: <546A6B43.2080504 at electude.nl>
Content-Type: text/plain; charset=windows-1252; format=flowed

On 17-11-14 09:08, Hadri Rahman wrote:
> So I've installed Bucardo onto my system, but whenever I try to perform
> a sync or running it in general, I would get the error message:
>
> DBI connect('dbname=bucardo;host=localhost;port5432', 'bucardo',...)
> failed: FATAL: password authentication failed for user "bucardo"
> FATAL: password authentication failed for user "bucardo" at
> /usr/local/bin/bucardo line 296

You configured Bucardo to connect to PostgreSQL over TCP/IP. TCP/IP 
connections are configured in pg_hba.conf using the 'host' connection 
type. Your pg_hba.conf has no entry to match your Bucardo connection.

> #IPv4
> local     all        all 127.0.0.1/32 <http://127.0.0.1/32>         md5
> #IPv6
> local     all        all     ::1/128         peer

These lines do nothing, since local connections are already handled by 
the second entry in your file. For TCP/IP connections you should use:

# IPv4 local connections:
host    all             all             127.0.0.1/32            md5
# IPv6 local connections:
host    all             all             ::1/128                 md5

Note that you can only use the peer method on local connections, so for 
IPv6 you should use something different like md5.

> #Allow replication connections from localhost:
> host     replication rep 192.168.0.111/32 <http://192.168.0.111/32>
md5
> local    bucardo     bucardo                      md5

This last line is intended when Bucardo uses a Unix domain socket (if 
you set 'no host' when you install Bucardo). You can remove it when you 
use TCP/IP.
Note that to make a local connection work, you should put this line 
above the 'local all all peer' line, otherwise peer authentication will 
be used (and will fail). PostgreSQL looks from top to bottom for the 
first matching entry in pg_hba.conf. Probably you also want Bucardo to 
connect to other database(s) as well, something like this:

local   all             postgres                                peer
local   all             bucardo                                 md5
local   all             all                                     peer


Kind regards,
-- 
Hans van der Riet


------------------------------

Message: 6
Date: Tue, 18 Nov 2014 13:09:57 +0800
From: Hadri Rahman <hadri90 at gmail.com>
To: Hans van der Riet <hans at electude.nl>
Cc: "bucardo-general at bucardo.org" <bucardo-general at bucardo.org>
Subject: Re: [Bucardo-general] (no subject)
Message-ID:
	<CALwTMdrymGAeGVw3XLapNFPX3SUbsa6gN5CMTa8r=oOmwWLQ5w at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

So I've followed the advice given and changed the contents of pg_hba.conf
to this:

#Database administrative login by Unix domain socket
local     all        postgres         peer
local     all        bucardo          md5
#"local" is for Unix domain socket connections only
local     all        all         peer
#IPv4
local     all        all     127.0.0.1/32         md5
#IPv6
local     all        all     ::1/128         md5
#Allow replication connections from localhost:
host     replication rep     192.168.0.111/32     md5

And I'm still getting the same error message.

Also, from what I remember, when I installed bucardo, the host was set to
"localhost"

On Tue, Nov 18, 2014 at 5:40 AM, Hans van der Riet <hans at electude.nl> wrote:

> On 17-11-14 09:08, Hadri Rahman wrote:
>
>> So I've installed Bucardo onto my system, but whenever I try to perform
>> a sync or running it in general, I would get the error message:
>>
>> DBI connect('dbname=bucardo;host=localhost;port5432', 'bucardo',...)
>> failed: FATAL: password authentication failed for user "bucardo"
>> FATAL: password authentication failed for user "bucardo" at
>> /usr/local/bin/bucardo line 296
>>
>
> You configured Bucardo to connect to PostgreSQL over TCP/IP. TCP/IP
> connections are configured in pg_hba.conf using the 'host' connection
type.
> Your pg_hba.conf has no entry to match your Bucardo connection.
>
>  #IPv4
>> local     all        all 127.0.0.1/32 <http://127.0.0.1/32>         md5
>> #IPv6
>> local     all        all     ::1/128         peer
>>
>
> These lines do nothing, since local connections are already handled by the
> second entry in your file. For TCP/IP connections you should use:
>
> # IPv4 local connections:
> host    all             all             127.0.0.1/32            md5
> # IPv6 local connections:
> host    all             all             ::1/128                 md5
>
> Note that you can only use the peer method on local connections, so for
> IPv6 you should use something different like md5.
>
>  #Allow replication connections from localhost:
>> host     replication rep 192.168.0.111/32 <http://192.168.0.111/32>
>>  md5
>> local    bucardo     bucardo                      md5
>>
>
> This last line is intended when Bucardo uses a Unix domain socket (if you
> set 'no host' when you install Bucardo). You can remove it when you use
> TCP/IP.
> Note that to make a local connection work, you should put this line above
> the 'local all all peer' line, otherwise peer authentication will be used
> (and will fail). PostgreSQL looks from top to bottom for the first
matching
> entry in pg_hba.conf. Probably you also want Bucardo to connect to other
> database(s) as well, something like this:
>
> local   all             postgres                                peer
> local   all             bucardo                                 md5
> local   all             all                                     peer
>
>
> Kind regards,
> --
> Hans van der Riet
> _______________________________________________
> Bucardo-general mailing list
> Bucardo-general at bucardo.org
> https://mail.endcrypt.com/mailman/listinfo/bucardo-general
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://mail.endcrypt.com/pipermail/bucardo-general/attachments/20141118/62
e25e88/attachment.html>

------------------------------

_______________________________________________
Bucardo-general mailing list
Bucardo-general at bucardo.org
https://mail.endcrypt.com/mailman/listinfo/bucardo-general


End of Bucardo-general Digest, Vol 86, Issue 5
**********************************************



More information about the Bucardo-general mailing list