gnumed-devel
[Top][All Lists]
Advanced

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

Re: [Gnumed-devel] gnumed upgrade failure.


From: Sebastian Hilbert
Subject: Re: [Gnumed-devel] gnumed upgrade failure.
Date: Tue, 26 Nov 2013 10:46:12 +0100
User-agent: KMail/4.11.2 (Linux/3.11.0-14-generic; KDE/4.11.2; i686; ; )

Am Dienstag, 26. November 2013, 13:56:52 schrieb Vaibhav Banait:
> Most problems appeared to be sorted out with new server installation. But
> few problems still persists. Here is a log.
> 
This doesn't look too bad. A v19 database was created and most test succeed.

One test fails though

2013-11-26 12:16:21  ERROR     gm.bootstrapper 
(<string>::check_data_plausibility() #880): plausibility check [paperwork 
templates] failed, expected [79], found [80]

2013-11-26 12:16:21  ERROR     gm.bootstrapper (<string>::exit_with_msg() 
#1439): Bootstrapping failed: plausibility checks inconsistent


There seems to be one template that is not expected. I guess we can solve 
that.

Other then that it looks ok. 

PostgreSQL version (numeric): 9.3
2013-11-26 12:14:30  DEBUG     gm.cfg (d:\workplace\gnumed-
server.19.1\build\pyi.win32\gnumed\outpyz1.pyz\gnumed.pycommon.gmcfg2::get() 
#391): option [database gnumed_v19::template version] found in source [file]
2013-11-26 12:14:31  INFO      gm.db (d:\workplace\gnumed-
server.19.1\build\pyi.win32\gnumed\outpyz1.pyz\gnumed.pycommon.gmpg2::database_schema_compatible()
 
#512): detected schema version [18], hash [a0f9efcabdecfb4ddb6d8c0b69c02092]
2013-11-26 12:14:31  INFO      gm.bootstrapper (<string>::__db_exists() #738): 
Database [gnumed_v19] does not exist.

Ok. This looks like you restored your v18 database into PG 9.3 or did you 
bootstrap a fresh v18 ?

If you have successfully restored then you should already be able to use your 
existing client 1.3.8 against v18 in PG 9.3.

Sebastian



reply via email to

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