|| at Sep 27, 2012 at 7:49 pm
CM installer runs initdb w/o specifying the locale but specifies
encoding as UTF8. So the postgresql picks up default locale from the
OS. The error you see is generated by Postgresql when it checks the
default locale and finds that it doesn't support UTF-8 format.
Can you try running "initdb" on your setup w/o specifying locale, but
providing --encoding=UTF8? You should hit same error.
Also, what do you get when you run "locale" command? What do you get
when you run "locale -a"?
On Thu, Sep 27, 2012 at 11:55 AM, Mohit Chawla
Its Ubuntu 12.04 (precise).
On Fri, Sep 28, 2012 at 12:19 AM, Vikas Singh wrote:
What's the distro you are using?
On Thu, Sep 27, 2012 at 11:47 AM, Mohit Chawla
The locale of the OS which I have already mentioned is set to UTF-8.
On Thu, Sep 27, 2012 at 9:38 PM, Vikas Singh wrote:
Please set default Locale of the OS to be one which supports UTF-8.
Please look at documentation of the distro you are using to see how
you can change default Locale.
On Thu, Sep 27, 2012 at 3:31 AM, alcy wrote:
When running the installer for the free edition, this error is recorded in
the log file init-embedded-b.log:
"initdb: encoding mismatch
The encoding you selected (UTF8) and the encoding that the
selected locale uses (LATIN1) do not match. This would lead to
misbehavior in various character string processing functions.
Rerun initdb and either do not specify an encoding explicitly,
or choose a matching combination."
Is there a manual way to ensure this doesn't occur ? I have already tried to
execute initdb (successfully) with utf8 encoding and locale as the
cloudera-scm user and after that if I run the installer, the installer still
fails, but the log file it points to is empty.