Обсуждение: Failed to run initdb: 128

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?

> MSI (c) (C4:64) [15:59:30:242]: Note: 1: 2769 2: GetAvailableLocales 3:
> 1
> MSI (c) (C4:64) [15:59:30:242]: Note: 1: 2205 2:  3: Error
> MSI (c) (C4:64) [15:59:30:242]: Note: 1: 2228 2:  3: Error 4: SELECT
> `Message` FROM `Error` WHERE `Error` = 2769
> DEBUG: Error 2769:  Custom Action GetAvailableLocales did not close 1
> MSIHANDLEs.
> The installer has encountered an unexpected error installing this
> package. This may indicate a problem with this package. The error code
> is 2769. The arguments are: GetAvailableLocales, 1,

 > {1F701DBD-1660-4108-B10A-FB435EA63BF0} Version: 8.2.0 Attributes: 0
 > PatchId: Native BaselineId: -

This isn't version 8.2.0 you're installing, is it? Because 8.2.15 is the
current release for that version.

--
   Richard Huxton
   Archonet Ltd

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/

Hi

Thanks for the reply. Yes, I saw that "2769" is related to locales. On
the machine, I saw a new locale called "C" is installed. I am not sure
how it got installed. By default, this locale was getting selected. I
did select "English - united states" and try to install. It also failed
with the same error.

We are using 8.2.4. There is a later version, but we tested our
applciation thoroughly with 8.2.4 and so we currently bundle our
applciation with this version only.

Do you think uninstalling this locale would fix this issue?

Niranjan



-----Original Message-----
From: Richard Huxton [mailto:dev@archonet.com]
Sent: Thursday, March 04, 2010 1:05 AM
To: Niranjan Maturi (nmaturi)
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Failed to run initdb: 128

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?

> MSI (c) (C4:64) [15:59:30:242]: Note: 1: 2769 2: GetAvailableLocales
3:
> 1
> MSI (c) (C4:64) [15:59:30:242]: Note: 1: 2205 2:  3: Error
> MSI (c) (C4:64) [15:59:30:242]: Note: 1: 2228 2:  3: Error 4: SELECT
> `Message` FROM `Error` WHERE `Error` = 2769
> DEBUG: Error 2769:  Custom Action GetAvailableLocales did not close 1
> MSIHANDLEs.
> The installer has encountered an unexpected error installing this
> package. This may indicate a problem with this package. The error code
> is 2769. The arguments are: GetAvailableLocales, 1,

 > {1F701DBD-1660-4108-B10A-FB435EA63BF0} Version: 8.2.0 Attributes: 0
 > PatchId: Native BaselineId: -

This isn't version 8.2.0 you're installing, is it? Because 8.2.15 is the

current release for that version.

--
   Richard Huxton
   Archonet Ltd

On 04/03/10 20:43, Niranjan Maturi (nmaturi) wrote:
> Hi
>
> Thanks for the reply. Yes, I saw that "2769" is related to locales. On
> the machine, I saw a new locale called "C" is installed. I am not sure
> how it got installed. By default, this locale was getting selected. I
> did select "English - united states" and try to install. It also failed
> with the same error.

The "C" locale is a built-in one that just orders by the numeric
binary-representation of the characters in a string. Standard "C" style
ordering.

> We are using 8.2.4. There is a later version, but we tested our
> applciation thoroughly with 8.2.4 and so we currently bundle our
> applciation with this version only.

Try a later version. New features are not introduced in minor updates,
but bug-fixes are. Check the release-notes for the latest version back
to 8.2.4 and unless you are relying on the incorrect behaviour of a bug,
it is worth keeping up-to-date.

http://www.postgresql.org/docs/8.2/static/release-8-2-15.html

> Do you think uninstalling this locale would fix this issue?

No. Can you post the end of the installer log-file you get? Or
preferably the whole file.

--
   Richard Huxton
   Archonet Ltd

On 05/03/10 20:05, Niranjan Maturi (nmaturi) wrote:
> Hi
>
> Thanks for the detailed explanation with the locales. I am trying to get
> approvals to use a later version in 8.2. A colleague also suggested that
> I install 8.3 version and uninstall it to clean up the machine. Then I
> can install 8.2. I will try this as well.
>
> I am attaching the zipped version of the whole log file.

OK - everything in there from [16:02:11:419] onwards (line 11630+) is
just uninstalling.

The last few actions appear to be:
Action 16:01:37: DoCreateUser. Creating user account...
Action 16:01:38: SetPermissions. Setting filesystem permissions...

This one appears to fail:
Action 16:01:39: RunInitdb. Initializing database cluster (this may take
a minute or two)...
MSI (s) (44:24) [16:01:39:449]: Executing op:

