SQL-Ledger Homepage

SQL-Ledger User Forum

Forum index page

Log in | Register

Back to index page
Thread view  Board view
clusters(R)

02.06.2015, 15:45
 

Bug in {dbconnect} (General)

Version is 3.0.8 that I am testing...

I have Postgres 9 running on a non-default port as the default was used by Postgres 8.

When I create a new user the user can't login as the {dbconnect} is missing the port parameter. I can't seem to find where that is set. I tried updating the user conf file manually including the members file but the member file would get over written without the port no...so no go...any idea?

clusters(R)

02.06.2015, 18:06

@ clusters
 

Bug in {dbconnect}

Ok...further testing I found the port parameter to be removed from the members file for the user after I did a save preference. I could manually update the members file and the connection will reestablish; however, once I did a save preference again the port parameter will be removed and connection was lost...
so save preference would left out the port parameter of the dbconnect string...

any idea any one please?

Version is 3.0.8 that I am testing...

I have Postgres 9 running on a non-default port as the default was used by
Postgres 8.

When I create a new user the user can't login as the {dbconnect} is missing
the port parameter. I can't seem to find where that is set. I tried
updating the user conf file manually including the members file but the
member file would get over written without the port no...so no go...any
idea?

clusters(R)

02.06.2015, 20:02

@ clusters
 

Bug in {dbconnect}

alright...found the reason was dbport='xxxx' was missing during user creation. added that to the user conf and member files all is well...except for fixing the user creation process...Tim

Ok...further testing I found the port parameter to be removed from the
members file for the user after I did a save preference. I could manually
update the members file and the connection will reestablish; however, once
I did a save preference again the port parameter will be removed and
connection was lost...
so save preference would left out the port parameter of the dbconnect
string...

any idea any one please?

Version is 3.0.8 that I am testing...

I have Postgres 9 running on a non-default port as the default was used
by
Postgres 8.

When I create a new user the user can't login as the {dbconnect} is
missing
the port parameter. I can't seem to find where that is set. I tried
updating the user conf file manually including the members file but the
member file would get over written without the port no...so no go...any
idea?

Brian Dunn(R)

03.06.2015, 17:40

@ clusters
 

Upgraded Postgres: changed port number, not able to connect

I have Postgres 9 running on a non-default port as the default was used by
Postgres 8.

On my system, I only keep the newer version of Postgres. The newer version installs with a new port (5433 in my case), as you have seen, while the older version still uses the default (5432 in my case).

When the new version of Postgres was installed, hopefully the clusters were upgraded at that time. If not, do so now.

Verify that psql can see the new database in the new Postgres.

Remove the older version of Posgres.

Edit postgresql.conf to make port = 5432

clusters(R)

04.06.2015, 16:21

@ Brian Dunn
 

Upgraded Postgres: changed port number, not able to connect

Thanks for the info. I didn't even know Postgres 9 uses port 5433 instead of the standard 5432. Well, 8 is our production system and it is compiled with Slony so I was just testing 9 and assigned it a different port no and running multiple instances. We are still running SL 2.8 and I am planning on upgrading SL/Slony/Postgres together.

I think the issue here is with a bug in the HR module and that when creating a user the conf file is missing the dbport parameter...



I have Postgres 9 running on a non-default port as the default was used
by
Postgres 8.

On my system, I only keep the newer version of Postgres. The newer version
installs with a new port (5433 in my case), as you have seen, while the
older version still uses the default (5432 in my case).

When the new version of Postgres was installed, hopefully the clusters were
upgraded at that time. If not, do so now.

Verify that psql can see the new database in the new Postgres.

Remove the older version of Posgres.

Edit postgresql.conf to make port = 5432

clusters(R)

09.06.2015, 17:49

@ clusters
 

Bug in {dbconnect}

Ok...believe I found the issue.

In bin/mozilla/hr.pl line no. 1182 add dbport to the list...

for (qw(company dateformat dbconnect dbdriver dbname dbhost dboptions dbpasswd dbuser dbport numberformat)) { $m{$_} = $myconfig{$_} }



Version is 3.0.8 that I am testing...

I have Postgres 9 running on a non-default port as the default was used by
Postgres 8.

When I create a new user the user can't login as the {dbconnect} is missing
the port parameter. I can't seem to find where that is set. I tried
updating the user conf file manually including the members file but the
member file would get over written without the port no...so no go...any
idea?

Back to index page
Thread view  Board view
986 Postings in 325 Threads, 327 registered users, 116 users online (0 registered, 116 guests)
SQL-Ledger User Forum | Admin contact
RSS-Feed
powered by my little forum