initdb failure

Started by Kevin O'Gormanabout 25 years ago2 messages
#1Kevin O'Gorman
kogorman@pacbell.net
1 attachment(s)

I'm just catching up to the tip of the current tree, and find
that I have a reported failure in initdb. It seems to go through
(most of) the steps, and just reports failure. I can thereafter
start a backend using an old RedHat script (which tries to run
initdb again but can't because the directory is not empty), and
it goes okay.

I've attached a capture of the initdb run. There's not much to
go on there....

++ kevin

--
Kevin O'Gorman (805) 650-6274 mailto:kogorman@pacbell.net
Permanent e-mail forwarder: mailto:Kevin.O'Gorman.64@Alum.Dartmouth.org
At school: mailto:kogorman@cs.ucsb.edu
Web: http://www.cs.ucsb.edu/~kogorman/index.html
Web: http://trixie.kosman.via.ayuda.com/~kevin/index.html

"There is a freedom lying beyond circumstance,
derived from the direct intuition that life can
be grounded upon its absorption in what is
changeless amid change"
-- Alfred North Whitehead

Attachments:

typescripttext/plain; charset=us-ascii; name=typescriptDownload
#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Kevin O'Gorman (#1)
Re: initdb failure

"Kevin O'Gorman" <kogorman@pacbell.net> writes:

I'm just catching up to the tip of the current tree, and find
that I have a reported failure in initdb.

initdb works fine for me (as of CVS from about 11:30AM EST today).
Try running it with -d or -v or whatever the verbose-output option
is to get more info.

regards, tom lane