gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] gnumed.conf - still can't createdb


From: richard terry
Subject: Re: [Gnumed-devel] gnumed.conf - still can't createdb
Date: Tue, 23 Sep 2003 08:36:20 +1000
User-agent: KMail/1.5

Still not working. Nothing of infrastructure has changed on my machine and 
gnumed was perfectly functional last time I ran it - until I physically 
deleted the database recently wanting a 'fresh copy'.

No cancel was pressed at any stage in the script previously supplied

Starting point
---------------------------------------
gnumed.doesnt exist eg:
----------------------------------------
address@hidden bootstrap]$ dropdb gnumed
ERROR:  DROP DATABASE: database "gnumed" does not exist
dropdb: database removal failed

--------------------------------------------------------------------------------------
listing of /home/richard/.gnumed/ shows nothing exists
--------------------------------------------------------------------------------------
:address@hidden .gnumed]$ ls
address@hidden .gnumed]$
------------------------------------------
Now try and run the script:
------------------------------------------
address@hidden bootstrap]$ python bootstrap-gm_db_system.py 
--conf-file=bootstrap-monolithic_core.conf
log file is [/home/richard/.bootstrap-gm_db_system/bootstrap-gm_db_system.log]
Bootstrapping GnuMed database system...
You are about to install the following GnuMed services:
-------------------------------------------------------
service [default] => database [gnumed] => server [127.0.0.1]
service [personalia] => database [gnumed] => server [127.0.0.1]
service [historica] => database [gnumed] => server [127.0.0.1]
service [blobs] => database [gnumed] => server [127.0.0.1]
service [reference] => database [gnumed] => server [127.0.0.1]
-------------------------------------------------------
This will set up a monolithic GnuMed backend with all services
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
I need the password for the GnuMed database user [postgres].
Please type password:
We are about to check whether we need to create the
database user who owns all GnuMed database objects.

Unless the password for this user is given in the
config file you will be asked to provide it.
If you already ran the bootstrapping script previously
please provide the same password again. Otherwise you
you may get connection errors if this database user had
been created previously with a different password.

I need the password for the GnuMed database user [gm-dbowner].
Please type password:
Cannot bootstrap services.
Please check the log file for details.


Any suggestions

Thanks

richard

On Mon, 22 Sep 2003 09:23 pm, Karsten Hilbert wrote:
> > 2003-09-18 14:44:06
> > ------------------------------------------------------------ 2003-09-18
> > 14:44:06 [INFO] 
> > (/home/richard/gnumed/gnumed/client/python-common/gmLog.py::__init__:400)
> >: SECURITY: initial log level is [INFO] 2003-09-18 14:44:06 [INFO] 
> > (/home/richard/gnumed/gnumed/client/python-common/gmLog.py::SetAllLogLeve
> >ls:284): SECURITY: log level change from [INFO]   to [INFO] 2003-09-18
> > 14:44:06 [INFO] 
> > (/home/richard/gnumed/gnumed/client/python-common/gmLog.py::AddTarget:159
> >): SECURITY: adding log target "stdout/stderr" 2003-09-18 14:44:06 [INFO] 
> > (gnumed.py::Main:183): Starting up as main module ($Revision: 1.55 $).
> > 2003-09-18 14:44:06 [INFO] 
> > (/home/richard/gnumed/gnumed/client/python-common/gmPG.py::Main:60): DBMS
> > "Postgres" via DB-API module "<module 'pyPgSQL.PgSQL' from
> > '/usr/lib/python2.2/site-packages/pyPgSQL/PgSQL.pyc'>": API level 2.0,
> > thread safety 1, parameter style "pyformat" 2003-09-18 14:44:06 [WARN] 
> > (/home/richard/gnumed/gnumed/client/python-common/gmCfg.py::__get_conf_na
> >me:694): config file [/home/richard/gnumed/gnumed/client/etc/gnumed.conf]
> > not found 2003-09-18 14:44:06 [WARN] 
> > (/home/richard/gnumed/gnumed/client/python-common/gmCfg.py::__get_conf_na
> >me:694): config file [/home/richard/.gnumed.conf] not found 2003-09-18
> > 14:44:06 [INFO] 
> > (/home/richard/gnumed/gnumed/client/python-common/gmI18N.py::__install_do
> >main:124): text domain is "gnumed" 2003-09-18 14:44:07 [WARN] 
> > (/home/richard/gnumed/gnumed/client/python-common/gmCfg.py::get:438):
> > option <client encoding> not found in group [backend] 2003-09-18 14:44:07
> > [WARN]  (gmGuiMain.py::Main:50): you need to set the parameter <client
> > encoding> in the config file 2003-09-18 14:44:07 [WARN] 
> > (gmGuiMain.py::Main:51): on Linux you can determine a likely candidate
> > for the encoding by running "locale charmap" 2003-09-18 14:44:29 [INFO] 
> > (/home/richard/gnumed/gnumed/client/wxpython/gmLogin.py::Login:45): user
> > cancelled login dialog
>
> This seems to indicate the you pressed CANCEL before logging
> in ?!? If not, a code path is hosed.
>
> Karsten





reply via email to

[Prev in Thread] Current Thread [Next in Thread]