unable to run command gm-bootstrap_server
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNUmed |
Invalid
|
Low
|
ncq |
Bug Description
I have an UBUNTU 9.10. I tried installing GNUMED and facing lot of problems.
I first installed postgresql-8.4, then installed gnumed-server, then run the command gnumed-server. I get the response cannot bootstrap bundles I am unable to proceed with the installation.
This is the response I get
=======
Bootstrapping latest GNUmed database.
This will set up a GNUmed database of version v11
with the name "gnumed_v11".
Adjusting PYTHONPATH ...
/var/lib/
import urllib2 as wget, decimal, StringIO, MimeWriter, mimetypes, mimetools
Traceback (most recent call last):
File "/usr/lib/
msg = self.format(record)
File "/usr/lib/
return fmt.format(record)
File "/usr/lib/
record.message = record.getMessage()
File "/usr/lib/
msg = msg % self.args
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 0: ordinal not in range(128)
Traceback (most recent call last):
File "/usr/lib/
msg = self.format(record)
File "/usr/lib/
return fmt.format(record)
File "/usr/lib/
s = self._fmt % record.__dict__
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 31: ordinal not in range(128)
=======
Bootstrapping GNUmed database system...
=======
You are about to install the following parts of GNUmed:
-------
bundle "config" in <gnumed_v2> (or overridden) on <>
bundle "reference" in <gnumed_v2> (or overridden) on <>
bundle "demographics" in <gnumed_v2> (or overridden) on <>
bundle "clinical" in <gnumed_v2> (or overridden) on <>
bundle "documents" in <gnumed_v2> (or overridden) on <>
bundle "office" in <gnumed_v2> (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.
==> bootstrapping "config" ...
==> creating target database [gnumed_v2] from [template1] (5280 kB) ...
Cannot bootstrap bundles.
Please check the log file for details.
Bootstrapping "gnumed_v11" did not finish successfully. Aborting.
Please help me how to continue
# PostgreSQL Client Authentication Configuration File ======= ======= ======= ======= ======= ======= ==
# =======
#
# Refer to the "Client Authentication" section in the
# PostgreSQL documentation for a complete description
# of this file. A short synopsis follows.
#
# This file controls: which hosts are allowed to connect, how clients
# are authenticated, which PostgreSQL user names they can use, which
# databases they can access. Records take one of these forms:
#
# local DATABASE USER METHOD [OPTIONS]
# host DATABASE USER CIDR-ADDRESS METHOD [OPTIONS]
# hostssl DATABASE USER CIDR-ADDRESS METHOD [OPTIONS]
# hostnossl DATABASE USER CIDR-ADDRESS METHOD [OPTIONS]
#
# (The uppercase items must be replaced by actual values.)
#
# The first field is the connection type: "local" is a Unix-domain socket,
# "host" is either a plain or SSL-encrypted TCP/IP socket, "hostssl" is an
# SSL-encrypted TCP/IP socket, and "hostnossl" is a plain TCP/IP socket.
#
# DATABASE can be "all", "sameuser", "samerole", a database name, or
# a comma-separated list thereof.
#
# USER can be "all", a user name, a group name prefixed with "+", or
# a comma-separated list thereof. In both the DATABASE and USER fields
# you can also write a file name prefixed with "@" to include names from
# a separate file.
#
# CIDR-ADDRESS specifies the set of hosts the record matches.
# It is made up of an IP address and a CIDR mask that is an integer
# (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that specifies
# the number of significant bits in the mask. Alternatively, you can write
# an IP address and netmask in separate columns to specify the set of hosts.
#
# METHOD can be "trust", "reject", "md5", "password", "gss", "sspi", "krb5",
# "ident", "pam", "ldap" or "cert". Note that "password" sends passwords
# in clear text; "md5" is preferred since it sends encrypted passwords.
#
# OPTIONS are a set of options for the authentication in the format
# NAME=VALUE. The available options depend on the different authentication
# methods - refer to the "Client Authentication" section in the documentation
# for a list of which options are available for which authentication methods.
#
# Database and user names containing spaces, commas, quotes and other special
# characters must be quoted. Quoting one of the keywords "all", "sameuser" or
# "samerole" makes the name lose its special character, and just match a
# database or username with that name.
#
# This file is read on server startup and when the postmaster receives
# a SIGHUP signal. If you edit the file on a running system, you have
# to SIGHUP the postmaster for the changes to take effect. You can use
# "pg_ctl reload" to do that.
# Put your actual configuration here ------- ------- ------- ------
# -------
#
# If you want to allow non-local connections, you need to add more
# "host" records. In that case you will also need to make PostgreSQL listen
# on a non-local interface via the listen_addresses configuration parameter,
# or via the -i or -h command line switches.
#
# DO NOT DISABLE!
# If you change this first entry you will need to make sure that the
# database
# super user can access the database ...