Re: [Gnumed-devel] Release 0.4-rc4

[Rogerio Luz]

Ok here is the problem, my server v9 tarball makes a .bz2 file but gives the below error/exit 

***** consultorio:/home/rogerio/GNUmed/GNUmed-server.v9/GNUmed-v9/server# sh gm-zip+sign_backups.sh 
gm-zip+sign_backups.sh: line 107: -s: command not found
gm-zip+sign_backups.sh: line 107: -s: command not found
gm-zip+sign_backups.sh: line 107: -s: command not found
******consultorio:/home/rogerio/GNUmed/GNUmed-server.v9/GNUmed-v9/server# 

Please advise if this is ok, because I am weary to drop my current DB in order to restore a new v9 (the script does not let me restore a v9 if ther already exists a v9) 



I CAN make backups in .tar files, but I cannot make a restore with the script currently in my v9 tarball because it asks me to: 

**** consultorio:/home/rogerio/GNUmed/GNUmed-server.v9/GNUmed-v9/server# sh gm-restore_database.sh /root/.gnumed/backup/backup-gnumed_v9-GNUmed_Team-consultorio-2009-02-18-19-56-04.tar 

==> Trying to restore GNUmed backup ...
    file: /root/.gnumed/backup/backup-gnumed_v9-GNUmed_Team-consultorio-2009-02-18-19-56-04.tar

==> Reading configuration ...
    file: /etc/gnumed/gnumed-restore.conf

==> Testing backup file integrity ...
  /root/.gnumed/backup/backup-gnumed_v9-GNUmed_Team-consultorio-2009-02-18-19-56-04.tar: bad magic number (file not created by bzip2)

You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.

    ERROR: integrity check failed, aborting
***** consultorio:/home/rogerio/GNUmed/GNUmed-server.v9/GNUmed-v9/server# 

This was my problem a few months back and Karsten send me some scripts that fixed it, but I lost them ... the thing is it is shipped this way in the tarball and it should "just work", right??
--------------------------------------------------------------------------

Now I am having trouble testing the v10 server .... when I try to upgrade: 


****consultorio:/home/rogerio/GNUmed/GNUmed-server-v10# sh upgrade-db.sh 9 10

===========================================================
Upgrading GNUmed database.

This will *non-destructively* create a new GNUmed database
of version v10 from an existing v9 database.
Existing data is transferred and transformed as necessary.

The name of the new database will be "gnumed_v10".
===========================================================

1) creating backup of existing database ...
Note that this may take a substantial amount of time and disk space!
You may need to type in the password for gm-dbo.
Senha: 

2) upgrading to new database ...
Adjusting PYTHONPATH ...
Please make sure the GNUmed Python modules are in the Python path !
Traceback (most recent call last):
  File "./bootstrap_gm_db_system.py", line 65, in <module>
    from Gnumed.pycommon import gmLog2
ImportError: cannot import name gmLog2
Upgrading "gnumed_v9" to "gnumed_v10" did not finish successfully.
consultorio:/home/rogerio/GNUmed/GNUmed-server-v10# 

Seems an error on PYTHONPATH, never had this error before when upgrading (since v7 :) 


Rogerio 

PS sending the .po file 65% done

2009/2/18 Karsten Hilbert <address@hidden>

On Wed, Feb 18, 2009 at 09:18:12AM +0100, Hilbert, Sebastian wrote:

> > By the way, having trouble again to backup and auto bzip and to restore
> > backups form the 0.3.9 - 0.3.10 packages. The gm-backupdatabase.sh works
> > fine.
> >
> Do you mean you are trying to restore a backup from version 0.3.9/10 which is
> server version 9 into a server version 10 which is needed for 0.4 client
> series ?

That's what I thought, too. For that no backup/restore is
needed. Just run the upgrade-db.sh script as root
appropriately:

       upgrade-db.sh 9 10

That's it !

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


_______________________________________________

Gnumed-devel mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/gnumed-devel

pt_BR.po
Description: Text Data