On 2015-01-12, at 3:47 PM, "Busser, Jim" <address@hidden> wrote:
> I have run into problems trying to upgrade to server 20.0 and am not sure how much was a result of my own mistakes or if there may be a problem in the server files.
>
> My first problem was my losing track (in my notes) of the appropriate syntax because, from inside
>
> /Users/djb/Downloads/gnumed-server.20.0/server/bootstrap/
>
> I issued the command
>
> sh ./fixup-db.sh 20
>
> which gave me
>
> Traceback (most recent call last):
> File "./bootstrap_gm_db_system.py", line 74, in <module>
> from Gnumed.pycommon import gmCfg2, gmPsql, gmPG2, gmTools, gmI18N
> File "/Users/djb/Downloads/gnumed-server.20.0/Gnumed/pycommon/gmPG2.py", line 2057, in <module>
> psycopg2.extensions.register_adapter(dict, psycopg2.extras.Json)
> AttributeError: 'module' object has no attribute 'Json'
> Fixing "gnumed_v20" did not finish successfully.
> ^Z
> [2]+ Stopped(SIGTSTP)
>
> and so thinking I had the wrong syntax I next issued
>
> sh ./fixup-db.sh 19
>
> which gave me the same thing.
Further to the above, by way of an experiment to see if I could get *any* fixups to work,
I went back to the fixups which I had last run successfully, which came from server 19.8 which I had run back around May or June of 2014.
But when I tried to re-run them as follows,
dhcp-128-189-241-105:bootstrap root# cd /Users/djb/Downloads/gnumed-server.19.8/server/bootstrap/
dhcp-128-189-241-105:bootstrap root# sh ./fixup-db.sh 19
in the hope of achieving simple confirmation that these particular ones had already been run, the session appeared to "hang" …
===========================================================
Fixing GNUmed database.
This will apply fixups to an existing GNUmed database of
version 19 named "gnumed_v19".
===========================================================
1) applying fixes to database ...
Adjusting PYTHONPATH ...
=======================================
Bootstrapping GNUmed database system...
=======================================
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v19-fixups" in <gnumed_v19> (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed database.
It does so by applying all fixup SQL scripts
appropriate to the version of the database.
Do you really want to install this database setup ?
Type yes or no: yes
==> bootstrapping "v19-fixups" ...
I need the password for the database user [postgres].
Please type the password:
==> using pre-existing *target* database [gnumed_v19] ...
==> transferring users ...
... skipped (disabled)
(waited 20 minutes before aborting)
Is there a problem in what I was trying to do? Log attached.
-- Jim
fixup_db-v19.log