Re: [Gnumed-devel] Gnumed install on Debian

[Karsten Hilbert]

> 12. su - root
> 13. su - postgres
> 14. pg_ctl -D /var/lib/postgres/data -l pgsql.log restart
> 15. exit    exit
> 15. ./gnumed/dists/XdtViewer/make-links.sh
Not necessary.

> 16. edit bootstrap-monolitic_core.conf  -> update PgSQL version to 7.4.2 in 
> several places.
Not necessary at all. Its *minimum* postgresql version (and it
should say so. Being fixed.)

> 17. python bootstrap-gm_db_system.py --conf-file=bootstrap-monolitic_core.conf
> 18. enter for password "gnumed" for user gm-dbowner
> 
> Then I get:
> 
> Cannot bootstrap services.
> Please check the log file for details.
> 
> I can not find any log file,
It's location is printed out on the console when you startup
the boostrapping script.

but then by change I saw the following lines 
> in /var/log/messages:
> 
> Mar 13 14:12:53 bahji postgres[628]: [2-1] LOG:  connection received: 
> host=[local] port=
> Mar 13 14:12:53 bahji postgres[628]: [3-1] LOG:  connection authorized: 
> user=postgres database=template1
> Mar 13 14:13:12 bahji postgres[628]: [4-1] ERROR:  user "any-doc" already 
> exists
> Mar 13 14:13:12 bahji postgres[628]: [5-1] ERROR:  user "_any-doc" already 
> exists
> Mar 13 14:13:12 bahji postgres[628]: [6-1] ERROR:  relation 
> "gm_schema_revision" does not exist
> Mar 13 14:13:12 bahji postgres[629]: [2-1] LOG:  connection received: 
> host=[local] port=
> Mar 13 14:13:12 bahji postgres[629]: [3-1] LOG:  connection authorized: 
> user=gm-dbowner database=template1
> Mar 13 14:13:12 bahji postgres[630]: [2-1] LOG:  connection received: 
> host=[local] port=
> Mar 13 14:13:12 bahji postgres[630]: [3-1] LOG:  connection authorized: 
> user=gm-dbowner database=gnumed
> Mar 13 14:13:12 bahji postgres[630]: [4-1] NOTICE:  CREATE TABLE / UNIQUE 
> will 
> create implicit index "gm_schema_revision_filename_key" for table 
> "gm_schema_revision"
> Mar 13 14:13:13 bahji postgres[630]: [5-1] ERROR:  relation 
> "gm_schema_revision" already exists
> 
> So, what am I doing wrong or missing?
Those lines don't signify an error that makes GnuMed bail out.
It must be something else. I have recently removed a spurious
\i gmSchemaRevision.sql from one of the SQL scripts. Maybe you
update from CVS and try again. If it still fails we'd need the
log.

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346