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

Re: BUG #1271: Installation problems (cannot execute initd b.exe)

From: Harald Armin Massa <haraldarminmassa(at)gmail(dot)com>
To: Ramzi Fadel <raf(at)carlbro(dot)dk>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1271: Installation problems (cannot execute initd b.exe)
Date: 2004-09-30 18:06:39
Message-ID: 7be3f35d040930110679c11892@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Rami,

there is not even a small chance that the admin-restriction will be
dropped within windows. All arguments have been discussed in detail,
and the decision has been made to not drop it by the very core
developers.

You do know of the "runas" command within XP? That helps you in
testing, you can "switch" the secuirity-context "on the fly"

I often use:

runas /user:postgres cmd

and 
runas /user:Administrator cmd

giving me to command-windows with different security-contents.

Also have a look at the "work in progress" silent install within the
"dokumentation" section of pgfoundry.

For now I have posted (to be honest, in testing the "pgfoundry
publishing mechanism")  a batchfile to do a "rather silent" install of
postgres. That batch has to be run with admin privs and should only
require the user to "click through" - maybe it works with your setup
(user postgres is created differentyl)

Harald


On Thu, 30 Sep 2004 09:16:00 +0100, Ramzi Fadel <raf(at)carlbro(dot)dk> wrote:
> 
> Hi Magnus
> 
> I am 99% sure that the users I have tried with are not administrators. I
> have added users that are not member of any groups and still they cannot
> execute initdb after logging in.
> 
> I have earlier installed PostgreSQL but on other machines, and as I remember
> it, I followed the same procedures, so I guess there is some Windows
> security feature that is responsible.
> 
> Why not ommiting the administrator security on Windows builds?
> 
> Ramzi
> 
> -----Original Message-----
> From: Magnus Hagander [mailto:mha(at)sollentuna(dot)net]
> Sent: Wednesday, September 29, 2004 12:20 PM
> To: Ramzi Fadel; Harald Armin Massa
> Subject: RE: [BUGS] BUG #1271: Installation problems (cannot execute
> initdb.exe)
> 
> 
> Please try the steps outlined in FAQ 3.3 at
> http://pginstaller.projects.postgresql.org/FAQ_windows.html#3.3
> 
> //Magnus
> 
> 
> 
> > -----Original Message-----
> > From: Ramzi Fadel [mailto:raf(at)CARLBRO(dot)DK]
> > Sent: Wednesday, September 29, 2004 2:17 PM
> > To: 'Harald Armin Massa'; Magnus Hagander
> > Subject: RE: [BUGS] BUG #1271: Installation problems (cannot
> > execute initdb.exe)
> >
> >
> > Hi Harald and Magnus
> >
> > Thanks for the quick reply.
> >
> > I have tried to install again, but the problem is still that
> > initdb is not allowed to execute.
> >
> > The steps taken are:
> > - Login with user "raf", who has admin privs
> > - During installation the service user is chosen to be
> > "postgres" (does not exsist prior to installation)
> > - The internal user is "postgis" (does not exsist prior to
> > installation)
> > - The files are copied and permissions are granted
> > - Finally initdb fails, the log file (initdb.log) contains
> > the following:
> >
> > The files belonging to this database system will be owned by
> > user "postgres".
> > This user must also own the server process.
> >
> > The database cluster will be initialized with locale C.
> >
> > fixing permissions on existing directory C:/PGSQL80/data ...
> > ok creating directory C:/PGSQL80/data/global ... ok creating
> > directory C:/PGSQL80/data/pg_xlog ... ok creating directory
> > C:/PGSQL80/data/pg_xlog/archive_status ... ok creating
> > directory C:/PGSQL80/data/pg_clog ... ok creating directory
> > C:/PGSQL80/data/pg_subtrans ... ok creating directory
> > C:/PGSQL80/data/base ... ok creating directory
> > C:/PGSQL80/data/base/1 ... ok creating directory
> > C:/PGSQL80/data/pg_tblspc ... ok selecting default
> > max_connections ... 10 selecting default shared_buffers ...
> > 50 creating configuration files ... ok creating template1
> > database in C:/PGSQL80/data/base/1 ... execution of
> > PostgreSQL by a user with administrative permissions is not permitted.
> > The server must be started under an unprivileged user ID to
> > prevent possible system security compromise.  See the
> > documentation for more information on how to properly start
> > the server.
> > child process was terminated by signal 1
> > initdb: failed
> > initdb: removing contents of data directory "C:/PGSQL80/data"
> >
> > -----Original Message-----
> > From: Harald Armin Massa [mailto:haraldarminmassa(at)gmail(dot)com]
> > Sent: Wednesday, September 29, 2004 11:08 AM
> > To: Ramzi Fadel
> > Subject: Re: [BUGS] BUG #1271: Installation problems (cannot execute
> > initdb.exe)
> >
> >
> > Ramzi,
> >
> > your output contains:
> >
> > """
> > PostgreSQL by a user with administrative permissions is not permitted.
> > The server must be started under an unprivileged user ID to
> > prevent possible system security compromise.  See the
> > documentation for more information on how to properly start
> > the server.
> > child process was terminated by signal 1 """
> >
> > that is a clear signal that the user you are using HAS
> > adminstrative permissions. (or the check for admin privs
> > within postgres has a bug, but that is rather unlikeley)
> >
> > Normal way of installation.
> > - log in as a user with admin privs (at least "create
> > service", "create user" ," grant servicelogon right to user")
> > - allow the installer to create a postgres user with limited
> > privileges
> > - allow the installer to run initdb, install service and all
> > -------------------------------
> >
> > there is never a need to log on as postgres-user "on your
> > own" with normal installation. (it is usefull sometimes in
> > debugging, but thats quite after the installstep)
> >
> > Harald
> > --
> > GHUM Harald Massa
> > Harald Armin Massa
> > Reinsburgstra├če 202b
> > 70197 Stuttgart
> > 0173/9409607
> >
> >
> >
> 
> 



-- 
GHUM Harald Massa
Harald Armin Massa
Reinsburgstra├če 202b
70197 Stuttgart
0173/9409607

pgsql-bugs by date

Next:From: Neil ConwayDate: 2004-10-01 00:42:02
Subject: Re: semicolon not required on END statement
Previous:From: Bruce MomjianDate: 2004-09-30 16:37:39
Subject: consultant

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