Your message dated Sun, 5 Feb 2006 12:59:12 +0000 with message-id <[EMAIL PROTECTED]> and subject line Bug#348628: postgresql: unable to start: failed to initialize lc_message to "" 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 --->From [EMAIL PROTECTED] Tue Jan 17 19:18:52 2006 Received: (at submit) by bugs.debian.org; 18 Jan 2006 03:18:52 +0000 Return-path: <[EMAIL PROTECTED]> Received: from tor-pinab.porchlight.ca ([209.171.52.132]) by spohr.debian.org with esmtp (Exim 4.50) id 1Ez3qW-0007Wp-Ew for [EMAIL PROTECTED]; Tue, 17 Jan 2006 19:18:52 -0800 Received: from bulwark.hooton (tor-ppp-209.29.46.228.porchlight.ca [209.29.46.228]) (authenticated bits=0) by tor-pinab.porchlight.ca (8.13.1/8.13.1) with ESMTP id k0I3IjV4032028 for <[EMAIL PROTECTED]>; Tue, 17 Jan 2006 22:18:46 -0500 Received: from [192.168.1.2] (helo=workstation.hooton ident=Debian-exim) by bulwark.hooton with esmtp (Exim 4.50) id 1Ez3qO-0000Zu-MO for [EMAIL PROTECTED]; Tue, 17 Jan 2006 22:18:44 -0500 Received: from dtutty by workstation.hooton with local (Exim 4.50) id 1Ez3qN-0000rA-Kn for [EMAIL PROTECTED]; Tue, 17 Jan 2006 22:18:43 -0500 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Doug Tutty <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: postgresql: unable to start: failed to initialize lc_message to "" X-Mailer: reportbug 3.8 Date: Tue, 17 Jan 2006 22:18:43 -0500 Message-Id: <[EMAIL PROTECTED]> X-yoursite-MailScanner-Information: Please contact the ISP for more information X-yoursite-MailScanner: Found to be clean X-MailScanner-From: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Level: X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 Package: postgresql Version: 7.4.7-6sarge1 Severity: grave Justification: renders package unusable Starting PostgreSQL database server: postmaster(FAILED) 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 Note re postgresql error: Got this error after rebooting. Prior to rebooting had done a backup which had dump_all'd the database and that file looks fine. Copied the log to the working directory, don't see anything amiss. Try starting again, still get the error message. The FATAL log message is repeated every time I try to start postgresql; note that no time is logged. The shutdown started, according to syslog at 18:05:45, and kernel log daemon exited at 18:06:04, restarting at 18:12:00. (after full file system check). Here's the output from mount and df: /dev/hda5 on / type ext3 (rw,errors=remount-ro) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) /dev/hda1 on /boot type ext3 (rw) /dev/hda6 on /home type reiserfs (rw) /dev/hdc1 on /tmp type reiserfs (rw) /dev/hdc5 on /usr type reiserfs (rw) /dev/hdc6 on /var type reiserfs (rw) usbfs on /proc/bus/usb type usbfs (rw) bulwark:/var/mail on /var/mail type nfs (rw,fg,hard,intr,rsize=8192,wsize=8192,addr=192.168.1.1) bulwark:/usr on /mnt/bulwark/usr type nfs (rw,noexec,nosuid,nodev,bg,hard,intr,rsize=8192,wsize=8192,addr=192.168.1.1) Filesystem Size Used Avail Use% Mounted on /dev/hda5 96M 69M 23M 75% / tmpfs 32M 0 32M 0% /dev/shm /dev/hda1 16M 8.0M 7.3M 53% /boot /dev/hda6 1.2G 133M 1.1G 12% /home /dev/hdc1 1.1G 34M 987M 4% /tmp /dev/hdc5 2.1G 1.4G 702M 66% /usr /dev/hdc6 3.4G 885M 2.5G 27% /var bulwark:/var/mail 189M 62M 128M 33% /var/mail bulwark:/usr 131M 86M 45M 66% /mnt/bulwark/usr I didn't sit and watch the file system check. Try shutdown -hF (maybe its a power thing) and watch the boot up. No help. Check debian web site for bug reporting stuff. installing report bug. Checking aptitude, we have postgresql 7.4.7-6sarge1 Here's the log file: 2006-01-17 09:53:19 [16457] LOG: connection received: host=[local] port= 2006-01-17 09:53:19 [16457] LOG: connection authorized: user=postgres database=template1 2006-01-17 09:53:23 [16460] LOG: connection received: host=[local] port= 2006-01-17 09:53:23 [16460] LOG: connection authorized: user=postgres database=house 2006-01-17 09:53:33 [16463] LOG: connection received: host=[local] port= 2006-01-17 09:53:34 [16463] LOG: connection authorized: user=postgres database=template1 2006-01-17 10:02:05 [16689] LOG: connection received: host=[local] port= 2006-01-17 10:02:05 [16689] LOG: connection authorized: user=postgres database=template1 2006-01-17 10:02:08 [16699] LOG: connection received: host=[local] port= 2006-01-17 10:02:08 [16699] LOG: connection authorized: user=postgres database=template1 2006-01-17 10:02:08 [16700] LOG: connection received: host=[local] port= 2006-01-17 10:02:08 [16700] LOG: connection authorized: user=postgres database=house 2006-01-17 10:02:43 [16714] LOG: connection received: host=[local] port= 2006-01-17 10:02:44 [16714] LOG: connection authorized: user=postgres database=template1 2006-01-17 15:02:02 [17499] LOG: connection received: host=[local] port= 2006-01-17 15:02:02 [17499] LOG: connection authorized: user=postgres database=template1 2006-01-17 15:02:04 [17509] LOG: connection received: host=[local] port= 2006-01-17 15:02:04 [17509] LOG: connection authorized: user=postgres database=template1 2006-01-17 15:02:04 [17510] LOG: connection received: host=[local] port= 2006-01-17 15:02:04 [17510] LOG: connection authorized: user=postgres database=house 2006-01-17 15:02:16 [17511] LOG: connection received: host=[local] port= 2006-01-17 15:02:16 [17511] LOG: connection authorized: user=postgres database=template1 2006-01-17 18:05:58 [2081] LOG: received fast shutdown request 2006-01-17 18:05:58 [18431] LOG: shutting down 2006-01-17 18:06:01 [18431] LOG: database system is shut down FATAL: XX000: failed to initialize lc_messages to "" LOCATION: InitializeGUCOptions, guc.c:1867 FATAL: XX000: failed to initialize lc_messages to "" LOCATION: InitializeGUCOptions, guc.c:1867 FATAL: XX000: failed to initialize lc_messages to "" LOCATION: InitializeGUCOptions, guc.c:1867 FATAL: XX000: failed to initialize lc_messages to "" LOCATION: InitializeGUCOptions, guc.c:1867 -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.8-2-686 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-22 GNU C Library: Shared libraries an ii libcomerr2 1.37-2sarge1 common error description library ii libkrb53 1.3.6-2sarge2 MIT Kerberos runtime libraries ii libpam0g 0.76-22 Pluggable Authentication Modules l ii libperl5.8 5.8.4-8sarge3 Shared Perl library ii libpq3 7.4.7-6sarge1 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-6sarge1 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: /var/lib/postgres/preserve * postgresql/settings/day_month_order: European * postgresql/upgrade/policy: true * postgresql/settings/locale: C postgresql/enable_lang: true * postgresql/purge_data_too: false postgresql/very_old_version_warning: true * postgresql/upgrade/dump_location: /var/lib/postgres/ * postgresql/convert-pg_hba.conf: true ----------hardware and setup information: Intel P-II 233 MHz, 64 Mb ram, 512 L2 cache, Asus P2L97 AGP motherboard This computer, hostname 'workstation' has been my primary workstation, with an old P-75 'bulwark' as firewall, dnsmasq, exim4 etc server. A few days ago, I started down-sizing the installed packages preparatory to expanding the network to include a file server 'keep' to allow this workstation to spend more time doing my stuff, however to do that, a hard-drive swap is needed. Anyway, after the reduction in package load, postgres continued to work well, and completed a backup prior to the shutdown after which it refused to start. I got this computer and the hard drives free. I don't know anything about their history. On of the plans on the new set up is to change from reiserfs to jfs, so that I can catch bad blocks; I'm wondering if something wonky on the disk in the midst of what postgresql needs is causing a problem. Since I have full backups and postgresql now isn't functional, I plan to remove and reinstall postgresql. I'll leave it for a few days in case you want me to try anything to help pin this down. Thanks, Doug Tutty, Kingston, Ontario, Canada. [EMAIL PROTECTED]
--- End Message ---
--- Begin Message --->From [EMAIL PROTECTED] Sun Feb 05 11:10:30 2006 Received: (at 348628-done) by bugs.debian.org; 5 Feb 2006 19:10:30 +0000 Return-path: <[EMAIL PROTECTED]> Received: from box79162.elkhouse.de ([213.9.79.162]) by spohr.debian.org with esmtp (Exim 4.50) id 1F5pHJ-0001uV-T4 for [EMAIL PROTECTED]; Sun, 05 Feb 2006 11:10:30 -0800 Received: from localhost.localdomain (unknown [195.227.105.180]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Martin Pitt (iBook)", Issuer "piware CA" (verified OK)) by box79162.elkhouse.de (Postfix) with ESMTP id 95CE9E34A3 for <[EMAIL PROTECTED]>; Sun, 5 Feb 2006 20:09:53 +0100 (CET) Received: by localhost.localdomain (Postfix, from userid 1000) id BAC2C11E05; Sun, 5 Feb 2006 12:59:12 +0000 (GMT) Date: Sun, 5 Feb 2006 12:59:12 +0000 From: Martin Pitt <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: Bug#348628: postgresql: unable to start: failed to initialize lc_message to "" Message-ID: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <[EMAIL PROTECTED]> User-Agent: Mutt/1.5.11 X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Level: X-Spam-Status: No, hits=-1.2 required=4.0 tests=BAYES_00,DATE_IN_PAST_06_12, HAS_BUG_NUMBER,RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_SBLXBL, RCVD_IN_SBLXBL_CBL,RCVD_IN_SORBS,RCVD_IN_SORBS_WEB autolearn=no version=2.60-bugs.debian.org_2005_01_02 Hi again, Martin Pitt [2006-01-18 8:50 +0100]: > tag 348628 moreinfo > severity 348628 normal > thanks > > Hi Doug! > > Doug Tutty [2006-01-17 22:18 -0500]: > > FATAL: XX000: failed to initialize lc_messages to "" > > LOCATION: InitializeGUCOptions, guc.c:1867 > > FATAL: XX000: failed to initialize lc_messages to "" > > LOCATION: InitializeGUCOptions, guc.c:1867 > > FATAL: XX000: failed to initialize lc_messages to "" > > LOCATION: InitializeGUCOptions, guc.c:1867 > > FATAL: XX000: failed to initialize lc_messages to "" > > LOCATION: InitializeGUCOptions, guc.c:1867 > > This actually looks very familiar. It happens if the database was once > initialized with a locale that doesn't exist any more. Did you happen > to remove the 'locales' package in your clean-up process? If so, > please install it again. If you really want to run the postmaster in > the default POSIX locale (which I do not recommend, but other people > want it like that), then purge and reinstall postgresql, choose 'C' as > locale and feed back the dump. No answer to this mail, and I'm fairly sure that this is due to the removal of the underlying locale, thus I'm closing this now. Martin -- Martin Pitt http://www.piware.de Ubuntu Developer http://www.ubuntu.com Debian Developer http://www.debian.org
--- End Message ---
