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

Re: Initdb failing for no apparent reason in 8.0.0beta4 on windows

From: "Steve McWilliams" <smcwilliams(at)EmprisaNetworks(dot)com>
To: <pgsql-hackers-win32(at)postgresql(dot)org>
Cc: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Initdb failing for no apparent reason in 8.0.0beta4 on windows
Date: 2005-01-07 18:38:43
Message-ID: 4514.10.1.1.142.1105123123.squirrel@wwws.emprisanetworks.com (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers-win32
Nevermind, I found out what this was.  Turned out that the customer
machine in question had particularly heavy security settings and so the
enetaware account did not have permission to write into the directory
where it was trying to create PGDATA.  Once I widened the settings on the
parent directory then it worked fine.  Kind of odd that inidb.exe just
fails silently when this is the case however.

> Hello,
>
> We have been using postgres 8.0.0beta4 successfully on various windows
> machines for a while now, but we have run across a particular windows
> machine of one of our customers where initdb.exe is failing with an exit
> code of 1 for no reason that I can determine.  The machine is running
> windows 2000 (sp4, version 5.00.2195).  I have tested in-house
> successfully on windows 2k (sp4, v5.00.2195 as well), windows 2k3, and
> windows xp pro (sp2).
>
> We created a non-administrator account (named "enetaware") on the
> customer machine and given it "log-on-as-service" privileges (we
> ultimately run postgres as a service using this account).  We have the
> postgresql bin, lib, and share directories installed on the customer
> machine in
> "C:\Program Files\EmprisaNetworks\E-NetAware\postgresql".  We execute
> the following command while logged in using this account (-d and -n
> options added temporarily for debugging):
>
> initdb.exe -d -n -U ena -L "C:\Program
> Files\EmprisaNetworks\E-NetAware\postgresql\share" --locale=C
>
> The output from this command is:
>
> Running in noclean mode.  Mistakes will not be cleaned up.
> Running in debug mode.
> VERSION=8.0.0beta4
> PGDATA=C:/E-NetAware-Data/db
> share_path=C:/Program Files/EmprisaNetworks/E-NetAware/postgresql/share
> PGPATH=C:/Program Files/EmprisaNetworks/E-NetAware/postgresql/bin
> POSTGRES_SUPERUSERNAME=ena
> POSTGRES_BKI=C:/Program
> Files/EmprisaNetworks/E-NetAware/postgresql/share/postgr
> es.bki
> POSTGRES_DESCR=C:/Program
> Files/EmprisaNetworks/E-NetAware/postgresql/share/post
> gres.description
> POSTGRESQL_CONF_SAMPLE=C:/Program
> Files/EmprisaNetworks/E-NetAware/postgresql/sh
> are/postgresql.conf.sample
> PG_HBA_SAMPLE=C:/Program
> Files/EmprisaNetworks/E-NetAware/postgresql/share/pg_hb
> a.conf.sample
> PG_IDENT_SAMPLE=C:/Program
> Files/EmprisaNetworks/E-NetAware/postgresql/share/pg_
> ident.conf.sample
> The files belonging to this database system will be owned by user "ena".
> This user must also own the server process.
>
> The database cluster will be initialized with locale C.
>
> creating directory C:/E-NetAware-Data/db ... initdb: failed
>
> The exit code returned by initdb is "1".  Any ideas why this would be
> failing?  I didn't see any similar report about this in the mailing list
> archives.  My next step is to recompile initdb.exe and put in more
> temporary debug print statements and have the customer retry it, however
> that may take a while.
>
> Thanks in advance.
> Steve McWilliams


Steve McWilliams
Software Engineer
Emprisa Networks
703-691-0433x21
smcwilliams(at)emprisanetworks(dot)com

The information contained in this communication is intended only for the
use of the recipient named above, and may be legally privileged,
confidential and exempt from disclosure under applicable law. If the
reader of this communication is not the intended recipient, you are hereby
notified that any dissemination, distribution or copying of this
communication, or any of its contents, is strictly prohibited. If you have
received this communication in error, please resend this communication to
the sender and delete the original communication and any copy of it from
your computer system. Thank you.



In response to

Responses

pgsql-bugs by date

Next:From: Andrew DunstanDate: 2005-01-07 18:52:06
Subject: Re: [pgsql-hackers-win32] Initdb failing for no apparent reason in
Previous:From: Tom LaneDate: 2005-01-07 17:27:52
Subject: Re: Initdb failing for no apparent reason in 8.0.0beta4 on windows

pgsql-hackers-win32 by date

Next:From: Andrew DunstanDate: 2005-01-07 18:52:06
Subject: Re: [pgsql-hackers-win32] Initdb failing for no apparent reason in
Previous:From: Tom LaneDate: 2005-01-07 17:27:52
Subject: Re: Initdb failing for no apparent reason in 8.0.0beta4 on windows

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