gnumed-devel
[Top][All Lists]
Advanced

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

Re: [Gnumed-devel] install gnumed server


From: Karsten Hilbert
Subject: Re: [Gnumed-devel] install gnumed server
Date: Thu, 14 Jun 2007 12:23:43 +0200
User-agent: Mutt/1.5.13 (2006-08-11)

Hello Laurent,

glad to see you back.

> I tried to install the server side of gnumed.
> 
> Here comes the redo-v2.log:

I assume you are doing this indirectly via
bootstrap-latest.sh, right ? You should be getting a
bootstrap-latest-v2.log. It shouldn't really make a
difference as far as I can tell but it is recommended to use
bootstrap-latest.sh (well, *now* it is explicitely
recommended in the README ;-)

Anyways, please retry and send the log.

So, off to analyzing your progress:

> (/home/lof/gnumed-server/GNUmed-v6/Gnumed/pycommon/gmPG2.py:address@hidden): 
> assuming default client time zone of [00:00:00.00]
Are you indeed on UTC, locally ?

> (./bootstrap_gm_db_system.py:address@hidden):  running as  user [postgres]
That should work, I suppose.

> (/home/lof/gnumed-server/GNUmed-v6/Gnumed/pycommon/gmPG2.py:address@hidden): 
>  PostgreSQL version (numeric): 8.1
...
> (/home/lof/gnumed-server/GNUmed-v6/Gnumed/pycommon/gmPG2.py:address@hidden): 
>  PostgreSQL version (string): "PostgreSQL 8.1.8 on i486-pc-linux-gnu, 
> compiled by GCC cc (GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)"
That should work.

> (/home/lof/gnumed-server/GNUmed-v6/Gnumed/pycommon/gmPsql.py:address@hidden): 
> ../sql/gmPublicAccounts.sql:27:  la relation ?gm_schema_revision? 
> n'existe pas
Aha, your PG server speaks French. Which is good to know
because some translated error/notice messages will overflow
the error message buffer (happens with German, too) and
cause ...

> 2007-06-13 07:30:42  [ERROR] 
> (/home/lof/gnumed-server/GNUmed-v6/Gnumed/pycommon/gmPsql.py:address@hidden): 
> ../sql/gmClin-EMR-Structure-static.sql:23: ERRORDATA_STACK_SIZE exceeded

... this secondary error to occur.

A fix is to set lc_messages to 'C' in postgresql.conf and
restart PostgreSQL. That will make it return messages in
English :-( which, however, doesn't overflow the buffer.

Now, this may fix the problem entirely or it may unmask
another error hiding behind that. We'll have to see and will
debug it if there is a real bug somewhere.

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




reply via email to

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