Skip site navigation (1) Skip section navigation (2)

BUG #3784: pg_ctl fails to start server when called with -c parameters

From: "Stephen Bespalko" <sjbespa(at)comcast(dot)net>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #3784: pg_ctl fails to start server when called with -c parameters
Date: 2007-11-28 01:44:58
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      3784
Logged by:          Stephen Bespalko
Email address:      sjbespa(at)comcast(dot)net
PostgreSQL version: 8.2.5
Operating system:   Mac OS X 10.5
Description:        pg_ctl fails to start server when called with -c

The following start statement fails, after about 60 seconds:

ntPro" -w -D
"/Users/sjbespa/" -l
"/Users/sjbespa/" -o '-p 7147 
-c log_line_prefix="t2453888748:r:" -c log_error_verbosity=VERBOSE -c
log_min_messages=INFO -c log_min_error_statement=INFO -c
log_connections=true -c log_disconnections=true' start
waiting for server to
not start server

however the same basic statement without the -c parameters works fine:

ntPro" -w -D
"/Users/sjbespa/"  -o '-p 7147'
startwaiting for server to start....LOG:  could not bind IPv6 socket:
Address already in useHINT:  Is another postmaster already running on port
7147? If not, wait a few seconds and retry.
LOG:  database system was shut down at 2007-11-27 18:28:05 MST
LOG:  checkpoint record is at 0/2E55F30
LOG:  redo record is at 0/2E55F30; undo record is at 0/0; shutdown TRUE
LOG:  next transaction ID: 0/2565; next OID: 17130
LOG:  next MultiXactId: 1; next MultiXactOffset: 0
LOG:  database system is ready
server started

From what I can tell, it appears that the parameters specified with the -c
flags are legitimate... If this is not a blunder on my part, I would be
happy to investigate further with a bit of help.

I have modified the postgres programs in /bin with an OS X relative path to
the postgres dynamic library (libpq.5.dylib), so the dbm could be embedded
in an OS X application bundle. I can't see how that would contribute to the
symptoms given that the program works without the offending switches.

Best regards,
Stephen J. Bespalko


pgsql-bugs by date

Next:From: wengxcDate: 2007-11-28 05:43:34
Subject: BUG #3786: report error:"ERROR: invalid byte sequence for encoding "UTF8""
Previous:From: Thomas H.Date: 2007-11-27 18:21:17
Subject: Re: BUG #3766: tsearch2 index creation error

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group