Обсуждение: 8.2beta1 installation fails
I ran msi installation package downloaded from postgresql.org from remote desktop. I selected Estonian locale, UTF-8 database encoding. After that I got error Failed to run initdb: !128 Please see the logfile in 'C:\program Files\PostgreSQL\8.2beta1\tmp\initdb.log'. Note! You must read/copy this logfile before yuo click OK, or it will be automatically removed. (This message is handwritten and may contains some typos since Ctrl+C does not work in error message box). I leaved the message box in screen and looked into C:\Program Files\PostgreSQL\8.2beta1\tmp directory. This directory was empty. How to install 8.2 from msi file with cluster initialization ? Andrus. Environment: Windows 2003 Enterprise server build 3790 (service pack 1)
> I ran msi installation package downloaded from postgresql.org > from remote desktop. > I selected Estonian locale, UTF-8 database encoding. > > After that I got error > > Failed to run initdb: !128 > Please see the logfile in 'C:\program > Files\PostgreSQL\8.2beta1\tmp\initdb.log'. > Note! You must read/copy this logfile before yuo click OK, or > it will be automatically removed. > > (This message is handwritten and may contains some typos > since Ctrl+C does not work in error message box). > > I leaved the message box in screen and looked into > C:\Program Files\PostgreSQL\8.2beta1\tmp directory. > This directory was empty. > > How to install 8.2 from msi file with cluster initialization ? When this happens, can you run initdb manually? I mean while the error message is up there? Just to show where the problem is. Also, does it work if you pick a different locale/encoding? (it really shouldn't make this kind of error, but worth checking) //Magnus
Andrus,
did you make sure you used the /console mode of remote desktop?
it is a known limitation that installtion via remote desktop without /console does not work.
Easiest solution: use VNC :)
Harald
--
GHUM Harald Massa
persuadere et programmare
Harald Armin Massa
Reinsburgstraße 202b
70197 Stuttgart
0173/9409607
-
Python: the only language with more web frameworks than keywords.
did you make sure you used the /console mode of remote desktop?
On 10/24/06, Andrus <eetasoft@online.ee > wrote:
I ran msi installation package downloaded from postgresql.org from remote
desktop.
I selected Estonian locale, UTF-8 database encoding.
it is a known limitation that installtion via remote desktop without /console does not work.
Easiest solution: use VNC :)
Harald
--
GHUM Harald Massa
persuadere et programmare
Harald Armin Massa
Reinsburgstraße 202b
70197 Stuttgart
0173/9409607
-
Python: the only language with more web frameworks than keywords.
> Andrus, > > did you make sure you used the /console mode of remote desktop? > > > On 10/24/06, Andrus <eetasoft@online.ee > wrote: > > I ran msi installation package downloaded from > postgresql.org <http://postgresql.org> from remote > desktop. > I selected Estonian locale, UTF-8 database encoding. > > > it is a known limitation that installtion via remote desktop > without /console does not work. > > Easiest solution: use VNC :) Actually, that's not entirely so. I've seen it work just fine many times on Windows 2003 with 8.2, so the check has been removed in 8.2. And this is not the same problem - because with that problem it would run initdb and give a log with an error on it. It would still be interesting to know if made a difference if you were on the console, though //Magnus
> It would still be interesting to know if made a difference if you were > on the console, though Installation from console session is OK. > When this happens, can you run initdb manually? I mean while the error > message is up there? Just to show where the problem is. I'm unable to run initdb manually: C:\Program Files\PostgreSQL\8.2beta1\bin>initdb -D test The program "postgres" is needed by initdb but was not found in the same directory as "C:\Program Files\PostgreSQL\8.2beta1\bin/initdb". Check your installation. > Also, does it work if you pick a different locale/encoding? (it really > shouldn't make this kind of error, but worth checking) Please re-confirm if you want that I try this. I think it may be the same shared memory allocation issue which I descibed in message from April 5, 2006. Computer has 8 GB RAM. If you tell me how to run initdb manually I can try it. Previous report from 05.04.2006 was: creating directory data ... ok creating directory data/global ... ok creating directory data/pg_xlog ... ok creating directory data/pg_xlog/archive_status ... ok creating directory data/pg_clog ... ok creating directory data/pg_subtrans ... ok creating directory data/pg_twophase ... ok creating directory data/pg_multixact/members ... ok creating directory data/pg_multixact/offsets ... ok creating directory data/base ... ok creating directory data/base/1 ... ok creating directory data/pg_tblspc ... ok selecting default max_connections ... 10 selecting default shared_buffers ... 50 creating configuration files ... ok creating template1 database in data/base/1 ... DEBUG: TZ "Europe/Helsinki" matc hes Windows timezone "FLE Daylight Time" DEBUG: invoking IpcMemoryCreate(size=1327104) DEBUG: mapped win32 error code 161 to 2 FATAL: could not create shared memory segment: No such file or directory DETAIL: Failed system call was shmget(key=1, size=1327104, 03600). DEBUG: proc_exit(1) DEBUG: shmem_exit(1) DEBUG: exit(1) child process was terminated by signal 1 initdb: removing data directory "data" Andrus.