Make install fails - using postgresql for db

I’m having identical symptoms with the user in the following email.
Unfortuneatly, what fixed his problem doesn’t fix mine.
http://lists.fsck.com/pipermail/rt-users/2001-September/004251.html

[rt-2-0-11]# make install
mkdir -p //web/rt2/bin
mkdir -p //web/rt2/WebRT/data
mkdir -p //web/rt2/WebRT/sessiondata
mkdir -p //web/rt2/etc
mkdir -p //web/rt2/lib
mkdir -p //web/rt2/WebRT/html
mkdir -p //web/rt2/local/WebRT/html
/usr/bin/perl tools/initdb ‘Pg’ ‘/usr/local/pgsql’ ‘localhost’ ‘’
‘postgres’ ‘rt2’ create
Now creating a database for RT.
Enter the Pg password for postgres:
Creating Pg database rt2.
DBI->connect(dbname=template1;host=localhost) failed: PQconnectPoll() –
connect() failed: Connectio
n refused at /usr/local/lib/perl5/site_perl/5.6.1/DBIx/DataSource/Driver.pm
line 74
PQconnectPoll() – connect() failed: Connection refused at
/usr/local/lib/perl5/site_perl/5.6.1/DBIx
/DataSource/Driver.pm line 74, line 1.
make: *** [createdb] Error 255
[rt-2-0-11]#

Any ideas?

Thanks,
–Mark

Deleting the host name from the Makefile fixed my problem.

DB_HOST =

Please update the install docs to indicate that this might be a good idea.
It would have saved me HOURS.-----Original Message-----
From: Swayne, Mark A [mailto:mark.a.swayne@xo.com]
Sent: Thursday, February 07, 2002 12:12 PM
To: rt-users@lists.fsck.com
Subject: [rt-users] make install fails - using postgresql for db.

I’m having identical symptoms with the user in the following email.
Unfortuneatly, what fixed his problem doesn’t fix mine.
http://lists.fsck.com/pipermail/rt-users/2001-September/004251.html

[rt-2-0-11]# make install
mkdir -p //web/rt2/bin
mkdir -p //web/rt2/WebRT/data
mkdir -p //web/rt2/WebRT/sessiondata
mkdir -p //web/rt2/etc
mkdir -p //web/rt2/lib
mkdir -p //web/rt2/WebRT/html
mkdir -p //web/rt2/local/WebRT/html
/usr/bin/perl tools/initdb ‘Pg’ ‘/usr/local/pgsql’ ‘localhost’ ‘’
‘postgres’ ‘rt2’ create
Now creating a database for RT.
Enter the Pg password for postgres:
Creating Pg database rt2.
DBI->connect(dbname=template1;host=localhost) failed: PQconnectPoll() –
connect() failed: Connectio
n refused at /usr/local/lib/perl5/site_perl/5.6.1/DBIx/DataSource/Driver.pm
line 74
PQconnectPoll() – connect() failed: Connection refused at
/usr/local/lib/perl5/site_perl/5.6.1/DBIx
/DataSource/Driver.pm line 74, line 1.
make: *** [createdb] Error 255
[rt-2-0-11]#

Any ideas?

Thanks,
–Mark

rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Way back in February, Swayne, Mark A (mark.a.swayne@xo.com) wrote
this regarding getting RT to work with PostgreSQL connections via UNIX
domain sockets:

Deleting the host name from the Makefile fixed my problem.

DB_HOST =

Please update the install docs to indicate that this might be a good idea.
It would have saved me HOURS.

Please listen to your users! :frowning:

I started installing RT 2.0.15 with PostgreSQL this morning, and if
you had updated the docs as Mark suggested, you would have saved me
hours too :frowning: It’s somewhat dampened my enthusiasm for finally getting
round to trying out what I already know by reputation to be a great
product. Sorry to delurk on a negative note, but it really does make
a big difference when sticking points like this are well-documented.

I suspect this is not the only PostgreSQL-related issue. I could well
be wrong, because it’s the first time I’ve used PostgreSQL too, but
here’s my take on things:

The comment in Makefile regarding DB_DBA:

For Pg, you probably want ‘postgres’

is correct, I think. However, it’s not at all clear what the
corresponding DB_DBA_PASSWORD should be. Admittedly this is more
of a PostgreSQL issue. Anyone know the default password, if there
even is one? If not, the following is even more relevant:

initdb calls prompt_for_dba_password() regardless of whether
DB_DBA_PASSWORD is set in the Makefile or not. Furthermore, I
don’t believe it caters for the possibility that you might not
actually want to use passwords - for instance if you are making
use of SO_PEERCRED for UNIX domain sockets, where just having the
relevant euid is considered sufficient authentication.

So I’ve ended up configuring PostgreSQL for md5 password-based
authentication, even though I’d much rather use SO_PEERCRED in this
instance, which avoids the need for passwords lying around in text
files.

Thoughts?

Adam Spiers ## musician & hacker ## me@adamspiers.org ## http://tigerpig.org

$@=>$_=q^{$Just =bless{},’$another ';"$Perl ::$hacker,"}=sub{print$%[$.++];$
},eval join+v45.62,(q)$q ))x v54^,s.(?<=$)\w
[\s,].f if+push@%,$&.sixmegs,eval