Обсуждение: Failed to initialize lc_messages to ''

Hi,

when I try to execute initdb I get the following errors:

---<<< cut >>>---

The files belonging to this database system will be owned by user
"postgres".
This user must also own the server process.

The database cluster will be initialized with locales:
    COLLATE:  POSIX     CTYPE:   en_US  MESSAGES: en_US
    MONETARY: en_US     NUMERIC: en_US  TIME:     en_US

Fixing permissions on existing directory /opt/pgsql/data... ok
creating directory /opt/pgsql/data/base... ok
creating directory /opt/pgsql/data/global... ok
creating directory /opt/pgsql/data/pg_xlog... ok
creating directory /opt/pgsql/data/pg_clog... ok
creating template1 database in /opt/pgsql/data/base/1... Failed to
initialize lc_messages to ''
ok
creating configuration files... ok
initializing pg_shadow... Failed to initialize lc_messages to ''
ok
enabling unlimited row size for system tables... Failed to initialize
lc_messages to ''
ok
initializing pg_depend... Failed to initialize lc_messages to ''
ok
creating system views... Failed to initialize lc_messages to ''
ok
loading pg_description... Failed to initialize lc_messages to ''
ok
creating conversions... Failed to initialize lc_messages to ''
ok
setting privileges on built-in objects... Failed to initialize
lc_messages to ''
ok
vacuuming database template1... Failed to initialize lc_messages to ''
ok
copying template1 to template0... Failed to initialize lc_messages to
''
ok

Success. You can now start the database server using:

    ./bin/postmaster -D /opt/pgsql/data
or
    ./bin/pg_ctl -D /opt/pgsql/data -l logfile start

---<<< cut >>>---

Can someone help ?

Thanx


Jan

jan.berka@dreger.de (Jan B.) writes:
> when I try to execute initdb I get the following errors:

> The database cluster will be initialized with locales:
>     COLLATE:  POSIX     CTYPE:   en_US  MESSAGES: en_US
>     MONETARY: en_US     NUMERIC: en_US  TIME:     en_US

> creating template1 database in /opt/pgsql/data/base/1... Failed to
> initialize lc_messages to ''

What platform is this?  You should complain to the relevant people about
their broken locale definitions.  If they're going to set en_US as the
default locale then it darn well ought to work in all locale categories.

In the meantime, try
    export LC_ALL=C
(or equivalent syntax if you use a C shell) before you run initdb.
You'll be better off running Postgres in C locale anyway.

            regards, tom lane

On Monday, March 17, 2003, at 11:36 AM, Tom Lane wrote:

> jan.berka@dreger.de (Jan B.) writes:
>> when I try to execute initdb I get the following errors:
>
>> The database cluster will be initialized with locales:
>>     COLLATE:  POSIX     CTYPE:   en_US  MESSAGES: en_US
>>     MONETARY: en_US     NUMERIC: en_US  TIME:     en_US
>
>> creating template1 database in /opt/pgsql/data/base/1... Failed to
>> initialize lc_messages to ''
>
> What platform is this?  You should complain to the relevant people
> about
> their broken locale definitions.  If they're going to set en_US as the
> default locale then it darn well ought to work in all locale
> categories.
>

Mac OS X does this.  See my recent post on the subject here:

http://fts.postgresql.org/db/mw/msg.html?mid=1064449

--Jeremy

>> I just tried a fresh install of pg 7.3.1 on a SuSE
8.1 box. I keep getting
>> messages like
>> Failed to initialize lc_messages to ''
>> during initdb. I already tried --locale=C but no
help. Anyone any
>> ideas?

>Try initdb with -d option and show us the (last few
lines of) output.
>Also, what is your LANG/LC_ALL setting?  Does the -d
output change
>when you use --locale=C?
>
>            regards, tom lane

Hi,

I've had this same problem trying to install 7.3.3 on
Suse 8.0.  Here is the abridged logfile, as requested.
 THe -d output does not change when using --locale=C.
LANG is set to en_US and LC_ALL is set to C.

[Begin logfile]

initdb variables:
  PGDATA=/usr/local/pgsql/data
  datadir=/usr/local/pgsql/share
  PGPATH=/usr/local/pgsql/bin
  ENCODING=
  ENCODINGID=0
  POSTGRES_SUPERUSERNAME=postgres
  POSTGRES_BKI=/usr/local/pgsql/share/postgres.bki

POSTGRES_DESCR=/usr/local/pgsql/share/postgres.description

POSTGRESQL_CONF_SAMPLE=/usr/local/pgsql/share/postgresql.conf.sample

