Your message dated Tue, 19 Sep 2006 21:56:56 +0200
with message-id <[EMAIL PROTECTED]>
and subject line postgresql: don't run with libc version 2.3.6.ds1-4
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: postgresql
Version: 7.4.7-6sarge3
Severity: normal

aftre update to libc version 2.3.6.ds1-4, the following error rises:

ERROR: ERROR: PostgreSQL postmaster did not start because of an unknown reason.
PostgreSQL's init script (/etc/init.d/postgresql) attempted
to start the postmaster, however, this failed because of an unknown
reason.

This should not happen and is a serious problem. Please examine the
situation (please take a look at the log files). If you know the
reason why it failed and, then please file a bug report to Debian
(unless the reason is something obvious like a full disk).

Debian PostgreSQL


in the log:

FATAL:  XX000: failed to initialize lc_messages to ""
LOCATION:  InitializeGUCOptions, guc.c:1880


the dependency on libc should be restricted.

Regards
Robert


-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (101, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8.1
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages postgresql depends on:
ii  adduser          3.63                    Add and remove users and groups
ii  debconf [debconf 1.4.30.13               Debian configuration management sy
ii  debianutils      2.8.4                   Miscellaneous utilities specific t
ii  dpkg             1.10.28                 Package maintenance system for Deb
ii  libc6            2.3.2.ds1-22sarge4      GNU C Library: Shared libraries an
ii  libcomerr2       1.37-2sarge1            common error description library
ii  libkrb53         1.3.6-2sarge3           MIT Kerberos runtime libraries
ii  libpam0g         0.76-22                 Pluggable Authentication Modules l
ii  libperl5.8       5.8.4-8sarge5           Shared Perl library
ii  libpq3           7.4.7-6sarge3           PostgreSQL C client library
ii  libreadline4     4.3-11                  GNU readline and history libraries
ii  libssl0.9.7      0.9.7e-3sarge1          SSL shared libraries
ii  mailx            1:8.1.2-0.20040524cvs-4 A simple mail user agent
ii  postgresql-clien 7.4.7-6sarge3           front-end programs for PostgreSQL
ii  procps           1:3.2.1-2               The /proc file system utilities
ii  python2.3        2.3.5-3sarge1           An interactive high-level object-o
ii  ucf              1.17                    Update Configuration File: preserv
ii  zlib1g           1:1.2.2-4.sarge.2       compression library - runtime

-- debconf information:
* postgresql/initdb/location: /var/lib/postgres/data
  postgresql/upgrade/preserve_location: $PGDATA/..
* postgresql/settings/day_month_order: European
  postgresql/upgrade/policy: true
* postgresql/settings/locale: [EMAIL PROTECTED]
  postgresql/enable_lang: true
* postgresql/purge_data_too: false
  postgresql/very_old_version_warning: true
  postgresql/upgrade/dump_location: $PGDATA/..
* postgresql/settings/encoding: LATIN1
  postgresql/convert-pg_hba.conf: true


--- End Message ---
--- Begin Message ---
Hi,

Martin Pitt [Wed, 6 Sep 2006 11:43:07]:
> Robert Suna [2006-09-06 10:37 +0200]:
> > in the log:
> > 
> > FATAL:  XX000: failed to initialize lc_messages to ""
> > LOCATION:  InitializeGUCOptions, guc.c:1880
> 
> It sounds like the glibc upgrade has killed your locales, in
> particular the locale postmaster runs under (the sid/etch packages
> have an explicit check for that since above error message is rather
> unintelligible). Please upgrade your locales package as well and make
> sure that postgres' locale works properly.
> 
> Does that help?

In the absence of any further information there is little I can do
about this. I believe that the reason for the failure is the
explanation above, which is outside the scope of postgresql itself.
The Etch packages have a better error message for this, too.

Thus I am closing this bug until further information arrives.

Thank you!

Martin

-- 
Martin Pitt        http://www.piware.de
Ubuntu Developer   http://www.ubuntu.com
Debian Developer   http://www.debian.org

In a world without walls and fences, who needs Windows and Gates?

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to