Re: [Gnumed-devel] gnumed upgrade failure.

[Vaibhav Banait]

I had actually did it before clicking upgrade. Now I am 100% sure nothing is 
connected . Vaibhav Banait

-original message-
Subject: Re: gnumed upgrade failure.
From: "Busser, Jim" <address@hidden>
Date: 25/11/2013 11:54 pm

On 2013-11-25, at 10:02 AM, Vaibhav Banait 
<address@hidden<mailto:address@hidden>> wrote:

So far , no success. Here are few errors I could trace back. I can only hope I 
am not annoying you.<332.gif>

: update_db-v18_v19.conf
2013-11-25 22:41:36  INFO      gm.cfg 
(d:\workplace\gnumed-server.19.0\build\pyi.win32\gnumed\outpyz1.pyz\gnumed.pycommon.gmcfg2::add_file_source()
 #445): file source "file": update_db-v18_v19.conf (utf8)
2013-11-25 22:41:36  DEBUG     gm.cfg 
(d:\workplace\gnumed-server.19.0\build\pyi.win32\gnumed\outpyz1.pyz\gnumed.pycommon.gmcfg2::parse_INI_stream()
 #274): parsing INI-style data stream [<open file 'update_db-v18_v19.conf', 
mode 'rb' at 0x01E192E0>]
2013-11-25 22:41:36  DEBUG     gm.cfg 
(d:\workplace\gnumed-server.19.0\build\pyi.win32\gnumed\outpyz1.pyz\gnumed.pycommon.gmcfg2::get()
 #389): option [config files] not in group [installation] in source [file]
2013-11-25 22:41:36  INFO      gm.bootstrapper (<string>::main() #1573): 
single-shot config file
2013-11-25 22:41:36  INFO      gm.bootstrapper (<string>::handle_cfg() #1508): 
config file: update_db-v18_v19.conf
2013-11-25 22:41:36  WARNING   gm.bootstrapper 
(<string>::become_pg_demon_user() #1463): running on broken OS -- can't import 
pwd module

ERROR     gm.bootstrapper 
(d:\workplace\gnumed-server.19.0\build\pyi.win32\gnumed\outpyz1.pyz\logging::exception()
 #1088): cannot run import script [v19-import-form-templates.py]
Traceback (most recent call last):
  File "<string>", line 992, in import_data
  File "..\sql\v18-v19\python\v19-import-form-templates.py", line 38, in run
    conn = conn
  File 
"D:\workplace\gnumed-server.19.0\build\pyi.win32\gnumed\outPYZ1.pyz\Gnumed.pycommon.gmPG2",
 line 1091, in file2bytea
IOError: [Errno 2] No such file or directory: 
'..\\sql\\v18-v19\\data\\v19-GNUmed-Gr\xc3\xbcnes_Rezept_template.tex'
2013-11-25 22:43:44  ERROR     gm.bootstrapper (<string>::exit_with_msg() 
#1439): Bootstrapping failed: unable to import data
2013-11-25 22:43:44  INFO      gm.bootstrapper (<string>::exit_with_msg() 
#1440): shutdown

[Error 32] The process cannot access the file because it is being used by 
another process: 
'c:\\users\\dell\\appdata\\local\\temp\\audit-trail-schema.sql'<smb://users//dell//appdata//local//temp//audit-trail-schema.sql'>
2013-11-25 22:43:43  INFO      gm.boo

ERROR     gm.bootstrapper (<string>::__connect_superuser_to_srv_template() 
#388): LC_CTYPE does not end in .UTF-8 or .UTF8
2013-11-25 22:41:43  INFO      gm.bootstrapper 
(<string>::__connect_superuser_to_srv_template() #392): server_encoding is 
[UTF8]
2013-11-25 22:41:43  INFO      gm.bootstrapper 
(<string>::__connect_superuser_to_srv_template() #399): server encoding seems 
compatible despite not being reported in LC_CTYPE
2013-11-25 22:41:43  INFO      gm.bootstrapper 
(<string>::__connect_superuser_to_srv_template() #405): successfully connected 
to template database [template1]
2013-11-25 22:41:43

Vaibhav S Banait

Vaibhav, if you did not in the meantime receive other suggestions, you could 
try rebooting your machine before the next time you attempt to bootstrap. That 
should close the persisting connections that you were unaware or unable to 
close and which gave rise to [Error 32].

-- Jim