Re: Failed to run initdb: 128 - Mailing list pgsql-general

From Magnus Hagander
Subject Re: Failed to run initdb: 128
Date
Msg-id 9837222c1003040353j4cc75584tbc4e2ae1dab6e634@mail.gmail.com
Whole thread Raw
In response to Re: Failed to run initdb: 128  (Richard Huxton <dev@archonet.com>)
List pgsql-general
2010/3/4 Richard Huxton <dev@archonet.com>:
> On 04/03/10 00:12, Niranjan Maturi (nmaturi) wrote:
>>
>> Hi
>>
>> I am trying to install Postgres 8.2 on a virtual machine that has
>> Windown 2003 SP2. The installation fails with the error "Failed to run
>> initdb: 128". I searched the archives and looks like it is a catch-all
>> error. But is there anything specific that we can do to resolve this
>> issue?
>>
>> I am logged in as an administrator, so no problem with permissions.
>> Postgres was able to create the windows user account properly and after
>> that it fails with the above error. It tells us to copy a log file
>> initdb.log, but that file does not exist.
>
> It clearly didn't get that far in the process.
>
>> There is another log file pginstall.log, where I do see some error
>> messages, I printed them below. Any help is appreciated.
>
> Well, searching on error "2769" just seems to say a custom installer step failed. In this case clearly
"GetAvailableLocales"- nothing unusual with your locale setup, is there? 

No, that's not the probem. GetAvailableLocales() is the last step that
runs pre-installation. It has clearly moved past it.

If you get the initdb execution error, there should (hopefully) be a
separate log called (IIRC) initdb.log.


--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

pgsql-general by date:

Previous
From: Craig Ringer
Date:
Subject: Re: The REAL cost of joins
Next
From: Asher Hoskins
Date:
Subject: Re: to_timestamp() and quarters