[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] gnumed upgrade failure
From: |
Sebastian Hilbert |
Subject: |
Re: [Gnumed-devel] gnumed upgrade failure |
Date: |
Mon, 25 Nov 2013 09:07:08 +0100 |
User-agent: |
KMail/4.11.2 (Linux/3.11.0-14-generic; KDE/4.11.2; i686; ; ) |
Am Montag, 25. November 2013, 07:41:32 schrieb Karsten Hilbert:
> On Mon, Nov 25, 2013 at 08:43:35AM +0530, Vaibhav Banait wrote:
> > Log attached here. For your kind consideration
>
> you need to close all other sessions:
> > 2013-06-10 09:10:43 INFO gm.bootstrapper (<string>::__create_db()
> > #747): trying to drop target database 2013-06-10 09:10:48 ERROR
> > gm.bootstrapper
> > (d:\workplace\gnumed-server.18.0\build\pyi.win32\gnumed\outpyz1.pyz\loggi
> > ng::exception() #1088): >>>[drop database "gnumed_v18"]<<< failed>
> > Traceback (most recent call last):
> > File "<string>", line 752, in __create_db
> > File
> > "D:\workplace\gnumed-server.18.0\build\pyi.win32\gnumed\outPYZ1.pyz\psy
> > copg2.extras", line 121, in execute>
> > OperationalError: database "gnumed_v18" is being accessed by other users
> > DETAIL: There are 1 other session(s) using the database.
>
> Karsten
That includes PG admin being open. If you have PG admin open it will not work.
Have hit that problem many times myself.
Sebastian