Package: postgresql-7.4
Version: 1:7.4.12-2
Severity: normal
When upgrading postgresql-7.4 package from 7.4.12-1 to 7.4.12-2 on an AMD64 box
apt-get outputted this:
---------------------------------------------------------
Unpacking replacement postgresql-client-7.4 ...
Preparing to replace postgresql-7.4 1:7.4.12-1 (using
.../postgresql-7.4_1%3a7.4.12-2_amd64.deb) ...
/etc/init.d/postgresql-7.4: line 17: log_daemon_msg: command not found
/etc/init.d/postgresql-7.4: line 30: log_progress_msg: command not found
[ ok ]
Unpacking replacement postgresql-7.4 ...
[...]
Setting up postgresql-7.4 (7.4.12-2) ...
/etc/init.d/postgresql-7.4: line 17: log_daemon_msg: command not found
/etc/init.d/postgresql-7.4: line 30: log_progress_msg: command not found
[ ok ]
--------------------------------------------------------------------
* * *
On an other AMD64 box I got this:
---------------------------------------------------------------
Preparing to replace postgresql-7.4 1:7.4.12-1 (using
.../postgresql-7.4_1%3a7.4.12-2_amd64.deb) ...
/etc/init.d/postgresql-7.4: line 17: log_daemon_msg: command not found
/etc/init.d/postgresql-7.4: line 30: log_progress_msg: command not found
[fail]
Use of uninitialized value in pattern match (m//) at
/usr/share/postgresql-common/PgCommon.pm line 403.
Use of uninitialized value in pattern match (m//) at
/usr/share/postgresql-common/PgCommon.pm line 409.
Error: specified cluster does not exist
invoke-rc.d: initscript postgresql-7.4, action "stop" failed.
Unpacking replacement postgresql-7.4 ...
[...]
Setting up postgresql-7.4 (7.4.12-2) ...
/etc/init.d/postgresql-7.4: line 17: log_daemon_msg: command not found
*tc/init.d/postgresql-7.4: line 30: log_progress_msg: command not found
[fail]
Use of uninitialized value in pattern match (m//) at
/usr/share/postgresql-common/PgCommon.pm line 403.
Use of uninitialized value in pattern match (m//) at
/usr/share/postgresql-common/PgCommon.pm line 409.
Error: specified cluster does not exist
invoke-rc.d: initscript postgresql-7.4, action "start" failed.
----------------------------------------------------------------------
The message "Error: specified cluster does not exist" is correct, so it's not a
bug,
but the other messages indicate that something else is wrong, too.
* * *
It is of some interest that I have performed the same upgrade on other
(non-AMD64) boxen as well,
it went without any error messages.
Please let me know how can I help you to debug this!
Kristof Csillag
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.12
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages postgresql-7.4 depends on:
ii libc6 2.3.6-3 GNU C Library: Shared libraries an
ii libcomerr2 1.37-2sarge1 common error description library
ii libkrb53 1.4.3-6 MIT Kerberos runtime libraries
ii libpam0g 0.76-22 Pluggable Authentication Modules l
ii libpq3 1:7.4.12-2 PostgreSQL C client library
ii libssl0.9.8 0.9.8a-7 SSL shared libraries
ii postgresql-client-7.4 1:7.4.12-2 front-end programs for PostgreSQL
ii postgresql-common 44 manager for PostgreSQL database cl
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
