Hi, Thank you Greg. To make sure everything could work, I finally set the password in the database "dbpass" column. The good thing is everything started to work perfectly.
So the next step was to make sure both bucardo and postgres could access the file, so I setup two files directly in /etc/ with "chmod 440" and "chown postgres:bucardo". This way, both of them would have read access. Now, I removed the field dbpass, change the path to the pgpass file in the pgpass column, stop/start bucardo, and I end up with the same problem... At least now, I have a temporary working solution so I can start testing, but I would really like to make the pgpass work, as it seems a better/safer approach. Raphaël On Wed, Sep 26, 2012 at 10:50 PM, Greg Sabino Mullane <[email protected]>wrote: > On Wed, Sep 26, 2012 at 11:02:48AM -0400, Raphael Nadeau wrote: > ... > > MCP Warning: Killed (line 44): DBI > > connect('dbname=xxxxx;port=5432;host=xxxxxxxxxxxx','bucardo',...) failed: > > fe_sendauth: no password supplied at /usr/share/perl5/Bucardo.pm line 265 > > pgpass should be working fine. Can you connect via psql using those > same parameters? Is the pgpass file available to the user Bucardo > is running as? You could also rule out other things by putting the > password into the bucardo.db table temporarily. > > -- > Greg Sabino Mullane [email protected] > End Point Corporation > PGP Key: 0x14964AC8 >
_______________________________________________ Bucardo-general mailing list [email protected] https://mail.endcrypt.com/mailman/listinfo/bucardo-general