CustomActionSchedule(Action=RunInitdb,ActionType=3073,Source=BinaryData,Target=RunInitdb@4,CustomActionData=1033;e:\pgsql\;e:\pgsql\data\;e:\pgsql\share\;1502;;C;SQL_ASCII;postgres;postgres;GEAMTEST6V;cupmuser;V%JG:<DBA&mYeVqyXIBLbU:WfaqfY_L;)
MSI (s) (44:24) [16:01:39:465]: Creating MSIHANDLE (3) of type 790536
for thread 3620
MSI (s) (44:20) [16:01:39:465]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI21.tmp, Entrypoint: RunInitdb@4
MSI (s) (44!C0) [16:01:39:668]: Creating MSIHANDLE (4) of type 790531
for thread 448
MSI (c) (C4:08) [16:01:39:668]: Note: 1: 2205 2:  3: Error
MSI (c) (C4:08) [16:01:39:668]: Note: 1: 2228 2:  3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 2867
DEBUG: Error 2867:  The error dialog property is not set
The installer has encountered an unexpected error installing this
package. This may indicate a problem with this package. The error code
is 2867. The arguments are: , ,
MSI (c) (C4:08) [16:01:39:668]: Font created.  Charset: Req=0, Ret=0,
Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
...
DEBUG: Error 2888:  Executing the TextStyle view failed
The installer has encountered an unexpected error installing this
package. This may indicate a problem with this package. The error code
is 2888. The arguments are: TextStyle, ,
Failed to run initdb: 128!
Please see the logfile in 'e:\pgsql\tmp\initdb.log'.
...


It might be that the file permissions aren't actually working. If the
"postgres" user still exists, can you check it has permission to write
to "e:\pgsql\data" and also to acccess "e:\pgsql" and "e:\" too (doesn't
need write access).

--
   Richard Huxton
   Archonet Ltd

2010/3/8 Richard Huxton <dev@archonet.com>:
> On 05/03/10 20:05, Niranjan Maturi (nmaturi) wrote:
>>
>> Hi
>>
>> Thanks for the detailed explanation with the locales. I am trying to get
>> approvals to use a later version in 8.2. A colleague also suggested that
>> I install 8.3 version and uninstall it to clean up the machine. Then I
>> can install 8.2. I will try this as well.
>>
>> I am attaching the zipped version of the whole log file.
>
> OK - everything in there from [16:02:11:419] onwards (line 11630+) is just uninstalling.
>
> The last few actions appear to be:
> Action 16:01:37: DoCreateUser. Creating user account...
> Action 16:01:38: SetPermissions. Setting filesystem permissions...
>
> This one appears to fail:
> Action 16:01:39: RunInitdb. Initializing database cluster (this may take a minute or two)...
> MSI (s) (44:24) [16:01:39:449]: Executing op:
CustomActionSchedule(Action=RunInitdb,ActionType=3073,Source=BinaryData,Target=RunInitdb@4,CustomActionData=1033;e:\pgsql\;e:\pgsql\data\;e:\pgsql\share\;1502;;C;SQL_ASCII;postgres;postgres;GEAMTEST6V;cupmuser;V%JG:<DBA&mYeVqyXIBLbU:WfaqfY_L;)
> MSI (s) (44:24) [16:01:39:465]: Creating MSIHANDLE (3) of type 790536 for thread 3620
> MSI (s) (44:20) [16:01:39:465]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI21.tmp, Entrypoint:
RunInitdb@4
> MSI (s) (44!C0) [16:01:39:668]: Creating MSIHANDLE (4) of type 790531 for thread 448
> MSI (c) (C4:08) [16:01:39:668]: Note: 1: 2205 2:  3: Error
> MSI (c) (C4:08) [16:01:39:668]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 2867
> DEBUG: Error 2867:  The error dialog property is not set
> The installer has encountered an unexpected error installing this package. This may indicate a problem with this
package.The error code is 2867. The arguments are: , , 
> MSI (c) (C4:08) [16:01:39:668]: Font created.  Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
> ...
> DEBUG: Error 2888:  Executing the TextStyle view failed
> The installer has encountered an unexpected error installing this package. This may indicate a problem with this
package.The error code is 2888. The arguments are: TextStyle, , 
> Failed to run initdb: 128!
> Please see the logfile in 'e:\pgsql\tmp\initdb.log'.
> ...
>
>
> It might be that the file permissions aren't actually working. If the "postgres" user still exists, can you check it
haspermission to write to "e:\pgsql\data" and also to acccess "e:\pgsql" and "e:\" too (doesn't need write access). 

I wonder if it may have osmehting to do with a semicolon in the
password. IIRC we fixed that in the way that we reject semicolons, but
I don't recall which version we did that in.

So please give it a try without having a semicolon in the password.

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