This appears to be because Jeff McKenna set up a second postgresql
(using 8.4 instead of 8.3, and apparently not installed via
debian packages) on the same machine, and both are configured to use
the same port.
I've bumped the port of the debian-installed 8.3 to 5433; any applications
depending on this Postgresql instance should change their configuration
accordingly.
-- Chris
On Feb 3, 2011, at 2:41 AM, ext Hamish wrote:
Hi,
after standard "aptitude update && aptitude upgrade" on the adhoc VM, postgresql has not come back up.
"""
Get:10 http://debian.osuosl.org lenny/main postgresql-client-8.3 8.3.13-0lenny1 [1732kB]
Get:11 http://debian.osuosl.org lenny/main postgresql-8.3 8.3.13-0lenny1 [5442kB]
Get:12 http://debian.osuosl.org lenny/main postgresql 8.3.13-0lenny1 [279kB]
...
Preparing to replace postgresql-client-8.3 8.3.12-0lenny1 (using .../postgresql-client-8.3_8.3.13-0lenny1_amd64.deb) ...
Unpacking replacement postgresql-client-8.3 ...
Preparing to replace postgresql-8.3 8.3.12-0lenny1 (using .../postgresql-8.3_8.3.13-0lenny1_amd64.deb) ...
Stopping PostgreSQL 8.3 database server: main.
Unpacking replacement postgresql-8.3 ...
Preparing to replace postgresql 8.3.12-0lenny1 (using .../postgresql_8.3.13-0lenny1_all.deb) ...
Unpacking replacement postgresql ...
...
Setting up postgresql-client-8.3 (8.3.13-0lenny1) ...
Setting up postgresql-8.3 (8.3.13-0lenny1) ...
Starting PostgreSQL 8.3 database server: mainThe PostgreSQL server failed to start. Please check the log output. failed!
failed!
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
dpkg: dependency problems prevent configuration of postgresql:
postgresql depends on postgresql-8.3; however:
Package postgresql-8.3 is not configured yet.
dpkg: error processing postgresql (--configure):
dependency problems - leaving unconfigured
...
Errors were encountered while processing:
postgresql-8.3
postgresql
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up postgresql-8.3 (8.3.13-0lenny1) ...
Starting PostgreSQL 8.3 database server: mainThe PostgreSQL server failed to start. Please check the log output: 2011-02-02 23:30:04 PST LOG: could not load root certificate file "root.crt": no SSL error reported 2011-02-02 23:30:04 PST DETAIL: Will not verify client certificates. 2011-02-02 23:30:04 PST LOG: could not bind IPv4 socket: Address already in use 2011-02-02 23:30:04 PST HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry. 2011-02-02 23:30:04 PST LOG: could not bind IPv6 socket: Address already in use 2011-02-02 23:30:04 PST HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry. 2011-02-02 23:30:04 PST WARNING: could not create listen socket for "localhost" 2011-02-02 23:30:04 PST FATAL: could not create any TCP/IP sockets failed!
failed!
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
dpkg: dependency problems prevent configuration of postgresql:
postgresql depends on postgresql-8.3; however:
Package postgresql-8.3 is not configured yet.
dpkg: error processing postgresql (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
postgresql-8.3
postgresql
"""
On 11-03-06 6:51 PM, christopher.schmidt@nokia.com wrote:
This appears to be because Jeff McKenna set up a second postgresql
(using 8.4 instead of 8.3, and apparently not installed via
debian packages) on the same machine, and both are configured to use
the same port.
I've bumped the port of the debian-installed 8.3 to 5433; any applications
depending on this Postgresql instance should change their configuration
accordingly.
-- Chris
Sorry Chris, this is probably the one installed with FGS by default (even though I don't need PG)...my apologies.
> Sorry Chris, this is probably the one installed with
> FGS by default (even though I don't need PG)...my apologies.
err..I guess I do use that PG instance (FGS) for OSM
data... anyway let me know if you want me to change the port
or whatever...so sorry.
for the record, next time/VM around it would be better if the semi-
official debian PG 8.4 packages from backports.org were used
instead of custom installs, and system wide upgrades/changes
were noted on the adhoc wiki page.
As far as I know no one else is trying to use Postgres on adhoc,
just that the custom install had broken 'apt-get upgrade' for a
while. Mainly bugs in a custom bleeding-edge version of sphinx
someone installed is all that has been causing trouble for me.
thanks,
Hamish
ps- one day in the next year or so we will have to consider
migration plans to the new stable release of debian.
On Mon, Mar 21, 2011 at 11:25 PM, Hamish <hamish_b@yahoo.com> wrote:
...
ps- one day in the next year or so we will have to consider
migration plans to the new stable release of debian.
I just did than on one of my servers, worked out of the box.
The server contains Mailman, 8 CMS, PostgreSQL, Mysql, Zope,
virtual hosts etc. and is a virtual machine. So similar to
ours here.