PG_HBA_SAMPLE=/usr/local/pgsql/share/pg_hba.conf.sample

PG_IDENT_SAMPLE=/usr/local/pgsql/share/pg_ident.conf.sample
Failed to initialize lc_messages to ''
DEBUG:  invoking IpcMemoryCreate(size=983040)
LOG:  database system was shut down at 2003-06-27
19:38:13 EDT
LOG:  checkpoint record is at 0/10
LOG:  redo record is at 0/10; undo record is at 0/10;
shutdown TRUE
LOG:  next transaction id: 3; next oid: 16384
LOG:  database system is ready
DEBUG:  start transaction
DEBUG:  creating bootstrap relation pg_proc...

...
[168000+ lines of insertions, etc]
...
DEBUG:  start transaction
DEBUG:  commit transaction
DEBUG:  proc_exit(0)
DEBUG:  shmem_exit(0)
DEBUG:  exit(0)
Failed to initialize lc_messages to ''
LOG:  database system was shut down at 2003-06-27
19:38:17 EDT
LOG:  checkpoint record is at 0/74
LOG:  redo record is at 0/74; undo record is at 0/0;
shutdown TRUE
LOG:  next transaction id: 3; next oid: 16652
LOG:  database system is ready
LOG:  shutting down
LOG:  database system is shut down
Failed to initialize lc_messages to ''
LOG:  database system was shut down at 2003-06-27
19:38:17 EDT
LOG:  checkpoint record is at 0/8F24
LOG:  redo record is at 0/8F24; undo record is at 0/0;
shutdown TRUE
LOG:  next transaction id: 11; next oid: 16654
LOG:  database system is ready
LOG:  shutting down
LOG:  database system is shut down
Failed to initialize lc_messages to ''
LOG:  database system was shut down at 2003-06-27
19:38:17 EDT
LOG:  checkpoint record is at 0/44800
LOG:  redo record is at 0/44800; undo record is at
0/0; shutdown TRUE
LOG:  next transaction id: 21; next oid: 16681
LOG:  database system is ready
LOG:  shutting down
LOG:  database system is shut down
Failed to initialize lc_messages to ''
LOG:  database system was shut down at 2003-06-27
19:38:17 EDT
LOG:  checkpoint record is at 0/F671C
LOG:  redo record is at 0/F671C; undo record is at
0/0; shutdown TRUE
LOG:  next transaction id: 43; next oid: 16681
LOG:  database system is ready
LOG:  shutting down
LOG:  database system is shut down
Failed to initialize lc_messages to ''
LOG:  database system was shut down at 2003-06-27
19:38:18 EDT
LOG:  checkpoint record is at 0/1515D4
LOG:  redo record is at 0/1515D4; undo record is at
0/0; shutdown TRUE
LOG:  next transaction id: 72; next oid: 16765
LOG:  database system is ready
LOG:  shutting down
LOG:  database system is shut down
Failed to initialize lc_messages to ''
LOG:  database system was shut down at 2003-06-27
19:38:18 EDT
LOG:  checkpoint record is at 0/1BA9D8
LOG:  redo record is at 0/1BA9D8; undo record is at
0/0; shutdown TRUE
LOG:  next transaction id: 77; next oid: 16771
LOG:  database system is ready
LOG:  shutting down
LOG:  database system is shut down
Failed to initialize lc_messages to ''
LOG:  database system was shut down at 2003-06-27
19:38:18 EDT
LOG:  checkpoint record is at 0/213008
LOG:  redo record is at 0/213008; undo record is at
0/0; shutdown TRUE
LOG:  next transaction id: 420; next oid: 16975
LOG:  database system is ready
LOG:  shutting down
LOG:  database system is shut down
Failed to initialize lc_messages to ''
LOG:  database system was shut down at 2003-06-27
19:38:18 EDT
LOG:  checkpoint record is at 0/490120
LOG:  redo record is at 0/490120; undo record is at
0/0; shutdown TRUE
LOG:  next transaction id: 425; next oid: 16975
LOG:  database system is ready
LOG:  shutting down
LOG:  database system is shut down
Failed to initialize lc_messages to ''
LOG:  database system was shut down at 2003-06-27
19:38:19 EDT
LOG:  checkpoint record is at 0/7FAD6C
LOG:  redo record is at 0/7FAD6C; undo record is at
0/0; shutdown TRUE
LOG:  next transaction id: 466; next oid: 16975
LOG:  database system is ready
LOG:  shutting down
LOG:  database system is shut down

[End logfile]

Thanks for any assistance.

Shawn

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com