pg_ctrl: odd messages logged at startup -

From: Lou Picciano <LouPicciano(at)comcast(dot)net>
To: pgsql-testers(at)postgresql(dot)org
Subject: pg_ctrl: odd messages logged at startup -
Date: 2010-09-12 16:53:02
Message-ID: 7E1BE98A-6948-4909-BD64-AAEB6E6D482A@comcast.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-testers

[TEST REPORT]
[Release]: 9.0 RC1
[Test Type]: Install, initdb, first startup
[Test]: pg_ctrl startup of a newly-intdb'd cluster.
[Platform]: Solaris 10 SUN E450 Quad
[Parameters]: pg_ctrl startup of a newly-intdb'd cluster.
[Failure]: NO. Server starts perfectly. However,
[Results]:
2010-09-12 16:17:43 GMT - LOG: could not open directory "DIR": No such file or directory (Many repetitions)
2010-09-12 12:17:43 EDT - LOG: could not bind IPv6 socket: Cannot assign requested address
2010-09-12 12:17:43 EDT - HINT: Is another postmaster already running on port 5434? If not, wait a few seconds and retry..
[Comments]: None of this a showstopper.
However, we have no 'DIR' in configuration file. What is this?
Is there a way to set 'localhost' listen to use only the IPv4 interface?
There is no postmaster running on 5434 - Could this message either be more informative or - what does it actually mean? We don't see the postmaster.pid file persisting after a shutdown...

Browse pgsql-testers by date

  From Date Subject
Next Message Josh Berkus 2010-09-12 22:23:23 Re: Configure/Build 9.0 rc1 - cannot build against python3.1, with two versions of python in the environment
Previous Message James William Pye 2010-09-12 00:07:46 Re: Configure/Build 9.0 rc1 - cannot build against python3.1, with two versions of python in the environment