Re: [Gnumed-devel] Strange

[Sebastian Hilbert]

Be very careful here. 

Go to c:\program files\PosgresPlus\8.4SS\data\postgresql.conf

what does it say for port ? initially was 5432 and should be 5433

Go to c:\program files\Posgresql\9.3\data\postgresql.conf

what does it say for port ? initially was 5433 and should be 5432

Be aware that all postgresql instances need to be restarted to accept the 
changes.

do this by typing

net stop postgresql-8.4
net start postgresql-8.4

net stop postgresql-9.3
net start postgresql-9.3

Pgadmin can fool you ! When you connect make sure you don't rely on the names 
in the left pane, make sure it tells you the correct port and PG version on 
the right !

Look at the image ! There is only two databases in what seems to be PG 8.4 on 
port 5432 and 18+ databases in the supposedly PG 9.3 on port 5433.

I think PGadmin is not telling the truth. In reality PG 9.3 is on 5432 and PG 
8.4 is on 5433 despite what Pgadmin tells you. How would you have managed to 
have only two databases in PG 8.4 and 18+ in PG 9.3 ?

pgadmin will tell you the truth in the right pane. Check that.

As an intermediate test you would want to check if GNUmed 1.3.8 connects to 
the v18 database in PG 9.3.

You can even check that without swapping ports. What I mean to say is :

If you edit the port in gnumed.conf from 5432 to 5433 you can connect to the 
other PG (e.g. if PG 8.4 is on 5432 and PG 9.3 is on 5433).

Or you can add another profile in gnumed.conf. One for port 5433 and one for 
port 5432.

In any case do not just delete databases. You could be doing it in the wrong 
PG !!!

Make sure you know which PG is on which port and go from there.

Sebastian

Am Mittwoch, 20. November 2013, 18:54:12 schrieb Busser, Jim:
> On 2013-11-20, at 10:16 AM, Vaibhav Banait
> <address@hidden<mailto:address@hidden>> wrote:
> 
> Something strange has happened. I copied and pasted all the commands as
> suggested by Sebastian. And then upgraded the database. When trying to
> connect with client 1.4, I am getting error shown in PNG file. Moreover
> when I looked at the database through pgadmin 1. Ports have not reversed
> 2. The database which were previously there in 8.4 are seen in 9.3 ,and 8.4
> shows only two databases 18 and 19, I expected in 9.3.
> 
> Attached is an update log file.
> 
> I am not sure why your ports have not reversed ... I believe you should have
> needed to stop both your servers (postgres-8.4 on port 5432 and
> postgres-9.3 on 5433) before suitably altering *both* of your postgres.conf
> files, and *then* restarting both of your servers, and *then* making sure
> you quit pgadmin (and all your GNUmed clients and any open psql
> connections, if any are open) before you try again to bootstrap v19 because
> your log shows that your attempt failed.
> 
> For a long time, I did not bother to actually examine my own log files,
> because I had assumed I lacked the knowledge to understand them. Over time
> though,
> 
> - the contents became more familiar and
> - more importantly, I discovered that I could commonly identify, all by
> myself, the nature of the problem, and sometimes even the solution.
> 
> The answer is easiest to locate near the bottom of the log, typically 10-20
> lines from the bottom and above the exit logging, in those cases where
> logging ceased. This is in contrast to, say, the case where the user choose
> and succeeded to keep the client and therefore the logging running.
> 
> In this case, your log ends as below, suggesting that you had pgadmin open
> and/or a GNUmed client (whether 1.3.x v18 would account for it) or else a
> psql shell / session.
> 
> You will have to quit all of those before retrying to re-run the bootstrap.
> 
> =========================
> 
> 2013-11-20 23:10:11  INFO      gm.bootstrapper (<string>::__create_db()
> #761): trying to drop target database 2013-11-20 23:10:16  ERROR    
> gm.bootstrapper
> (d:\workplace\gnumed-server.19.0\build\pyi.win32\gnumed\outpyz1.pyz\logging
> ::exception() #1088): >>>[drop database "gnumed_v19"]<<< failed Traceback
> (most recent call last):
>   File "<string>", line 766, in __create_db
>   File
> "D:\workplace\gnumed-server.19.0\build\pyi.win32\gnumed\outPYZ1.pyz\psycopg
> 2.extras", line 120, in execute OperationalError: database "gnumed_v19" is
> being accessed by other users DETAIL:  There is 1 other session using the
> database.
> 
> 2013-11-20 23:10:16  ERROR     gm.bootstrapper (<string>::__bootstrap()
> #594): Cannot create database. 2013-11-20 23:10:16  ERROR    
> gm.bootstrapper
> (d:\workplace\gnumed-server.19.0\build\pyi.win32\gnumed\outpyz1.pyz\logging
> ::exception() #1088): Cannot bootstrap bundle [v18_fixups-pre_v19].
> Traceback (most recent call last):
>   File "<string>", line 1259, in bootstrap
>   File "<string>", line 567, in __init__
> ConstructorError: database.__init__(): Cannot bootstrap database.
> 2013-11-20 23:10:16  ERROR     gm.bootstrapper (<string>::exit_with_msg()
> #1439): Cannot bootstrap bundles. 2013-11-20 23:10:16  INFO     
> gm.bootstrapper (<string>::exit_with_msg() #1440): shutdown
> =========================
> 
> -- Jim