[Top][All Lists]

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

Re: [Gnumed-devel] Connection to local server

From: Karsten Hilbert
Subject: Re: [Gnumed-devel] Connection to local server
Date: Tue, 19 Jun 2007 20:34:41 +0200
User-agent: Mutt/1.5.13 (2006-08-11)

On Wed, Jun 20, 2007 at 05:01:02AM +1100, Laurent FRANCOIS wrote:

> I backport from unstable to etch: gnumed-client_0.2.6.3-1

You need to backport gnumed-common, too, but I suppose you
knew that.

So, on to your log file (thanks $DEITY it tells us
everything we need to know):

> (/var/lib/python-support/python2.4/Gnumed/pycommon/ 
>  found config file [--conf-file=/home/lof/.gnumed/gnumed.conf]

This file tells GNUmed to ...

> 2007-06-19 17:30:23  [INFO] 
> (/var/lib/python-support/python2.4/Gnumed/pycommon/ 
>  setting default DSN from [dbname=gnumed_v5 host=localhost port=5432 
> user=gm-dbo password=gm-dbo sslmode=prefer] to [dbname=gnumed_v5 
> host=localhost port=5432 user=gm-dbo password=gm-dbo sslmode=prefer]

... connect to the gnumed_v5 database. It then ...

> 2007-06-19 17:30:33  [ERROR] 
> (/var/lib/python-support/python2.4/Gnumed/pycommon/ 
>  database schema version mismatch

... complains about that here because ...

> 2007-06-19 17:30:33  [ERROR] 
> (/var/lib/python-support/python2.4/Gnumed/pycommon/ 
>  expected: v6 (90e2026ac2efd236da9c8608b8685b2d)

... it needs a v6 database but ...

> 2007-06-19 17:30:35  [ERROR] 
> (/var/lib/python-support/python2.4/Gnumed/pycommon/ 
>  detected: v5 (7e7b093af57aea48c288e76632a382e5)

... it found a v5 one.

> So it seems to be a problem with gnumed_v5

No, you need to tell GNUmed to connect to the proper
database, namely gnumed_v6. To do so you need to edit the
config file.

> Do you think I can just drop it?

You can, but there is no need to (this is actually one of
our features for safekeeping medical data across database
upgrades). I customarily do NOT drop the old database after
an upgrade but disable access to them so I don't accidentally
connect and have to dig around for errors like the above.

GPG key ID E4071346 @
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

reply via email to

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