On 2015-01-14, at 2:57 AM, Karsten Hilbert <address@hidden> wrote:
On Tue, Jan 13, 2015 at 07:14:07PM +0000, Jim Busser wrote:
1) In order to try to minimize problems during the attempt at restore, I became root
sudo -i
I doubt this will *make* you root. It will _do_ something
_as_ root (specifically: "nothing") and - upon finishing - go
back to being what you were before. The -i mainly serves to
more fully simulate your being root *during execution of
"nothing"*.
"whoami" should be able to tell you who you are.
root
=====================================================
2) As root, I copied a 19.8 server tarball from my normal
user space to the root directory / and then decompressed it,
in order that this would be owned by root
OK
3) I also copied the hopefully-intact, 383 Mb backup into the root-owned server folder
cd /gnumed-server.19.8/server
cp /Users/djb/.gnumed/backup/backup-gnumed_v19-GNUmed_Team-dhcp-128-189-241-105.ubcsecure.wireless.ubc.ca-2015-01-12-09-59-25.tar .
OK. Can you double-check (and post) the permissions of that copy ?
=====================================================
-rw-r--r-- 1 djb staff 383343616 12 Jan 10:00
4) However when I try to restore from this backup which is sitting in the same level of .../server/ as follows:
sh gm-restore_database.sh backup-gnumed_v19-GNUmed_Team-dhcp-128-189-241-105.ubcsecure.wireless.ubc.ca-2015-01-12-09-59-25.tar
what results is
==> Trying to restore a GNUmed backup …
file: backup-gnumed_v19-GNUmed_Team-dhcp-128-189-241-105.ubcsecure.wireless.ubc.ca-2015-01-12-09-59-25.tar
==> Reading configuration …
Please post content of "/etc/gnumed/gnumed-restore.conf".
=====================================================
#------------------------------------------------------------
# $Source: /home/ncq/Projekte/cvs2git/vcs-mirror/gnumed/gnumed/client/etc/gnumed/gnumed-restore.conf.example,v $
# $Id: gnumed-restore.conf.example,v 1.2 2009-01-08 21:12:42 ncq Exp $
#------------------------------------------------------------
#
# this is a shell fragment used by gm-restore_from_backup.sh
#
# copy this file to /etc/gnumed/gnumed-restore.conf and
# configure appropriately
#
# if the PostgreSQL user $GM_DBO needs a password you will
# have to configure that using a .pgpass file (see the PG
# manual for how to do that)
#
# http://www.postgresql.org/docs/8.1/static/libpq-pgpass.html
#
#------------------------------------------------------------
# if your PostgreSQL server is running on another port
GM_PORT="5432"
# set this to a writable directory on a drive where
# there is plenty of disk space available
# WORK_DIR_BASE="${HOME}/gnumed"
WORK_DIR_BASE="Users/djb/gnumed"
# where to store log files,
# note that if you chose to write logs to the work
# directory they will get lost during cleanup if the
# restore process succeeds
LOG_BASE="."
#============================================================
# $Log: gnumed-restore.conf.example,v $
# Revision 1.2 2009-01-08 21:12:42 ncq
# - remove /bin/bash
#
# Revision 1.1 2008/08/28 15:11:48 ncq
# - moved here
#
# Revision 1.3 2008/08/01 10:08:49 ncq
# - /bin/sh -> /bin/bash
#
# Revision 1.2 2007/07/03 09:57:29 ncq
# - WORK_DIR_BASE, LOG_BASE
#
# Revision 1.1 2007/05/08 11:57:40 ncq
# - new
#
# $Source: /home/ncq/Projekte/cvs2git/vcs-mirror/gnumed/gnumed/client/etc/gnumed/gnumed-restore.conf.example,v $
# $Id: gnumed-restore.conf.example,v 1.2 2009-01-08 21:12:42 ncq Exp $
#------------------------------------------------------------
#
# this is a shell fragment used by gm-restore_from_backup.sh
#
# copy this file to /etc/gnumed/gnumed-restore.conf and
# configure appropriately
#
# if the PostgreSQL user $GM_DBO needs a password you will
# have to configure that using a .pgpass file (see the PG
# manual for how to do that)
#
# http://www.postgresql.org/docs/8.1/static/libpq-pgpass.html
#
#------------------------------------------------------------
# if your PostgreSQL server is running on another port
GM_PORT="5432"
# set this to a writable directory on a drive where
# there is plenty of disk space available
# WORK_DIR_BASE="${HOME}/gnumed"
WORK_DIR_BASE="Users/djb/gnumed"
# where to store log files,
# note that if you chose to write logs to the work
# directory they will get lost during cleanup if the
# restore process succeeds
LOG_BASE="."
#============================================================
# $Log: gnumed-restore.conf.example,v $
# Revision 1.2 2009-01-08 21:12:42 ncq
# - remove /bin/bash
#
# Revision 1.1 2008/08/28 15:11:48 ncq
# - moved here
#
# Revision 1.3 2008/08/01 10:08:49 ncq
# - /bin/sh -> /bin/bash
#
# Revision 1.2 2007/07/03 09:57:29 ncq
# - WORK_DIR_BASE, LOG_BASE
#
# Revision 1.1 2007/05/08 11:57:40 ncq
# - new
#
=====================================================
==> Setting up workspace ... Users/djb/gnumed/gm-restore-2015-01-13-10-27-04
Given that the workspace name does NOT start with a "/" I
would suspect the option WORK_DIR_BASE inside
/etc/gnumed/gnumed-restore.conf does not start with one
either ?
=====================================================
what you say above looks to be correct.
The folder
Users/djb/gnumed/gm-restore-2015-01-13-10-27-04
is shown in the context of others in the attached screen shot
=====================================================
… so what can I do to troubleshoot the error message
directory Users/... does not exist
Please post the above.
Karsten
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
