Hello Bastian, Bastian Blank [2009-02-20 15:32 +0100]: > The postinst of postgresql-8.3 fails if the newly created cluster fails > to start, for example on port clashs: > > | Setting up postgresql-8.3 (8.3.6-1) ... > | Use of uninitialized value in socket at > /usr/share/postgresql-common/PgCommon.pm line 539.
That looks like a bug (not sure if it's the cause for the failure). What's your version of postgresql-client-common? Or alternatively, what is line 539 in that file for you? > | Creating new cluster (configuration: /etc/postgresql/8.3/main, data: > /var/lib/postgresql/8.3/main)... > | Moving configuration file /var/lib/postgresql/8.3/main/postgresql.conf to > /etc/postgresql/8.3/main... > | Moving configuration file /var/lib/postgresql/8.3/main/pg_hba.conf to > /etc/postgresql/8.3/main... > | Moving configuration file /var/lib/postgresql/8.3/main/pg_ident.conf to > /etc/postgresql/8.3/main... > | Configuring postgresql.conf to use port 5433... > | Starting PostgreSQL 8.3 database server: mainThe PostgreSQL server failed > to start. Please check the log output. > | failed! So you are saying that this was an undetected port conflict? Do you already have another cluster running on 5433 which wasn't detected? What does pg_lsclusters show for you? This seems to be the actual bug here. > | invoke-rc.d: initscript postgresql-8.3, action "start" failed. > | dpkg: error processing postgresql-8.3 (--configure): > | subprocess post-installation script returned error exit status 1 > | Errors were encountered while processing: > | postgresql-8.3 I think the Debian Policy mandates that postinst fails if the init script fails, so that the failure doesn't go unnoticed. Do you think it should just go on? Thanks, Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
