0001154: No admin password for PostgreSQL in Ubuntu/Debian

(0001016)
jpabloae (reporter)
2007-04-30 22:59
edited on: 2008-06-12 09:18

Logged In: YES
user_id=1603191
Originator: NO

This is a common issue in most default PostgreSQL installations. A possible workaround for the users:
1) Edit pg_hba.conf (located in /var/lib/postgresql/data or similar) and replace all the "password" or "md5" strings by "trust". Eg:

local all all md5
into
local all all trust

2) Restart postresql: /etc/init.d/postgresql restart
3) Change postgres' password:

psql -d postgres -U postgres
alter role postgres with password 'new_password';
\q

4) Open pg_hba.conf again and replace all the "trust" strings by "md5".
5) Restart postgresql.

(0001017)
user71
2007-05-24 15:48
edited on: 2008-06-12 09:18

Logged In: YES
user_id=1318257
Originator: NO

You can simple change PostgresSQL admin password.
$ sudo su - postgres
$ alter role postgres with password '123';
$ exit

(0001018)
user71
2007-05-24 16:48
edited on: 2008-06-12 09:18

Logged In: YES
user_id=1318257
Originator: NO

Pass something in previous post.
This is right way:
$ sudo su - postgres
$ psql -U postgres
# alter role postgres with password '123';
# \q
$ exit

(0001019)
user11
2007-11-11 15:11
edited on: 2008-06-12 09:18

Logged In: YES
user_id=1505407
Originator: YES

I'm re-opening this bug. The installer still does not work correctly. Jordi,

(0001020)
villind (developer)
2007-12-12 14:22
edited on: 2008-06-12 09:18

Logged In: YES
user_id=61737
Originator: NO

I would suggest instead that there would be option to install to an existing database & database user. Then you don't need to care about this, but just expect that there is an existing database (or at least database user).

See feature request: https://sourceforge.net/tracker/index.php?func=detail&aid=1761370&group_id=162271&atid=823132 [^]

(0004743)
user71
2005-06-01 00:00
edited on: 2008-06-12 09:43

This bug was originally reported in SourceForge bug tracker and then migrated to Mantis.

You can see the original bug report in:
https://sourceforge.net/support/tracker.php?aid=1710008 [^]

(0010225)
jpabloae (reporter)
2008-11-13 06:51

Thank you for the bug report.

However, I close the issue because we are not having an installer for 2.50 and future releases.

Issue History
Date Modified	Username	Field	Change
2008-06-12 10:04	jpabloae	Project	Openbravo ERP => @5@
2008-06-12 11:56	jpabloae	Category	A.Installation & Platform => Installer
2008-11-13 06:51	jpabloae	Status	new => closed
2008-11-13 06:51	jpabloae	Note Added: 0010225
2008-11-13 06:51	jpabloae	Resolution	open => out of date
2008-11-25 21:41	pjuvara	Sticky Issue	No => Yes
2008-11-25 21:43	pjuvara	Project	@5@ => Openbravo ERP
2008-11-25 21:45	pjuvara	Category	Installer => K. Packaging
2008-11-25 21:47	pjuvara	Sticky Issue	Yes => No

Notes
(0001016) jpabloae (reporter) 2007-04-30 22:59 edited on: 2008-06-12 09:18	Logged In: YES user_id=1603191 Originator: NO This is a common issue in most default PostgreSQL installations. A possible workaround for the users: 1) Edit pg_hba.conf (located in /var/lib/postgresql/data or similar) and replace all the "password" or "md5" strings by "trust". Eg: local all all md5 into local all all trust 2) Restart postresql: /etc/init.d/postgresql restart 3) Change postgres' password: psql -d postgres -U postgres alter role postgres with password 'new_password'; \q 4) Open pg_hba.conf again and replace all the "trust" strings by "md5". 5) Restart postgresql.

(0001017) user71 2007-05-24 15:48 edited on: 2008-06-12 09:18	Logged In: YES user_id=1318257 Originator: NO You can simple change PostgresSQL admin password. $ sudo su - postgres $ alter role postgres with password '123'; $ exit

(0001018) user71 2007-05-24 16:48 edited on: 2008-06-12 09:18	Logged In: YES user_id=1318257 Originator: NO Pass something in previous post. This is right way: $ sudo su - postgres $ psql -U postgres # alter role postgres with password '123'; # \q $ exit

(0001019) user11 2007-11-11 15:11 edited on: 2008-06-12 09:18	Logged In: YES user_id=1505407 Originator: YES I'm re-opening this bug. The installer still does not work correctly. Jordi,

(0001020) villind (developer) 2007-12-12 14:22 edited on: 2008-06-12 09:18	Logged In: YES user_id=61737 Originator: NO I would suggest instead that there would be option to install to an existing database & database user. Then you don't need to care about this, but just expect that there is an existing database (or at least database user). See feature request: https://sourceforge.net/tracker/index.php?func=detail&aid=1761370&group_id=162271&atid=823132 [^]

(0004743) user71 2005-06-01 00:00 edited on: 2008-06-12 09:43	This bug was originally reported in SourceForge bug tracker and then migrated to Mantis. You can see the original bug report in: https://sourceforge.net/support/tracker.php?aid=1710008 [^]

(0010225) jpabloae (reporter) 2008-11-13 06:51	Thank you for the bug report. However, I close the issue because we are not having an installer for 2.50 and future releases.

Relationships [ Relation Graph ] [ Dependency Graph ]