Re: Having trouble with gm-restore_database in Mint 17.3 ... Ubuntu 14.04

Rogerio Luz Coelho <[email protected]> Fri, 8 Apr 2016 20:39:50 -0300
Newsgroups gmane.comp.gnu.medical.devel
Message-ID <CADGYJsyhz+jN51uEbkMLCZdm5OL4GuD4dSYxcxKVAwgzTpDZLQ@mail.gmail.com>
Can I put the password for gm-dbo in the roles sql file at the time I
inspect it for the restore? What else should it have ? SUPERUSER and LOGIN ?

R.

2016-04-08 17:18 GMT-03:00 Karsten Hilbert <[email protected]>:

> On Fri, Apr 08, 2016 at 12:05:38AM -0300, Rogerio Luz wrote:
>
> > Fixing GNUmed database.
> >
> > This will apply fixups to an existing GNUmed database of
> > version 19 named "gnumed_v19".
> > ===========================================================
>
> >   /var/lib/gnumed/server/bootstrap/fixup_db-v19.log
> >
> > Fixing "gnumed_v19" did not finish successfully.
> >
> >
> > and the log file:
> >
> > http://dpaste.com/3BFN95C
>
> The combination of you seemingly having successfully run
> restore script *and* the fixup thinking gm-dbo is missing
> seems to suggest that either both were run against different
> PG clusters or that you may have used a database owner _other
> than_ gm-dbo previously ?
>
> At any rate, what does the *-roles.sql file from the restored
> backup say ? (beware, it does contain passwords)
>
> Karsten
> --
> GPG key ID E4071346 @ eu.pool.sks-keyservers.net
> E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346
>
> _______________________________________________
> Gnumed-devel mailing list
> [email protected]
> https://lists.gnu.org/mailman/listinfo/gnumed-devel
>

_______________________________________________
Gnumed-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/gnumed-devel