Re: [Gnumed-devel] trying to bootstrap database on Mac " Cannot bootstrap bundles."

[Sebastian Hilbert]

Am Montag 05 Juli 2010, 21:35:46 schrieb Jim Busser:
> On 2010-07-01, at 12:05 AM, Karsten Hilbert wrote:
> 
> I *think* the newest bootstrapper as recently checked-in (to master) --
> supplemented by my uncommenting prompts for postgres password -- works
> even despite letting the downloaded master.tgz reside in user space (and
> not, as Sebastian previously found necessary, to copy it to /tmp/).
>

We have made that possible today. Sorry for not properly communicating this.
Karsten has found a way to bootstrap without moving the files to /tmp
 
> However, in regard to the need (or lack of need) for
> 
>       local   samegroup   +gm-logins   md5
> 
> which was missing from my freshly-reinstalled postgres, the bottom of the
> bootstrap log yielded the following, in which it seemed to look for
> 
>       regex: local.*samegroup.*\+gm-logins
> 
What is this ?

> making me wonder...was that just for information, or are the warnings
> relevant?
> 
The + gm-logins stuff is not necessary for bootstraping. It is necessary for 
clients being able to connect.


> ********************************
> 
> 2010-07-05 12:03:30  INFO      gm.bootstrapper
> (./bootstrap_gm_db_system.py::connect() #245): trying DB connection to
> gnumed_v14 on localhost as postgres 2010-07-05 12:03:30  DEBUG     gm.db
> (/Users/djb/Downloads/gnumed-gnumed/gnumed/gnumed/Gnumed/pycommon/gmPG2.py
> ::get_raw_connection() #1204): new database connection, backend PID: 21975,
> readonly: False 2010-07-05 12:03:30  DEBUG     gm.db
> (/Users/djb/Downloads/gnumed-gnumed/gnumed/gnumed/Gnumed/pycommon/gmPG2.py
> ::get_raw_connection() #1241): access mode [READ WRITE] 2010-07-05 12:03:30
>  DEBUG     gm.db
> (/Users/djb/Downloads/gnumed-gnumed/gnumed/gnumed/Gnumed/pycommon/gmPG2.py
> ::get_connection() #1304): client string encoding [UTF8], isolation level
> [serializable], time zone [America/Dawson], datestyle [ISO],
> sql_inheritance [ON] 2010-07-05 12:03:30  INFO      gm.bootstrapper
> (./bootstrap_gm_db_system.py::connect() #256): successfully connected
> 2010-07-05 12:03:30  INFO      gm.bootstrapper
> (./bootstrap_gm_db_system.py::check_holy_auth_line() #893): hba file:
> /Library/PostgreSQL/8.4/data/pg_hba.conf 2010-07-05 12:03:30  INFO     
> gm.bootstrapper (./bootstrap_gm_db_system.py::check_holy_auth_line()
> #912): did not find standard GNUmed authentication directive in
> pg_hba.conf 2010-07-05 12:03:30  INFO      gm.bootstrapper
> (./bootstrap_gm_db_system.py::check_holy_auth_line() #913): regex:
> local.*samegroup.*\+gm-logins 2010-07-05 12:03:30  WARNING  
> gm.bootstrapper (./bootstrap_gm_db_system.py::main() #1470): open
> connection detected: database.__connect_owner_to_db via
> database.__connect_superuser_to_db 2010-07-05 12:03:30  WARNING  
> gm.bootstrapper (./bootstrap_gm_db_system.py::main() #1471): <connection
> object at 0x1013a7260; dsn: 'dbname=gnumed_v14 port=5432 user=postgres
> password=xxxxxxxx sslmode=prefer', closed: 0> 2010-07-05 12:03:30  WARNING
>   gm.bootstrapper (./bootstrap_gm_db_system.py::main() #1472): closing
> connection 2010-07-05 12:03:30  INFO      gm.bootstrapper
> (./bootstrap_gm_db_system.py::main() #1475): shutdown
> 
> 
Can you send the log file ? Are you saying it bootstraped a v14 database but 
you found those messages and are wondering if they pose a problem ?

If so can you connect to the local database ?

Sebastian