[Pkg-puppet-devel] Bug#567784: Bug#567784: puppetmaster - Insists in using password auth via TCP to postgresql

[micah anderson]

tag 567784 +moreinfo
thx

On Sun, 31 Jan 2010 13:32:40 +0100, Bastian Blank <waldi at debian.org> wrote:
> puppetmaster insists in using a TCP connection to the postgresql server
> instead of the UNIX socket. The postgresql library hardcodes "localhost"
> to use the UNIX socket and I have explicitely set dbserver to localhost.

This isn't puppetmaster, it is rails. Puppet just passes the
configuration information through, renaming the parameters as follows
(args are what rails sees):

	    args[:host]     = Puppet[:dbserver] unless Puppet[:dbserver].empty?
	    args[:username] = Puppet[:dbuser] unless Puppet[:dbuser].empty?
	    args[:password] = Puppet[:dbpassword] unless Puppet[:dbpassword].empty?
	    args[:database] = Puppet[:dbname]
	    args[:reconnect]= true

	    socket          = Puppet[:dbsocket]
	    args[:socket]   = socket unless socket.empty?

Looking at the rails documentation, it appears that the effect you want
can be obtained by setting the path to the unix socket as the host (so
dbserver, in puppet), with something like this:

<pre>
dbserver = /var/run/postgresql
</pre>

Please try this and update the bug with your results.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20100203/af190a84/attachment.pgp>