gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] installing and using gnumed


From: Karsten Hilbert
Subject: Re: [Gnumed-devel] installing and using gnumed
Date: Fri, 31 Oct 2003 21:02:15 +0100
User-agent: Mutt/1.3.22.1i

> Ok, I tried that after fixing what was wrong in my pg_hba.conf (gathered
> it from the logs after I saw where they were).
> 
> The bootstrap program ran, but I noticed several PostgreSQL ERROR messages
> flying by, so I wanted to check them.
Most of them are warnings that PG reports as errors and result
from dropping non-existant DB objects (with halt-on-error
temporarily off). They *do* hide the real errors which is
unfortunate but to the best of my knowledge not avoidable.

> To do that I started redirecting
> stderr to a pg-out file like this:
> 
> $ ./bootstrap-gm_db_system.py --conf-file=bootstrap-monolithic_core.conf 
> --log-file=./foo 2> pg-out.txt
> 
> This tells me that the bootstrap script has a bug because an interactive
> question is going into stderr which is now being redirected:
Catch 22.

Try using <script> (man script) for that.

> Now the bootstrap doesn't work anymore. Understandable, I think to myself,
> since now things have been created, although it should check and ask me if
> I want to drop them or not.
I'd be delighted to learn how to do that in SQL.

> So I start trying to DROP the database
Yep, that's required.

> and users it created.
Never mind. It simply skips users/groups that are already
there. We can do that since we run those commands directly
from Python and not from an SQL script.

> 2003-10-31 11:55:53 [WARN]  (./bootstrap-gm_db_system.py::__create_db:651): 
> exception type : libpq.Warning
> 2003-10-31 11:55:53 [WARN]  (./bootstrap-gm_db_system.py::__create_db:651): 
> exception value: WARNING:  ROLLBACK: no transaction in progress
> 
> 2003-10-31 11:55:53 [DATA]  (./bootstrap-gm_db_system.py::__create_db:651): 
> Traceback (most recent call last):<#10-0x0A-lf>
> 2003-10-31 11:55:53 [DATA]  (./bootstrap-gm_db_system.py::__create_db:651):   
> File "./bootstrap-gm_db_system.py", line 649, in __create_db<#10-0x0A-lf>    
> cursor.execute(cmd)<#10-0x0A-lf>
> 2003-10-31 11:55:53 [DATA]  (./bootstrap-gm_db_system.py::__create_db:651):   
> File "/usr/lib/python2.3/site-packages/pyPgSQL/PgSQL.py", line 3069, in 
> execute<#10-0x0A-lf>    raise Warning, self.conn.notices.pop()<#10-0x0A-lf>
> 2003-10-31 11:55:53 [DATA]  (./bootstrap-gm_db_system.py::__create_db:651): 
> Warning: WARNING:  ROLLBACK: no transaction in 
> progress<#10-0x0A-lf><#10-0x0A-lf>
> 2003-10-31 11:55:53 [PANIC] (./bootstrap-gm_db_system.py::bootstrap:772): 
> Cannot bootstrap service [config].
> 2003-10-31 11:55:53 [PANIC] (./bootstrap-gm_db_system.py::bootstrap:772): 
> exception type : libpq.Warning
> 2003-10-31 11:55:53 [PANIC] (./bootstrap-gm_db_system.py::bootstrap:772): 
> exception value: WARNING:  COMMIT: no transaction in progress
Highly interesting. Can you post (or mail me) the full log ?
I know it's rather large.

> So the question is, what do I need to do in order to 
> "start from scratch" the bootstrap process? It looks like I need to drop
> some groups. 
Just dropping the DB is supposed to do.

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]