|
From: | Rogerio Luz Coelho |
Subject: | Re: [Gnumed-devel] Having trouble with gm-restore_database in Mint 17.3 ... Ubuntu 14.04 |
Date: | Sat, 23 Apr 2016 22:32:21 -0300 |
Hi Rogerio !
> > got this after bootstrap of a new gnumed_v19 in a NEW main cluster(after pg_dumpcluster / pg_createcluster)
> >
> > List of databases
> > Name | Owner | Encoding | Collate | Ctype | Access privileges
> >------------+----------+----------+-------------+-------------+-----------------------
> > gnumed_v18 | gm-dbo | UTF8 | en_US.UTF-8 | en_US.UTF-8 |
> > gnumed_v19 | gm-dbo | UTF8 | en_US.UTF-8 | en_US.UTF-8 |
> > postgres | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 |
> > template0 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/postgres +
> > | | | | | postgres=CTc/postgres
> > template1 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/postgres +
> > | | | | | postgres=CTc/postgres
> > (5 rows)
>
> Looks spot on. First things would be to
>
> - re-check pg_hba.conf for the proper position of the "samerole gm-logins md5" line
> - dropdb gnumed_v19 (because we want to restore)
> - check out whether any password is set for gm-dbo:
> psql -d gnumed_v18 -U gm-dbo
> - if an unknown password is set, reset it to something known
> connect as user postgres
> alter role 'gm-dbo' encrypted password 'your-new-password';
> - try connecting as gm-dbo
> - try connecting as any-doc (default password should be any-doc)
>
> and check back here.
Any news ? Help needed ?
Karsten
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
_______________________________________________
Gnumed-devel mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/gnumed-devel
[Prev in Thread] | Current Thread | [Next in Thread] |