Last login: Wed Jan 2 23:26:32 on ttyp1
Welcome to Darwin!
MacBook:~ djb$ cd /Volumes/MacBookHD_1/GNUmed-v8/server/bootstrap/bootstrap-latest.sh
-bash: cd: /Volumes/MacBookHD_1/GNUmed-v8/server/bootstrap/bootstrap-latest.sh: Not a directory
MacBook:~ djb$ cd /Volumes/MacBookHD_1/GNUmed-v8/server/bootstrap/ MacBook:/Volumes/MacBookHD_1/GNUmed-v8/server/bootstrap djb$ ./bootstrap-latest.sh
ln: Gnumed: File exists
===========================================================
Bootstrapping latest GNUmed database.
This will set up a GNUmed database of version v8
with the name "gnumed_v8".
It contains all the currently working parts including
localizations for countries you don't live in. This does
not disturb the operation of the GNUmed client in your
country in any way.
===========================================================
1) Dropping old baseline gnumed_v2 database if there is any.
WARNING: Improper use of the sudo command could lead to data loss
or the deletion of important system files. Please double-check your
typing when using sudo. Type "man sudo" for more information.
To proceed, enter your password, or type Ctrl-C to abort.
Password:
Sorry, try again.
Password:
sudo: dropdb: command not found
==========================
2) bootstrapping databases
#################################################################################
#
# log file is [/Volumes/MacBookHD_1/GNUmed-v8/server/bootstrap/bootstrap-latest-v2.log]
#
# Please email this file to
if you encounter problems.
#
#################################################################################
=======================================
Bootstrapping GNUmed database system...
=======================================
Using config file [/Volumes/MacBookHD_1/GNUmed-v8/server/bootstrap/bootstrap-local_first.conf].
You are about to install the following parts of GNUmed:
-------------------------------------------------------
-------------------------------------------------------
This script can be used to run SQL files local to a site
*before* bootstrapping the rest of the database.
Thereby things that are only needed locally can be
integrated with the bootstrapping process and need not
be run manually after re-bootstrapping.
It is "guaranteed" that this file will never be changed
by the GNUmed team, hence keeping local modifications
in a safe place.
Do you really want to install this database setup ?
Type yes or no: yes
Using config file [/Volumes/MacBookHD_1/GNUmed-v8/server/bootstrap/bootstrap-monolithic_core.conf].
WARNING: This script may not work if not running as the system administrator.
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "config" in (or overridden) on <>
bundle "reference" in (or overridden) on <>
bundle "demographics" in (or overridden) on <>
bundle "clinical" in (or overridden) on <>
bundle "documents" in (or overridden) on <>
bundle "office" in (or overridden) on <>
-------------------------------------------------------
This will set up a monolithic GNUmed backend with all bundles
in one database named [gnumed]. It will contain the core schema
without country or language-specific components. Those will
have to be added by using one of the bootstrap-XX.conf file
where XX represents the ISO country code.
Currently this file will also import the test accounts which
MUST be removed prior to real use.
Do you really want to install this database setup ?
Type yes or no: yes
==> bootstrapping "config" ...
We are about to check whether we need to create the
database user who owns all GNUmed database objects.
The database owner will be created.
You will have to provide a new password for it
unless it is pre-defined in the configuration file.
Make sure to remember the password.
I need the password for the GNUmed database user [gm-dbo].
Please type password:
==> creating new target database [gnumed_v2] ...
(this can take a while if [template1] is large)
==> transferring users ...
... skipped (unconfigured)
==> bootstrapping "reference" ...
==> bootstrapping "demographics" ...
==> bootstrapping "clinical" ...
==> bootstrapping "documents" ...
==> bootstrapping "office" ...
==> setting up auditing ...
==> setting up notifications ...
... skipped (disabled)
Using config file [/Volumes/MacBookHD_1/GNUmed-v8/server/bootstrap/bootstrap-de.conf].
WARNING: This script may not work if not running as the system administrator.
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "demographics-de" in (or overridden) on <>
bundle "clinical-de" in (or overridden) on <>
bundle "reference-de" in (or overridden) on <>
bundle "?bersetzung" in (or overridden) on <>
-------------------------------------------------------
Dieses Skript installiert Daten in ein GNUmed-Datenbanksystem,
mit denen GNUmed f?r Deutschland angepa?t wird.
Die Datenbankstruktur mu? bereits in einer GNUmed-Datenbank
installiert sein, ebenso mu? mindestens der Nutzer gm-dbo
bereits existieren.
==> bootstrapping "demographics-de" ...
==> bootstrapping "clinical-de" ...
==> bootstrapping "reference-de" ...
==> bootstrapping "?bersetzung" ...
==> setting up auditing ...
... skipped (disabled)
==> setting up notifications ...
... skipped (disabled)
Using config file [/Volumes/MacBookHD_1/GNUmed-v8/server/bootstrap/bootstrap-es.conf].
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "demographics-es" in (or overridden) on <>
-------------------------------------------------------
Este script instala en la base de datos de GNUmed las informaciones
espec?ficas para su uso en Espa?a (provincias).
Como requisitos, el esquema debe haber sido previamente instalado
en la base de datos "gnumed" y, al menos, el usuario "gm-dbo" debe
haber sido creado.
==> bootstrapping "demographics-es" ...
==> setting up auditing ...
... skipped (disabled)
==> setting up notifications ...
... skipped (disabled)
Using config file [/Volumes/MacBookHD_1/GNUmed-v8/server/bootstrap/bootstrap-ca.conf].
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "demographics-ca" in (or overridden) on <>
-------------------------------------------------------
This script installs data into a GNUmed database system in
order to localise GNUmed for Canada.
The core database schema must have been imported into a database
"gnumed" already. Also, the user gm-dbo must exist.
==> bootstrapping "demographics-ca" ...
==> setting up auditing ...
... skipped (disabled)
==> setting up notifications ...
... skipped (disabled)
Using config file [/Volumes/MacBookHD_1/GNUmed-v8/server/bootstrap/bootstrap-au.conf].
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "au-locale" in (or overridden) on <>
-------------------------------------------------------
This script installs data into a GNUmed database system in
order to localise GNUmed for Australia.
The core database schema must have been imported into a database
"gnumed" already. Also, the user gm-dbo must exist.
==> bootstrapping "au-locale" ...
==> setting up auditing ...
... skipped (disabled)
==> setting up notifications ...
... skipped (disabled)
Using config file [/Volumes/MacBookHD_1/GNUmed-v8/server/bootstrap/bootstrap-test_data.conf].
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "test data" in (or overridden) on <>
-------------------------------------------------------
This script installs test data into an existing GNUmed database
named "gnumed". Also, the database owner "gm-dbo" must exist
already.
==> bootstrapping "test data" ...
==> setting up auditing ...
... skipped (disabled)
==> setting up notifications ...
... skipped (disabled)
Using config file [/Volumes/MacBookHD_1/GNUmed-v8/server/bootstrap/bootstrap-local_last.conf].
You are about to install the following parts of GNUmed:
-------------------------------------------------------
-------------------------------------------------------
This script can be used to run SQL files local to a site
*after* bootstrapping the rest of the database.
Thereby things that are only needed locally can be
integrated with the bootstrapping process and need not
be run manually after re-bootstrapping.
It is "guaranteed" that this file will never be changed
by the GNUmed team, hence keeping local modifications
in a safe place.
Do you really want to install this database setup ?
Type yes or no: yes
==> setting up auditing ...
... skipped (disabled)
==> setting up notifications ...
... skipped (disabled)
==> verifying target database schema ...
identity hash of "gnumed_v2": b09d50d7ed3f91ddf4c4ddb8ea507720
==> checking migrated data for plausibility ...
... skipped (no checks defined)
==> upgrading reference data sets ...
... skipped (no scripts to run)
Done bootstrapping: We very likely succeeded.
#################################################################################
#
# log file is [/Volumes/MacBookHD_1/GNUmed-v8/server/bootstrap/bootstrap-latest-v3.log]
#
# Please email this file to if you encounter problems.
#
#################################################################################
=======================================
Bootstrapping GNUmed database system...
=======================================
Using config file [update_db-v2_v3.conf].
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v2-v3-static" in (or overridden) on <>
bundle "v2-v3-dynamic" in (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 2
database to the version 3 schema. It does not do
any harm to the data contained within.
The existing database is cloned first. The copy is
then modified. The original database remains unchanged.
Do you really want to install this database setup ?
Type yes or no: yes
==> bootstrapping "v2-v3-static" ...
We are about to check whether we need to create the
database user who owns all GNUmed database objects.
The database owner already exists.
Please provide the password previously used for it.
I need the password for the GNUmed database user [gm-dbo].
Please type password:
==> creating new target database [gnumed_v3] ...
(this can take a while if [gnumed_v2] is large)
==> transferring users ...
... skipped (unconfigured)
==> bootstrapping "v2-v3-dynamic" ...
==> setting up auditing ...
... skipped (disabled)
==> setting up notifications ...
... skipped (disabled)
==> verifying target database schema ...
identity hash of "gnumed_v3": e73718eaf230d8f1d2d01afa8462e176
==> checking migrated data for plausibility ...
... skipped (no checks defined)
==> upgrading reference data sets ...
... skipped (no scripts to run)
Done bootstrapping: We very likely succeeded.
Dropping obsoleted staging database gnumed_v2 ...
sudo: dropdb: command not found
#################################################################################
#
# log file is [/Volumes/MacBookHD_1/GNUmed-v8/server/bootstrap/bootstrap-latest-v4.log]
#
# Please email this file to if you encounter problems.
#
#################################################################################
=======================================
Bootstrapping GNUmed database system...
=======================================
Using config file [update_db-v3_v4.conf].
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v3-v4-static" in (or overridden) on <>
bundle "v3-v4-dynamic" in (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 3
database to the version 4 schema. It does not do
any harm to the data contained within.
The existing database is cloned first. The copy is
then modified. The original database remains unchanged.
Do you really want to install this database setup ?
Type yes or no: yes
==> bootstrapping "v3-v4-static" ...
We are about to check whether we need to create the
database user who owns all GNUmed database objects.
The database owner already exists.
Please provide the password previously used for it.
I need the password for the GNUmed database user [gm-dbo].
Please type password:
==> creating new target database [gnumed_v4] ...
(this can take a while if [gnumed_v3] is large)
==> transferring users ...
... skipped (unconfigured)
==> bootstrapping "v3-v4-dynamic" ...
==> setting up auditing ...
... skipped (disabled)
==> setting up notifications ...
... skipped (disabled)
==> verifying target database schema ...
identity hash of "gnumed_v4": 4428ccf2e54c289136819e701bb095ea
==> checking migrated data for plausibility ...
... skipped (no checks defined)
==> upgrading reference data sets ...
... skipped (no scripts to run)
Done bootstrapping: We very likely succeeded.
Dropping obsoleted staging database gnumed_v3 ...
Password:
Sorry, try again.
Password:
Sorry, try again.
Password:
sudo: 2 incorrect password attempts
#################################################################################
#
# log file is [/Volumes/MacBookHD_1/GNUmed-v8/server/bootstrap/bootstrap-latest-v5.log]
#
# Please email this file to if you encounter problems.
#
#################################################################################
=======================================
Bootstrapping GNUmed database system...
=======================================
Using config file [update_db-v4_v5.conf].
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v4-v5-static" in (or overridden) on <>
bundle "v4-v5-dynamic" in (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 4
database to the version 5 schema. It does not do
any harm to the data contained within.
The existing database is cloned first. The copy is
then modified. The original database remains unchanged.
Do you really want to install this database setup ?
Type yes or no: yes
==> bootstrapping "v4-v5-static" ...
We are about to check whether we need to create the
database user who owns all GNUmed database objects.
The database owner already exists.
Please provide the password previously used for it.
I need the password for the GNUmed database user [gm-dbo].
Please type password:
==> creating new target database [gnumed_v5] ...
(this can take a while if [gnumed_v4] is large)
==> transferring users ...
... skipped (unconfigured)
==> bootstrapping "v4-v5-dynamic" ...
==> setting up auditing ...
... skipped (disabled)
==> setting up notifications ...
... skipped (disabled)
==> verifying target database schema ...
identity hash of "gnumed_v5": 7e7b093af57aea48c288e76632a382e5
==> checking migrated data for plausibility ...
... skipped (no checks defined)
==> upgrading reference data sets ...
... skipped (no scripts to run)
Done bootstrapping: We very likely succeeded.
Dropping obsoleted staging database gnumed_v4 ...
Password:
Sorry, try again.
Password:
sudo: dropdb: command not found
#################################################################################
#
# log file is [/Volumes/MacBookHD_1/GNUmed-v8/server/bootstrap/bootstrap-latest-v6.log]
#
# Please email this file to if you encounter problems.
#
#################################################################################
=======================================
Bootstrapping GNUmed database system...
=======================================
Using config file [update_db-v5_v6.conf].
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v5-v6-static" in (or overridden) on <>
bundle "v5-v6-dynamic" in (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 5
database to the version 6 schema. It does not do
any harm to the data contained within.
The existing database is cloned first. The copy is
then modified. The original database remains unchanged.
Do you really want to install this database setup ?
Type yes or no: yes
==> bootstrapping "v5-v6-static" ...
We are about to check whether we need to create the
database user who owns all GNUmed database objects.
The database owner already exists.
Please provide the password previously used for it.
I need the password for the GNUmed database user [gm-dbo].
Please type password:
==> creating new target database [gnumed_v6] ...
(this can take a while if [gnumed_v5] is large)
==> transferring users ...
==> bootstrapping "v5-v6-dynamic" ...
==> setting up auditing ...
... skipped (disabled)
==> setting up notifications ...
... skipped (disabled)
==> verifying target database schema ...
identity hash of "gnumed_v6": 90e2026ac2efd236da9c8608b8685b2d
==> checking migrated data for plausibility ...
==> upgrading reference data sets ...
... skipped (no scripts to run)
Done bootstrapping: We very likely succeeded.
Dropping obsoleted staging database gnumed_v5 ...
sudo: dropdb: command not found
#################################################################################
#
# log file is [/Volumes/MacBookHD_1/GNUmed-v8/server/bootstrap/bootstrap-latest-v7.log]
#
# Please email this file to if you encounter problems.
#
#################################################################################
=======================================
Bootstrapping GNUmed database system...
=======================================
Using config file [update_db-v6_v7.conf].
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v6-v7-static" in (or overridden) on <>
bundle "v6-v7-dynamic" in (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 6
database to the version 7 schema. It does not do
any harm to the data contained within.
The existing database is cloned first. The copy is
then modified. The original database remains unchanged.
Do you really want to install this database setup ?
Type yes or no: yes
==> bootstrapping "v6-v7-static" ...
We are about to check whether we need to create the
database user who owns all GNUmed database objects.
The database owner already exists.
Please provide the password previously used for it.
I need the password for the GNUmed database user [gm-dbo].
Please type password:
==> creating new target database [gnumed_v7] ...
(this can take a while if [gnumed_v6] is large)
==> transferring users ...
==> bootstrapping "v6-v7-dynamic" ...
==> setting up auditing ...
... skipped (disabled)
==> setting up notifications ...
... skipped (disabled)
==> verifying target database schema ...
identity hash of "gnumed_v7": 6c9f6d3981483f8e9433df99d1947b27
==> checking migrated data for plausibility ...
==> upgrading reference data sets ...
Done bootstrapping: We very likely succeeded.
Dropping obsoleted staging database gnumed_v6 ...
sudo: dropdb: command not found
#################################################################################
#
# log file is [/Volumes/MacBookHD_1/GNUmed-v8/server/bootstrap/bootstrap-latest-v8.log]
#
# Please email this file to if you encounter problems.
#
#################################################################################
=======================================
Bootstrapping GNUmed database system...
=======================================
Using config file [update_db-v7_v8.conf].
You are about to install the following parts of GNUmed:
-------------------------------------------------------
bundle "v7-v8-static" in (or overridden) on <>
bundle "v7-v8-dynamic" in (or overridden) on <>
-------------------------------------------------------
This will update an existing GNUmed version 7
database to the version 8 schema. It does not do
any harm to the data contained within.
The existing database is cloned first. The copy is
then modified. The original database remains unchanged.
Do you really want to install this database setup ?
Type yes or no: yes
==> bootstrapping "v7-v8-static" ...
We are about to check whether we need to create the
database user who owns all GNUmed database objects.
The database owner already exists.
Please provide the password previously used for it.
I need the password for the GNUmed database user [gm-dbo].
Please type password:
==> creating new target database [gnumed_v8] ...
(this can take a while if [gnumed_v7] is large)
==> transferring users ...
==> bootstrapping "v7-v8-dynamic" ...
==> setting up auditing ...
==> setting up notifications ...
==> verifying target database schema ...
identity hash of "gnumed_v8": 89b13a7af83337c3aad153b717e52360
==> checking migrated data for plausibility ...
==> upgrading reference data sets ...
... skipped (no scripts to run)
Done bootstrapping: We very likely succeeded.
MacBook:/Volumes/MacBookHD_1/GNUmed-v8/server/bootstrap djb$