[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] Problems calling or obtaining passwords from .pgpass
From: |
Sebastian Hilbert |
Subject: |
Re: [Gnumed-devel] Problems calling or obtaining passwords from .pgpass |
Date: |
Fri, 22 Nov 2013 09:11:30 +0100 |
User-agent: |
KMail/4.11.2 (Linux/3.11.0-14-generic; KDE/4.11.2; i686; ; ) |
Am Freitag, 22. November 2013, 08:07:07 schrieb Busser, Jim:
> On 2013-11-21, at 2:28 PM, Jim Busser <address@hidden> wrote:
> > Should I modify line 8 of the vaarious conf files
> >
> > interactive = yes
> >
> > to 'no'?
>
> I tried the above, and could not see that it made any difference. In spite
> of my .pgpass file, the log still complained as follows …
>
> 2013-11-21 23:53:05 INFO gm.bootstrapper
> (./bootstrap_gm_db_system.py::bootstrap() #1250): bootstrapping bundle
> [v18_fixups-pre_v19] 2013-11-21 23:53:05 DEBUG gm.cfg
> (/private/var/root/gnumed-server.19.1/Gnumed/pycommon/gmCfg2.py::get()
> #391): option [bundle v18_fixups-pre_v19::database a$ 2013-11-21 23:53:05
> INFO gm.bootstrapper (./bootstrap_gm_db_system.py::__init__() #518):
> bootstrapping database [gnumed_v19] 2013-11-21 23:53:05 DEBUG gm.cfg
> (/private/var/root/gnumed-server.19.1/Gnumed/pycommon/gmCfg2.py::get()
> #391): option [database gnumed_v19::override name by$ 2013-11-21 23:53:05
> INFO gm.bootstrapper (./bootstrap_gm_db_system.py::__init__() #527):
> environment variable [GM_CORE_DB] is not set, using database name $
> 2013-11-21 23:53:05 DEBUG gm.cfg
> (/private/var/root/gnumed-server.19.1/Gnumed/pycommon/gmCfg2.py::get()
> #391): option [database gnumed_v19::name] found in s$ 2013-11-21 23:53:05
> INFO gm.bootstrapper (./bootstrap_gm_db_system.py::__init__() #544):
> bootstrapping database [gnumed_v19] alias "gnumed_v19" 2013-11-21 23:53:05
> DEBUG gm.cfg
> (/private/var/root/gnumed-server.19.1/Gnumed/pycommon/gmCfg2.py::get()
> #391): option [database gnumed_v19::server alias] fo$ 2013-11-21 23:53:05
> DEBUG gm.cfg
> (/private/var/root/gnumed-server.19.1/Gnumed/pycommon/gmCfg2.py::get()
> #391): option [database gnumed_v19::template databas$ 2013-11-21 23:53:05
> INFO gm.bootstrapper (./bootstrap_gm_db_system.py::__init__() #303):
> bootstrapping server [local host] 2013-11-21 23:53:05 DEBUG gm.cfg
> (/private/var/root/gnumed-server.19.1/Gnumed/pycommon/gmCfg2.py::get()
> #391): option [server local host::super user alias] $ 2013-11-21 23:53:05
> DEBUG gm.cfg
> (/private/var/root/gnumed-server.19.1/Gnumed/pycommon/gmCfg2.py::get()
> #391): option [user postgres::name] found in source $ 2013-11-21 23:53:05
> DEBUG gm.cfg
> (/private/var/root/gnumed-server.19.1/Gnumed/pycommon/gmCfg2.py::get()
> #391): option [user postgres::password] found in sou$ 2013-11-21 23:53:05
> WARNING gm.bootstrapper (./bootstrap_gm_db_system.py::__init__() #296):
> cannot get password for database user [postgres] 2013-11-21 23:53:05 ERROR
> gm.bootstrapper (./bootstrap_gm_db_system.py::bootstrap() #1261):
> Cannot bootstrap bundle [v18_fixups-pre_v19].
>
> -- Jim
>
I assume setting interactive to no tells the bootstraper to not ask for it in
the console.
Is it possible that .pgpass needs to be kept in a different location ? For
Windows I seem to remember something like that.
Sebastian