Your message dated Tue, 12 May 2015 22:37:00 +0200
with message-id <[email protected]>
and subject line Re: Bug#784956: postgresql can't start when fallback to C
locale
has caused the Debian Bug report #784956,
regarding postgresql can't start when fallback to C locale
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
784956: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784956
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
package: postgresql
version: 9.4+165
This happens when default locale is set to 'None' (en_IN without en_IN
locale in the system).
root@pod:~# dpkg-reconfigure locales
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_PAPER = "en_IN.utf8",
LC_MONETARY = "en_IN.utf8",
LC_NUMERIC = "en_IN.utf8",
LC_MEASUREMENT = "en_IN.utf8",
LC_TIME = "en_IN.utf8",
LANG = "en_IN"
# pg_createcluster 9.4 main --start succeeds after en_IN is generated.
root@pod:~# pg_createcluster 9.4 main --start
Creating new cluster 9.4/main ...
config /etc/postgresql/9.4/main
data /var/lib/postgresql/9.4/main
locale en_IN
Flags of /var/lib/postgresql/9.4/main set as -------------e-C
could not change directory to "/root": Permission denied
port 5432
original error:
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
Setting up postgresql-common (165) ...
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
Adding user postgres to group ssl-cert
Creating config file /etc/postgresql-common/createcluster.conf with new
version
Building PostgreSQL dictionaries from installed myspell/hunspell packages...
Removing obsolete dictionary files:
insserv: warning: script 'wide-dhcpv6-client' missing LSB tags and overrides
[warn] No PostgreSQL clusters exist; see "man pg_createcluster" ...
(warning).
Setting up postgresql-9.4 (9.4.1-1) ...
Error: The locale requested by the environment is invalid.
Error: could not create default cluster. Please create it manually with
pg_createcluster 9.4 main --start
or a similar command (see 'man pg_createcluster').
update-alternatives: using
/usr/share/postgresql/9.4/man/man1/postmaster.1.gz to provide
/usr/share/man/man1/postmaster.1.gz (postmaster.1.gz) in auto mode
[warn] No PostgreSQL clusters exist; see "man pg_createcluster" ...
(warning).
I think this is an issue with perl, but I think falling back to C locale
should work.
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Re: Pirate Praveen 2015-05-11 <[email protected]>
> This happens when default locale is set to 'None' (en_IN without en_IN
> locale in the system).
> Setting up postgresql-common (165) ...
> locale: Cannot set LC_CTYPE to default locale: No such file or directory
> locale: Cannot set LC_MESSAGES to default locale: No such file or directory
> locale: Cannot set LC_ALL to default locale: No such file or directory
[...]
> Setting up postgresql-9.4 (9.4.1-1) ...
> Error: The locale requested by the environment is invalid.
> Error: could not create default cluster. Please create it manually with
>
> pg_createcluster 9.4 main --start
>
> or a similar command (see 'man pg_createcluster').
Hi,
it's impossible to create a proper database cluster without the locale
you want it to use created first. If you want the cluster to use the
"C" locale, make that the system's default locale. As witnessed by the
perl and "locale" warnings, other programs have problems with
non-existing locales as well.
> I think this is an issue with perl, but I think falling back to C locale
> should work.
It's an issue with your system, you shouldn't try to use a locale that
hasn't been generated yet.
Christoph
--
[email protected] | http://www.df7cb.de/
signature.asc
Description: Digital signature
--- End Message ---
_______________________________________________
Pkg-postgresql-public mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
