Re: [Gnumed-devel] Having trouble with gm-restore_database in Mint 17.3 ... Ubuntu 14.04

[Rogerio Luz Coelho]

Seems I did something with the database before the backup ... maybe I "tryied to clean it more than I should".

When trying to apply the fixups for v19 on my backed up DB here is the error:

===========================================================
Fixing GNUmed database.

This will apply fixups to an existing GNUmed database of
version 19 named "gnumed_v19".
===========================================================

1) applying fixes to database ...
Adjusting PYTHONPATH ...
=======================================
Bootstrapping GNUmed database system...
=======================================
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v19-fixups" in <gnumed_v19> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed database.

It does so by applying all fixup SQL scripts
appropriate to the version of the database.

==> bootstrapping "v19-fixups" ...
The database owner [gm-dbo] will be created.

You will have to provide a new password for it
unless it is pre-defined in the configuration file.

Make sure to remember the password for later use !

Cannot bootstrap bundles.

Please check the log file for details:

  /var/lib/gnumed/server/bootstrap/fixup_db-v19.log

Fixing "gnumed_v19" did not finish successfully.

and the log file:

http://dpaste.com/3BFN95C

Thx ...

Rogerio

2016-04-07 22:50 GMT-03:00 Rogerio Luz Coelho <address@hidden>:

pg_hba.conf:

A whole lot of TEXT ... bla bla bla

#

#
# Database administrative login by Unix domain socket
local   all             postgres                                peer

# TYPE  DATABASE        USER            ADDRESS                 METHOD
# allow anyone knowing the proper password to log into our GNUmed databases:
local   samegroup      +gm-logins                md5


# "local" is for Unix domain socket connections only
local   all             all                                     peer
# IPv4 local connections:
host    all             all             127.0.0.1/32            md5
# IPv6 local connections:
host    all             all             ::1/128                 md5
# Allow replication connections from localhost, by a user with the
# replication privilege.
#local   replication     postgres                                peer
#host    replication     postgres        127.0.0.1/32            md5
#host    replication     postgres        ::1/128                 md5

I have to to a: sudo -u postgres sudo psql -d gnumed_v19 -U rogluz

as 'rogluz' is not a normal user in my system.

results in:

psql: FATAL:  Peer authentication failed for user "rogluz"

Thx Karsten

Rogerio

2016-04-07 6:26 GMT-03:00 Karsten Hilbert <address@hidden>:

On Wed, Apr 06, 2016 at 10:18:03PM -0300, Rogerio Luz wrote:

> So I finally got to restoring my old v19 database in Mint 17.3, which has
> gnumed-server 19.6-1  and gnumed-client  1.4.6+dfsg-1 by Ubuntu.
>
> The restore script seems to work ok without erros, but when I try to
> connect I get :
>
> Unable to connect to database:
>
> PostgreSQL: FATAL:  Peer authentication failed for user "rogluz"
> DSN: dbname=gnumed_v19 port=5432 user=rogluz password=� sslmode=prefer

This seems to point at pg_hba.conf.

Can you (as rogluz, on the console) do:

        $> psql -d gnumed_v19 -U rogluz

What does your pg_hba.conf look like ?

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