Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows installer 16.3-2 fails at initdb if Turkish_Türkiye.1254 selected or is default locale of the OS #127

Open
ertankucukoglu opened this issue Jul 21, 2024 · 7 comments

Comments

@ertankucukoglu
Copy link

Hello,

I am using postgresql-16.3-2-windows-x64.exe as installer.

I get an error message Problem running post-install step. Installation may not complete correctly The database cluster initialization failed.

I tested the same installer on

  • Windows 10 x64 English - all settings US English
  • Windows 10 x64 Turkish - all settings US English
  • Windows 10 x64 Turkish - all settings TR Turkish
  • Windows Server 2022 x64 English - all settings US English

All above tests give same error message.

When you read installer log file using UTF8 encoding and cscript parameters are correct in Turkish letters. However, cluster initialization log entry has wrong Turkish letter in it.
The database cluster will be initialized with locale "Turkish_T rkiye.1254".
Above, word Türkiye has character ü (double dot at top) but that letter is not logged correctly in UTF8 encoding. I think that is the root cause for the installer error.

Below is compressed log file for your convenience.
installbuilder_installer.zip

Let me know if you need more information.

Thanks & Regards,
Ertan

@Hakkology
Copy link

Having the same problem.
Unable to install postgre using installer due to this error unless i change the locale.

Problem running post-install step. Installation may not complete correctly The database cluster initialization failed.

Kindly submitted for your information.
Regards,

@sandeep-edb
Copy link
Contributor

@ertankucukoglu and @Hakkology this is being discussed at https://www.postgresql.org/message-id/flat/[email protected]

apart from it, per https://www.postgresql.org/message-id/dd630b4a-e136-42d4-814e-954f9c03f90a%40dunslane.net Thomas feels installer is re-encoding and should be looked into as well. But, I couldn't reproduce this issue on <=15 so probably there is no bug in the installer and it only needs a source code change. It will be helpful if you could verify PostgreSQL version 15 installer and confirm if the fresh installation worked fine or returned the same locale issue? Thanks

@ertankucukoglu
Copy link
Author

@sandeep-edb
I tested 15.7 installer on both Windows English and Windows Turkish.
Installation complete without any problem on both systems.
Is this problem with 16 because of PostgreSQL source changes?

@sandeep-edb
Copy link
Contributor

@ertankucukoglu yes it seems like because the installer scripts around that part of functionality is same across all branches.

@dolunay
Copy link

dolunay commented Oct 2, 2024

We see the same problem in postgresql 17 installation. I was able to perform the installation by changing the regional settings of Windows to English. But this method invalidates some language-related features.

@1xFalcon
Copy link

  1. First, ensure all PostgreSQL files are completely removed from your system. This includes uninstalling any existing PostgreSQL instances and deleting leftover files.
  2. Run the installer as an administrator.
  3. During setup, instead of selecting your local default region, choose "English, United States" as the locale.

This error appears to be caused by localization settings, and changing the locale provides a simple solution for now.

@sandeep-edb
Copy link
Contributor

sandeep-edb commented Nov 29, 2024

I've generated a test installer that allows to provide a locale on the command line. I've uploaded it to EDB ShareFile. The installation was successful with this option:

postgresql-17.2-0.0snapshot12082629519.995.1.23fce2b.1-windows-x64.exe --locale "tr-TR"

I'll need the email address to grant download access to this file on ShareFile if anyone needs it to verify the fix before I generate the release installer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants