Workaround for bug #4608?

I'm experiencing bug 4608

http://archives.postgresql.org/pgsql-bugs/2009-01/msg00062.php

I have tried using the Windows one-click installer for both 8.3.x and
8.4. At the end of the process it says it can't read
data/postgres.conf and none of the conf files are generated.

I'm pretty surprised that this issue - which prevents me from
installing and running PostgreSQL on Windows - was reported in Jan.
and the only documentation I could find on it was this 1 bug with no
comments. Perhaps the original reporter and I are the only ones
experiencing this issue?

Anyway, does anyone have any ideas for a workaround?

Thanks,

Robert Campbell

Robert Campbell wrote:
> I'm experiencing bug 4608
>
> http://archives.postgresql.org/pgsql-bugs/2009-01/msg00062.php
>
> I have tried using the Windows one-click installer for both 8.3.x and
> 8.4. At the end of the process it says it can't read
> data/postgres.conf and none of the conf files are generated.
>
> I'm pretty surprised that this issue - which prevents me from
> installing and running PostgreSQL on Windows - was reported in Jan.
> and the only documentation I could find on it was this 1 bug with no
> comments. Perhaps the original reporter and I are the only ones
> experiencing this issue?
>
> Anyway, does anyone have any ideas for a workaround?

I think the issue is that we don't know what would cause that.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

Hi Bruce,

Thanks for the reply and for building the installer. Is there anything
I can do to help you pinpoint the problem? Some install logs I can
send or something of that sort?

Rob

On Wed, Apr 22, 2009 at 2:33 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Robert Campbell wrote:
>> I'm experiencing bug 4608
>>
>> http://archives.postgresql.org/pgsql-bugs/2009-01/msg00062.php
>>
>> I have tried using the Windows one-click installer for both 8.3.x and
>> 8.4. At the end of the process it says it can't read
>> data/postgres.conf and none of the conf files are generated.
>>
>> I'm pretty surprised that this issue - which prevents me from
>> installing and running PostgreSQL on Windows - was reported in Jan.
>> and the only documentation I could find on it was this 1 bug with no
>> comments. Perhaps the original reporter and I are the only ones
>> experiencing this issue?
>>
>> Anyway, does anyone have any ideas for a workaround?
>
> I think the issue is that we don't know what would cause that.
>
> --
>  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
>  EnterpriseDB                             http://enterprisedb.com
>
>  + If your life is a hard drive, Christ can be your backup. +
>

Robert Campbell wrote:
> Hi Bruce,
>
> Thanks for the reply and for building the installer. Is there anything
> I can do to help you pinpoint the problem? Some install logs I can
> send or something of that sort?

I hope someone with more Win32 experience can help you; did you look in
the event logs?

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

There are some in the Application log, but they are all symptoms of
the problem and don't really document why it happened initially:

"postgres cannot access the server configuration file "E:/Program
Files/PostgreSQL/8.3/data/postgresql.conf": No such file or directory"

"pg_ctl: PID file "E:/Program
Files/PostgreSQL/8.3/data/postmaster.pid" does not exist"

The data directory is simply empty.

On Wed, Apr 22, 2009 at 2:43 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Robert Campbell wrote:
>> Hi Bruce,
>>
>> Thanks for the reply and for building the installer. Is there anything
>> I can do to help you pinpoint the problem? Some install logs I can
>> send or something of that sort?
>
> I hope someone with more Win32 experience can help you;  did you look in
> the event logs?
>
> --
>  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
>  EnterpriseDB                             http://enterprisedb.com
>
>  + If your life is a hard drive, Christ can be your backup. +
>

Robert Campbell wrote:
> There are some in the Application log, but they are all symptoms of
> the problem and don't really document why it happened initially:
>
> "postgres cannot access the server configuration file "E:/Program
> Files/PostgreSQL/8.3/data/postgresql.conf": No such file or directory"
>
> "pg_ctl: PID file "E:/Program
> Files/PostgreSQL/8.3/data/postmaster.pid" does not exist"
>
> The data directory is simply empty.

Yea, that doesn't seem helpful. So there is nothing related to the
installation itself? I am wondering if it is a virus program problem.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

We do have McAfee running, which has caused problems in the past with
blocking some outgoing connections, but for that reason we have it
turned off always (can't uninstall due to automatic updates, etc).

On Wed, Apr 22, 2009 at 3:00 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Robert Campbell wrote:
>> There are some in the Application log, but they are all symptoms of
>> the problem and don't really document why it happened initially:
>>
>> "postgres cannot access the server configuration file "E:/Program
>> Files/PostgreSQL/8.3/data/postgresql.conf": No such file or directory"
>>
>> "pg_ctl: PID file "E:/Program
>> Files/PostgreSQL/8.3/data/postmaster.pid" does not exist"
>>
>> The data directory is simply empty.
>
> Yea, that doesn't seem helpful.  So there is nothing related to the
> installation itself?  I am wondering if it is a virus program problem.
>
> --
>  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
>  EnterpriseDB                             http://enterprisedb.com
>
>  + If your life is a hard drive, Christ can be your backup. +
>

Robert Campbell wrote:
> We do have McAfee running, which has caused problems in the past with
> blocking some outgoing connections, but for that reason we have it
> turned off always (can't uninstall due to automatic updates, etc).

Oh, it is off, hmm. I don't see Magnus on IM now but I am hoping one
of our Win32 guys has an idea.

I am moving this email over to the bugs list. Folks, here is a history
of the bug report; it seems he can't install in /data on Windows:

http://archives.postgresql.org//pgsql-novice/2009-04/msg00079.php

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

Rob,

Is this on a Windows 2003 server and is it part of a domain.
I recall having this problem with my windows 2003 servers in this domain and I couldn't install on any of them. (I think the 8.3 of the enterprise db+ ), though it installed fine on the windows xp boxes in the domain using a local postgres account.

The only thing I noticed is when the data cluster was being created it would remove all the permissions (so wasn't sure if it was becuase I was using a postgres domain account or not)

Anyrate to skirt around the issue, I manually set the permissions, and ended up manually initing the db and it worked fine. Though I was kind of pressed for time so didn't really bother investigating the issue. I suppose I can try again on a another server to recreate the issue if it would help.

Does it create the data cluster at all? In my case it would create the data folder but nothing in it.

Hope that helps,
Regina

-----Original Message-----
From: pgsql-novice-owner(at)postgresql(dot)org [mailto:pgsql-novice-owner(at)postgresql(dot)org] On Behalf Of Robert Campbell
Sent: Wednesday, April 22, 2009 8:35 AM
To: Bruce Momjian
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: [NOVICE] Workaround for bug #4608?

Hi Bruce,

Thanks for the reply and for building the installer. Is there anything
I can do to help you pinpoint the problem? Some install logs I can
send or something of that sort?

Rob

On Wed, Apr 22, 2009 at 2:33 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Robert Campbell wrote:
>> I'm experiencing bug 4608
>>
>> http://archives.postgresql.org/pgsql-bugs/2009-01/msg00062.php
>>
>> I have tried using the Windows one-click installer for both 8.3.x and
>> 8.4. At the end of the process it says it can't read
>> data/postgres.conf and none of the conf files are generated.
>>
>> I'm pretty surprised that this issue - which prevents me from
>> installing and running PostgreSQL on Windows - was reported in Jan.
>> and the only documentation I could find on it was this 1 bug with no
>> comments. Perhaps the original reporter and I are the only ones
>> experiencing this issue?
>>
>> Anyway, does anyone have any ideas for a workaround?
>
> I think the issue is that we don't know what would cause that.
>
> --
>  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
>  EnterpriseDB                             http://enterprisedb.com
>
>  + If your life is a hard drive, Christ can be your backup. +
>

--
Sent via pgsql-novice mailing list (pgsql-novice(at)postgresql(dot)org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-novice
-----------------------------------------
The substance of this message, including any attachments, may be
confidential, legally privileged and/or exempt from disclosure
pursuant to Massachusetts law. It is intended
solely for the addressee. If you received this in error, please
contact the sender and delete the material from any computer.

Rob,
Forgot to mention the other distinction here is that I was installing via terminal service (but I had it set to console mode). I have installed via terminal service before on web facing windows 2003 servers that are not part of a domain and had no issues. So I ruled that out as a culprit.

Anyrate if you are installing via terminal service, I think it still holds true that you must connect via console mode.

Hope that helps,
Regina

-----Original Message-----
From: Obe, Regina
Sent: Wednesday, April 22, 2009 9:37 AM
To: 'Robert Campbell'; Bruce Momjian
Cc: pgsql-novice(at)postgresql(dot)org
Subject: RE: [NOVICE] Workaround for bug #4608?

Rob,

Is this on a Windows 2003 server and is it part of a domain.
I recall having this problem with my windows 2003 servers in this domain and I couldn't install on any of them. (I think the 8.3 of the enterprise db+ ), though it installed fine on the windows xp boxes in the domain using a local postgres account.

The only thing I noticed is when the data cluster was being created it would remove all the permissions (so wasn't sure if it was becuase I was using a postgres domain account or not)

Anyrate to skirt around the issue, I manually set the permissions, and ended up manually initing the db and it worked fine. Though I was kind of pressed for time so didn't really bother investigating the issue. I suppose I can try again on a another server to recreate the issue if it would help.

Does it create the data cluster at all? In my case it would create the data folder but nothing in it.

Hope that helps,
Regina

-----Original Message-----
From: pgsql-novice-owner(at)postgresql(dot)org [mailto:pgsql-novice-owner(at)postgresql(dot)org] On Behalf Of Robert Campbell
Sent: Wednesday, April 22, 2009 8:35 AM
To: Bruce Momjian
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: [NOVICE] Workaround for bug #4608?

Hi Bruce,

Thanks for the reply and for building the installer. Is there anything
I can do to help you pinpoint the problem? Some install logs I can
send or something of that sort?

Rob

On Wed, Apr 22, 2009 at 2:33 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Robert Campbell wrote:
>> I'm experiencing bug 4608
>>
>> http://archives.postgresql.org/pgsql-bugs/2009-01/msg00062.php
>>
>> I have tried using the Windows one-click installer for both 8.3.x and
>> 8.4. At the end of the process it says it can't read
>> data/postgres.conf and none of the conf files are generated.
>>
>> I'm pretty surprised that this issue - which prevents me from
>> installing and running PostgreSQL on Windows - was reported in Jan.
>> and the only documentation I could find on it was this 1 bug with no
>> comments. Perhaps the original reporter and I are the only ones
>> experiencing this issue?
>>
>> Anyway, does anyone have any ideas for a workaround?
>
> I think the issue is that we don't know what would cause that.
>
> --
>  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
>  EnterpriseDB                             http://enterprisedb.com
>
>  + If your life is a hard drive, Christ can be your backup. +
>

--
Sent via pgsql-novice mailing list (pgsql-novice(at)postgresql(dot)org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-novice
-----------------------------------------
The substance of this message, including any attachments, may be
confidential, legally privileged and/or exempt from disclosure
pursuant to Massachusetts law. It is intended
solely for the addressee. If you received this in error, please
contact the sender and delete the material from any computer.

Hi Obe,

I'm running XP Pro, SP 2. Not running via Remote Desktop, this is
local. We don't use Windows Networking, but rather Novell Client (I
know, gag).

It does create the data folder, but it's completely empty. Also, this
happens during the "Loading additional SQL modules..." part of Setup
towards the end.

Also, to manually create the DB, I need the server running, correct? I
can't boot up the server. When I try to bring up the server in
pgAdminIII I get a connection error. From the Events log it looks like
the server won't start because of the previously mentioned errors.
Basically after logging those error, it logs "Is server running?" to
which the answer appears to be "no".

On Wed, Apr 22, 2009 at 3:40 PM, Obe, Regina <robe(dot)dnd(at)cityofboston(dot)gov> wrote:
> Rob,
> Forgot to mention the other distinction here is that I was installing via terminal service (but I had it set to console mode).  I have installed via terminal service before on web facing windows 2003 servers that are not part of a domain and had no issues.  So I ruled that out as a culprit.
>
> Anyrate if you are installing via terminal service,  I think it still holds true that you must connect via console mode.
>
> Hope that helps,
> Regina
>
> -----Original Message-----
> From: Obe, Regina
> Sent: Wednesday, April 22, 2009 9:37 AM
> To: 'Robert Campbell'; Bruce Momjian
> Cc: pgsql-novice(at)postgresql(dot)org
> Subject: RE: [NOVICE] Workaround for bug #4608?
>
> Rob,
>
> Is this on a Windows 2003 server and is it part of a domain.
> I recall having this problem with my windows 2003 servers in this domain and I couldn't install on any of them. (I think the 8.3 of the enterprise db+ ), though it installed fine on the windows xp boxes in the domain using a local postgres account.
>
> The only thing I noticed is when the data cluster was being created it would remove all the permissions (so wasn't sure if it was becuase I was using a postgres domain account or not)
>
> Anyrate to skirt around the issue, I manually set the permissions, and ended up manually initing the db and it worked fine.  Though I was kind of pressed for time so didn't really bother investigating the issue.  I suppose I can try again on a another server to recreate the issue if it would help.
>
> Does it create the data cluster at all?  In my case it would create the data folder but nothing in it.
>
> Hope that helps,
> Regina
>
> -----Original Message-----
> From: pgsql-novice-owner(at)postgresql(dot)org [mailto:pgsql-novice-owner(at)postgresql(dot)org] On Behalf Of Robert Campbell
> Sent: Wednesday, April 22, 2009 8:35 AM
> To: Bruce Momjian
> Cc: pgsql-novice(at)postgresql(dot)org
> Subject: Re: [NOVICE] Workaround for bug #4608?
>
> Hi Bruce,
>
> Thanks for the reply and for building the installer. Is there anything
> I can do to help you pinpoint the problem? Some install logs I can
> send or something of that sort?
>
> Rob
>
>
>
> On Wed, Apr 22, 2009 at 2:33 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>> Robert Campbell wrote:
>>> I'm experiencing bug 4608
>>>
>>> http://archives.postgresql.org/pgsql-bugs/2009-01/msg00062.php
>>>
>>> I have tried using the Windows one-click installer for both 8.3.x and
>>> 8.4. At the end of the process it says it can't read
>>> data/postgres.conf and none of the conf files are generated.
>>>
>>> I'm pretty surprised that this issue - which prevents me from
>>> installing and running PostgreSQL on Windows - was reported in Jan.
>>> and the only documentation I could find on it was this 1 bug with no
>>> comments. Perhaps the original reporter and I are the only ones
>>> experiencing this issue?
>>>
>>> Anyway, does anyone have any ideas for a workaround?
>>
>> I think the issue is that we don't know what would cause that.
>>
>> --
>>  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
>>  EnterpriseDB                             http://enterprisedb.com
>>
>>  + If your life is a hard drive, Christ can be your backup. +
>>
>
> --
> Sent via pgsql-novice mailing list (pgsql-novice(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-novice
> -----------------------------------------
> The substance of this message, including any attachments, may be
> confidential, legally privileged and/or exempt from disclosure
> pursuant to Massachusetts law. It is intended
> solely for the addressee. If you received this in error, please
> contact the sender and delete the material from any computer.
>

Robert,

Sorry I meant to say manually init the database cluster and register the service. All this do from a dos prompt.

So you init the cluster like this
"C:\Program Files\PostgreSQL\8.3\bin\initdb" -D "C:\PGData83"

And manually register the service like this
"C:\Program Files\PostgreSQL\8.3\bin\pg_ctl.exe" register -N "pgsql-8.3" -D "C:\PGData83\" -U postgres -P "NT passwordgoes here"

Hope that helps,
Regina

-----Original Message-----
From: Robert Campbell [mailto:rrc7cz(at)gmail(dot)com]
Sent: Wednesday, April 22, 2009 9:56 AM
To: Obe, Regina
Cc: Bruce Momjian; pgsql-novice(at)postgresql(dot)org
Subject: Re: [NOVICE] Workaround for bug #4608?

Hi Obe,

I'm running XP Pro, SP 2. Not running via Remote Desktop, this is
local. We don't use Windows Networking, but rather Novell Client (I
know, gag).

It does create the data folder, but it's completely empty. Also, this
happens during the "Loading additional SQL modules..." part of Setup
towards the end.

Also, to manually create the DB, I need the server running, correct? I
can't boot up the server. When I try to bring up the server in
pgAdminIII I get a connection error. From the Events log it looks like
the server won't start because of the previously mentioned errors.
Basically after logging those error, it logs "Is server running?" to
which the answer appears to be "no".

On Wed, Apr 22, 2009 at 3:40 PM, Obe, Regina <robe(dot)dnd(at)cityofboston(dot)gov> wrote:
> Rob,
> Forgot to mention the other distinction here is that I was installing via terminal service (but I had it set to console mode).  I have installed via terminal service before on web facing windows 2003 servers that are not part of a domain and had no issues.  So I ruled that out as a culprit.
>
> Anyrate if you are installing via terminal service,  I think it still holds true that you must connect via console mode.
>
> Hope that helps,
> Regina
>
> -----Original Message-----
> From: Obe, Regina
> Sent: Wednesday, April 22, 2009 9:37 AM
> To: 'Robert Campbell'; Bruce Momjian
> Cc: pgsql-novice(at)postgresql(dot)org
> Subject: RE: [NOVICE] Workaround for bug #4608?
>
> Rob,
>
> Is this on a Windows 2003 server and is it part of a domain.
> I recall having this problem with my windows 2003 servers in this domain and I couldn't install on any of them. (I think the 8.3 of the enterprise db+ ), though it installed fine on the windows xp boxes in the domain using a local postgres account.
>
> The only thing I noticed is when the data cluster was being created it would remove all the permissions (so wasn't sure if it was becuase I was using a postgres domain account or not)
>
> Anyrate to skirt around the issue, I manually set the permissions, and ended up manually initing the db and it worked fine.  Though I was kind of pressed for time so didn't really bother investigating the issue.  I suppose I can try again on a another server to recreate the issue if it would help.
>
> Does it create the data cluster at all?  In my case it would create the data folder but nothing in it.
>
> Hope that helps,
> Regina
>
> -----Original Message-----
> From: pgsql-novice-owner(at)postgresql(dot)org [mailto:pgsql-novice-owner(at)postgresql(dot)org] On Behalf Of Robert Campbell
> Sent: Wednesday, April 22, 2009 8:35 AM
> To: Bruce Momjian
> Cc: pgsql-novice(at)postgresql(dot)org
> Subject: Re: [NOVICE] Workaround for bug #4608?
>
> Hi Bruce,
>
> Thanks for the reply and for building the installer. Is there anything
> I can do to help you pinpoint the problem? Some install logs I can
> send or something of that sort?
>
> Rob
>
>
>
> On Wed, Apr 22, 2009 at 2:33 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>> Robert Campbell wrote:
>>> I'm experiencing bug 4608
>>>
>>> http://archives.postgresql.org/pgsql-bugs/2009-01/msg00062.php
>>>
>>> I have tried using the Windows one-click installer for both 8.3.x and
>>> 8.4. At the end of the process it says it can't read
>>> data/postgres.conf and none of the conf files are generated.
>>>
>>> I'm pretty surprised that this issue - which prevents me from
>>> installing and running PostgreSQL on Windows - was reported in Jan.
>>> and the only documentation I could find on it was this 1 bug with no
>>> comments. Perhaps the original reporter and I are the only ones
>>> experiencing this issue?
>>>
>>> Anyway, does anyone have any ideas for a workaround?
>>
>> I think the issue is that we don't know what would cause that.
>>
>> --
>>  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
>>  EnterpriseDB                             http://enterprisedb.com
>>
>>  + If your life is a hard drive, Christ can be your backup. +
>>
>
> --
> Sent via pgsql-novice mailing list (pgsql-novice(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-novice
> -----------------------------------------
> The substance of this message, including any attachments, may be
> confidential, legally privileged and/or exempt from disclosure
> pursuant to Massachusetts law. It is intended
> solely for the addressee. If you received this in error, please
> contact the sender and delete the material from any computer.
>

Okay here's where things get strange. I ran initdb and got this error:

--------
C:\Program Files\PostgreSQL\8.3\bin>initdb -D "C:\Program
Files\PostgreSQL\8.3\data"
The files belonging to this data... <text here>

initdb: could not access directory "C:/Program
Files/PostgreSQL/8.3/data": No such file or directory
--------

Now the odd part is if I copy the same path I provided and "cd" to it,
it works. I can paste it into Windows Explorer and it's there. I mean
clearly I can see it there.

If I pass a different directory, such as C:/PgData38, it runs fine.

Perhaps this is the problem the Setup script encounters?

On Wed, Apr 22, 2009 at 4:02 PM, Obe, Regina <robe(dot)dnd(at)cityofboston(dot)gov> wrote:
> Robert,
>
> Sorry I meant to say manually init the database cluster and register the service.  All this do from a dos prompt.
>
> So you init the cluster like this
> "C:\Program Files\PostgreSQL\8.3\bin\initdb" -D "C:\PGData83"
>
> And manually register the service like this
> "C:\Program Files\PostgreSQL\8.3\bin\pg_ctl.exe" register -N "pgsql-8.3" -D "C:\PGData83\" -U postgres -P "NT passwordgoes here"
>
> Hope that helps,
> Regina
>
> -----Original Message-----
> From: Robert Campbell [mailto:rrc7cz(at)gmail(dot)com]
> Sent: Wednesday, April 22, 2009 9:56 AM
> To: Obe, Regina
> Cc: Bruce Momjian; pgsql-novice(at)postgresql(dot)org
> Subject: Re: [NOVICE] Workaround for bug #4608?
>
> Hi Obe,
>
> I'm running XP Pro, SP 2. Not running via Remote Desktop, this is
> local. We don't use Windows Networking, but rather Novell Client (I
> know, gag).
>
> It does create the data folder, but it's completely empty. Also, this
> happens during the "Loading additional SQL modules..." part of Setup
> towards the end.
>
> Also, to manually create the DB, I need the server running, correct? I
> can't boot up the server. When I try to bring up the server in
> pgAdminIII I get a connection error. From the Events log it looks like
> the server won't start because of the previously mentioned errors.
> Basically after logging those error, it logs "Is server running?" to
> which the answer appears to be "no".
>
>
>
> On Wed, Apr 22, 2009 at 3:40 PM, Obe, Regina <robe(dot)dnd(at)cityofboston(dot)gov> wrote:
>> Rob,
>> Forgot to mention the other distinction here is that I was installing via terminal service (but I had it set to console mode).  I have installed via terminal service before on web facing windows 2003 servers that are not part of a domain and had no issues.  So I ruled that out as a culprit.
>>
>> Anyrate if you are installing via terminal service,  I think it still holds true that you must connect via console mode.
>>
>> Hope that helps,
>> Regina
>>
>> -----Original Message-----
>> From: Obe, Regina
>> Sent: Wednesday, April 22, 2009 9:37 AM
>> To: 'Robert Campbell'; Bruce Momjian
>> Cc: pgsql-novice(at)postgresql(dot)org
>> Subject: RE: [NOVICE] Workaround for bug #4608?
>>
>> Rob,
>>
>> Is this on a Windows 2003 server and is it part of a domain.
>> I recall having this problem with my windows 2003 servers in this domain and I couldn't install on any of them. (I think the 8.3 of the enterprise db+ ), though it installed fine on the windows xp boxes in the domain using a local postgres account.
>>
>> The only thing I noticed is when the data cluster was being created it would remove all the permissions (so wasn't sure if it was becuase I was using a postgres domain account or not)
>>
>> Anyrate to skirt around the issue, I manually set the permissions, and ended up manually initing the db and it worked fine.  Though I was kind of pressed for time so didn't really bother investigating the issue.  I suppose I can try again on a another server to recreate the issue if it would help.
>>
>> Does it create the data cluster at all?  In my case it would create the data folder but nothing in it.
>>
>> Hope that helps,
>> Regina
>>
>> -----Original Message-----
>> From: pgsql-novice-owner(at)postgresql(dot)org [mailto:pgsql-novice-owner(at)postgresql(dot)org] On Behalf Of Robert Campbell
>> Sent: Wednesday, April 22, 2009 8:35 AM
>> To: Bruce Momjian
>> Cc: pgsql-novice(at)postgresql(dot)org
>> Subject: Re: [NOVICE] Workaround for bug #4608?
>>
>> Hi Bruce,
>>
>> Thanks for the reply and for building the installer. Is there anything
>> I can do to help you pinpoint the problem? Some install logs I can
>> send or something of that sort?
>>
>> Rob
>>
>>
>>
>> On Wed, Apr 22, 2009 at 2:33 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>>> Robert Campbell wrote:
>>>> I'm experiencing bug 4608
>>>>
>>>> http://archives.postgresql.org/pgsql-bugs/2009-01/msg00062.php
>>>>
>>>> I have tried using the Windows one-click installer for both 8.3.x and
>>>> 8.4. At the end of the process it says it can't read
>>>> data/postgres.conf and none of the conf files are generated.
>>>>
>>>> I'm pretty surprised that this issue - which prevents me from
>>>> installing and running PostgreSQL on Windows - was reported in Jan.
>>>> and the only documentation I could find on it was this 1 bug with no
>>>> comments. Perhaps the original reporter and I are the only ones
>>>> experiencing this issue?
>>>>
>>>> Anyway, does anyone have any ideas for a workaround?
>>>
>>> I think the issue is that we don't know what would cause that.
>>>
>>> --
>>>  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
>>>  EnterpriseDB                             http://enterprisedb.com
>>>
>>>  + If your life is a hard drive, Christ can be your backup. +
>>>
>>
>> --
>> Sent via pgsql-novice mailing list (pgsql-novice(at)postgresql(dot)org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-novice
>> -----------------------------------------
>> The substance of this message, including any attachments, may be
>> confidential, legally privileged and/or exempt from disclosure
>> pursuant to Massachusetts law. It is intended
>> solely for the addressee. If you received this in error, please
>> contact the sender and delete the material from any computer.
>>
>

I found the problem: it's a permissions issue.

The autogenerated data folder has the following permissions:

Administrators (MY_COMPUTER_NAME\Administrators)
postgres (MY_COMPUTER_NAME\postgres)

Once I added my Novell user MY_COMPUTER_NAME\my_novell_username with
Full Control I was able to run initdb on it okay.

On Wed, Apr 22, 2009 at 4:36 PM, Robert Campbell <rrc7cz(at)gmail(dot)com> wrote:
> Okay here's where things get strange. I ran initdb and got this error:
>
> --------
> C:\Program Files\PostgreSQL\8.3\bin>initdb -D "C:\Program
> Files\PostgreSQL\8.3\data"
> The files belonging to this data... <text here>
>
> initdb: could not access directory "C:/Program
> Files/PostgreSQL/8.3/data": No such file or directory
> --------
>
> Now the odd part is if I copy the same path I provided and "cd" to it,
> it works. I can paste it into Windows Explorer and it's there. I mean
> clearly I can see it there.
>
> If I pass a different directory, such as C:/PgData38, it runs fine.
>
> Perhaps this is the problem the Setup script encounters?
>
>
> On Wed, Apr 22, 2009 at 4:02 PM, Obe, Regina <robe(dot)dnd(at)cityofboston(dot)gov> wrote:
>> Robert,
>>
>> Sorry I meant to say manually init the database cluster and register the service.  All this do from a dos prompt.
>>
>> So you init the cluster like this
>> "C:\Program Files\PostgreSQL\8.3\bin\initdb" -D "C:\PGData83"
>>
>> And manually register the service like this
>> "C:\Program Files\PostgreSQL\8.3\bin\pg_ctl.exe" register -N "pgsql-8.3" -D "C:\PGData83\" -U postgres -P "NT passwordgoes here"
>>
>> Hope that helps,
>> Regina
>>
>> -----Original Message-----
>> From: Robert Campbell [mailto:rrc7cz(at)gmail(dot)com]
>> Sent: Wednesday, April 22, 2009 9:56 AM
>> To: Obe, Regina
>> Cc: Bruce Momjian; pgsql-novice(at)postgresql(dot)org
>> Subject: Re: [NOVICE] Workaround for bug #4608?
>>
>> Hi Obe,
>>
>> I'm running XP Pro, SP 2. Not running via Remote Desktop, this is
>> local. We don't use Windows Networking, but rather Novell Client (I
>> know, gag).
>>
>> It does create the data folder, but it's completely empty. Also, this
>> happens during the "Loading additional SQL modules..." part of Setup
>> towards the end.
>>
>> Also, to manually create the DB, I need the server running, correct? I
>> can't boot up the server. When I try to bring up the server in
>> pgAdminIII I get a connection error. From the Events log it looks like
>> the server won't start because of the previously mentioned errors.
>> Basically after logging those error, it logs "Is server running?" to
>> which the answer appears to be "no".
>>
>>
>>
>> On Wed, Apr 22, 2009 at 3:40 PM, Obe, Regina <robe(dot)dnd(at)cityofboston(dot)gov> wrote:
>>> Rob,
>>> Forgot to mention the other distinction here is that I was installing via terminal service (but I had it set to console mode).  I have installed via terminal service before on web facing windows 2003 servers that are not part of a domain and had no issues.  So I ruled that out as a culprit.
>>>
>>> Anyrate if you are installing via terminal service,  I think it still holds true that you must connect via console mode.
>>>
>>> Hope that helps,
>>> Regina
>>>
>>> -----Original Message-----
>>> From: Obe, Regina
>>> Sent: Wednesday, April 22, 2009 9:37 AM
>>> To: 'Robert Campbell'; Bruce Momjian
>>> Cc: pgsql-novice(at)postgresql(dot)org
>>> Subject: RE: [NOVICE] Workaround for bug #4608?
>>>
>>> Rob,
>>>
>>> Is this on a Windows 2003 server and is it part of a domain.
>>> I recall having this problem with my windows 2003 servers in this domain and I couldn't install on any of them. (I think the 8.3 of the enterprise db+ ), though it installed fine on the windows xp boxes in the domain using a local postgres account.
>>>
>>> The only thing I noticed is when the data cluster was being created it would remove all the permissions (so wasn't sure if it was becuase I was using a postgres domain account or not)
>>>
>>> Anyrate to skirt around the issue, I manually set the permissions, and ended up manually initing the db and it worked fine.  Though I was kind of pressed for time so didn't really bother investigating the issue.  I suppose I can try again on a another server to recreate the issue if it would help.
>>>
>>> Does it create the data cluster at all?  In my case it would create the data folder but nothing in it.
>>>
>>> Hope that helps,
>>> Regina
>>>
>>> -----Original Message-----
>>> From: pgsql-novice-owner(at)postgresql(dot)org [mailto:pgsql-novice-owner(at)postgresql(dot)org] On Behalf Of Robert Campbell
>>> Sent: Wednesday, April 22, 2009 8:35 AM
>>> To: Bruce Momjian
>>> Cc: pgsql-novice(at)postgresql(dot)org
>>> Subject: Re: [NOVICE] Workaround for bug #4608?
>>>
>>> Hi Bruce,
>>>
>>> Thanks for the reply and for building the installer. Is there anything
>>> I can do to help you pinpoint the problem? Some install logs I can
>>> send or something of that sort?
>>>
>>> Rob
>>>
>>>
>>>
>>> On Wed, Apr 22, 2009 at 2:33 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>>>> Robert Campbell wrote:
>>>>> I'm experiencing bug 4608
>>>>>
>>>>> http://archives.postgresql.org/pgsql-bugs/2009-01/msg00062.php
>>>>>
>>>>> I have tried using the Windows one-click installer for both 8.3.x and
>>>>> 8.4. At the end of the process it says it can't read
>>>>> data/postgres.conf and none of the conf files are generated.
>>>>>
>>>>> I'm pretty surprised that this issue - which prevents me from
>>>>> installing and running PostgreSQL on Windows - was reported in Jan.
>>>>> and the only documentation I could find on it was this 1 bug with no
>>>>> comments. Perhaps the original reporter and I are the only ones
>>>>> experiencing this issue?
>>>>>
>>>>> Anyway, does anyone have any ideas for a workaround?
>>>>
>>>> I think the issue is that we don't know what would cause that.
>>>>
>>>> --
>>>>  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
>>>>  EnterpriseDB                             http://enterprisedb.com
>>>>
>>>>  + If your life is a hard drive, Christ can be your backup. +
>>>>
>>>
>>> --
>>> Sent via pgsql-novice mailing list (pgsql-novice(at)postgresql(dot)org)
>>> To make changes to your subscription:
>>> http://www.postgresql.org/mailpref/pgsql-novice
>>> -----------------------------------------
>>> The substance of this message, including any attachments, may be
>>> confidential, legally privileged and/or exempt from disclosure
>>> pursuant to Massachusetts law. It is intended
>>> solely for the addressee. If you received this in error, please
>>> contact the sender and delete the material from any computer.
>>>
>>
>

Robert Campbell wrote:
> I found the problem: it's a permissions issue.
>
> The autogenerated data folder has the following permissions:
>
> Administrators (MY_COMPUTER_NAME\Administrators)
> postgres (MY_COMPUTER_NAME\postgres)
>
> Once I added my Novell user MY_COMPUTER_NAME\my_novell_username with
> Full Control I was able to run initdb on it okay.

My guess is that a normal install would work fine now too.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

Robert Campbell wrote:

>Okay here's where things get strange. I ran initdb and got this error:
>
>--------
>C:\Program Files\PostgreSQL\8.3\bin>initdb -D "C:\Program
>Files\PostgreSQL\8.3\data"
>The files belonging to this data... <text here>
>
>initdb: could not access directory "C:/Program
>Files/PostgreSQL/8.3/data": No such file or directory

Is this a typo or have you tried to install PostgreSQL twice, because upthread
you wrote:

>"postgres cannot access the server configuration file "E:/Program
>Files/PostgreSQL/8.3/data/postgresql.conf": No such file or directory"
>
>"pg_ctl: PID file "E:/Program
>Files/PostgreSQL/8.3/data/postmaster.pid" does not exist"

Notice that one it's on drive C: and one on drive E:

Rainer

Robert Campbell <rrc7cz(at)gmail(dot)com> writes:
> I found the problem: it's a permissions issue.

Hmm ... I wonder why initdb is saying "No such file or directory" then.
Maybe we are incorrectly translating some Windows error code number?

[ for pgsql-hackers: see thread here:
http://archives.postgresql.org/pgsql-novice/2009-04/msg00079.php

regards, tom lane

I have performed multiple installs and uninstalls on both drives with
different versions (8.3 and 8.4) in an attempt to get the install to
work correctly.

From the very beginning, and throughout the various
installs/versions/locations the error remained the same.

On Wed, Apr 22, 2009 at 5:11 PM, Rainer Bauer <usenet(at)munnin(dot)com> wrote:
> Robert Campbell wrote:
>
>>Okay here's where things get strange. I ran initdb and got this error:
>>
>>--------
>>C:\Program Files\PostgreSQL\8.3\bin>initdb -D "C:\Program
>>Files\PostgreSQL\8.3\data"
>>The files belonging to this data... <text here>
>>
>>initdb: could not access directory "C:/Program
>>Files/PostgreSQL/8.3/data": No such file or directory
>
> Is this a typo or have you tried to install PostgreSQL twice, because upthread
> you wrote:
>
>>"postgres cannot access the server configuration file "E:/Program
>>Files/PostgreSQL/8.3/data/postgresql.conf": No such file or directory"
>>
>>"pg_ctl: PID file "E:/Program
>>Files/PostgreSQL/8.3/data/postmaster.pid" does not exist"
>
> Notice that one it's on drive C: and one on drive E:
>
> Rainer
>
> --
> Sent via pgsql-novice mailing list (pgsql-novice(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-novice
>

Bruce,
I doubt a normal install would work but perhaps might be worth trying.
As I recall the situation at least in my case
I would explicitly add full permission with a bunch of accounts to the
folder and then when I reran the PostgreSQL install, the installer
insisted on removing most of those permissions including the postgres
account.

So its almost like sometimes the installer shoots itself in the foot by
removing its own access to the folder so that it can't even install. But
why this happens only sometimes I have no clue.

Like I said on all the servers here I tested all exhibit the same odd
behavior, but my windows xp box which is also on the same windows 2003
domain network but uses a local postgres account doesn't run into this
issue.

I've installed on lots of standalone windows servers even windows 2008
without any issue.

Thanks,
Regina

-----Original Message-----
From: Bruce Momjian [mailto:bruce(at)momjian(dot)us]
Sent: Wednesday, April 22, 2009 11:05 AM
To: Robert Campbell
Cc: Obe, Regina; pgsql-novice(at)postgresql(dot)org
Subject: Re: [NOVICE] Workaround for bug #4608?

Robert Campbell wrote:
> I found the problem: it's a permissions issue.
>
> The autogenerated data folder has the following permissions:
>
> Administrators (MY_COMPUTER_NAME\Administrators)
> postgres (MY_COMPUTER_NAME\postgres)
>
> Once I added my Novell user MY_COMPUTER_NAME\my_novell_username with
> Full Control I was able to run initdb on it okay.

My guess is that a normal install would work fine now too.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +
-----------------------------------------
The substance of this message, including any attachments, may be
confidential, legally privileged and/or exempt from disclosure
pursuant to Massachusetts law. It is intended
solely for the addressee. If you received this in error, please
contact the sender and delete the material from any computer.

Well, to make thing stranger I installed 8.4 on a different WinXP Pro
SP3 machine outside the Novell network, no McAfee, etc. It installed
absolutely fine. Looking at the data folder permissions, they are
exactly the same as on the first machine: Administrators, postgres.

So why these two exactly similar permissions configurations work
differently on the two machines is anybody's guess. Why did I have to
add my specific user account to the permissions of machine 1 for it to
see the folder? Perhaps Novell tweaks the way Windows handles folder
permissions?

Anyway, I guess for the few people who run into this issue, the
workaround is to add the specific user account that you log in with to
the data folder's permissions, with Full Control, and run initdb
manually as mentioned. It screws up the Start and Stop scripts that
come with the install; instead just follow the command line suggestion
initdb gives after completing.

On Wed, Apr 22, 2009 at 6:07 PM, Obe, Regina <robe(dot)dnd(at)cityofboston(dot)gov> wrote:
> Bruce,
> I doubt a normal install would work but perhaps might be worth trying.
> As I recall the situation at least in my case
> I would explicitly add full permission with a bunch of accounts to the
> folder and then when I reran the PostgreSQL install, the installer
> insisted on removing most of those permissions including the postgres
> account.
>
> So its almost like sometimes the installer shoots itself in the foot by
> removing its own access to the folder so that it can't even install. But
> why this happens only sometimes I have no clue.
>
> Like I said on all the servers here I tested all exhibit the same odd
> behavior, but my windows xp box which is also on the same windows 2003
> domain network but uses a local postgres account doesn't run into this
> issue.
>
> I've installed on lots of standalone windows servers even windows 2008
> without any issue.
>
> Thanks,
> Regina
>
> -----Original Message-----
> From: Bruce Momjian [mailto:bruce(at)momjian(dot)us]
> Sent: Wednesday, April 22, 2009 11:05 AM
> To: Robert Campbell
> Cc: Obe, Regina; pgsql-novice(at)postgresql(dot)org
> Subject: Re: [NOVICE] Workaround for bug #4608?
>
> Robert Campbell wrote:
>> I found the problem: it's a permissions issue.
>>
>> The autogenerated data folder has the following permissions:
>>
>> Administrators (MY_COMPUTER_NAME\Administrators)
>> postgres (MY_COMPUTER_NAME\postgres)
>>
>> Once I added my Novell user MY_COMPUTER_NAME\my_novell_username with
>> Full Control I was able to run initdb on it okay.
>
> My guess is that a normal install would work fine now too.
>
> --
>  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
>  EnterpriseDB                             http://enterprisedb.com
>
>  + If your life is a hard drive, Christ can be your backup. +
> -----------------------------------------
> The substance of this message, including any attachments, may be
> confidential, legally privileged and/or exempt from disclosure
> pursuant to Massachusetts law. It is intended
> solely for the addressee. If you received this in error, please
> contact the sender and delete the material from any computer.
>

On 2009-04-22, Robert Campbell <rrc7cz(at)gmail(dot)com> wrote:
> Hi Obe,
>
> I'm running XP Pro, SP 2. Not running via Remote Desktop, this is
> local. We don't use Windows Networking, but rather Novell Client (I
> know, gag).
>
> It does create the data folder, but it's completely empty. Also, this
> happens during the "Loading additional SQL modules..." part of Setup
> towards the end.
>
> Also, to manually create the DB, I need the server running, correct? I
> can't boot up the server. When I try to bring up the server in
> pgAdminIII I get a connection error. From the Events log it looks like
> the server won't start because of the previously mentioned errors.
> Basically after logging those error, it logs "Is server running?" to
> which the answer appears to be "no".

Is E: drive is physically attached to the server you are installing
postgres on, and is the postgres directory not part of any share?

Hi Jasen,

Yes, the computer has 1 physical drive with two partitions: C and E.
It is not part of any share; it is created by the Setup application
and immediately after fails to write to data.

On Thu, Apr 23, 2009 at 12:38 PM, Jasen Betts <jasen(at)xnet(dot)co(dot)nz> wrote:
> On 2009-04-22, Robert Campbell <rrc7cz(at)gmail(dot)com> wrote:
>> Hi Obe,
>>
>> I'm running XP Pro, SP 2. Not running via Remote Desktop, this is
>> local. We don't use Windows Networking, but rather Novell Client (I
>> know, gag).
>>
>> It does create the data folder, but it's completely empty. Also, this
>> happens during the "Loading additional SQL modules..." part of Setup
>> towards the end.
>>
>> Also, to manually create the DB, I need the server running, correct? I
>> can't boot up the server. When I try to bring up the server in
>> pgAdminIII I get a connection error. From the Events log it looks like
>> the server won't start because of the previously mentioned errors.
>> Basically after logging those error, it logs "Is server running?" to
>> which the answer appears to be "no".
>
> Is E: drive is physically attached to the server you are installing
> postgres on, and is the postgres directory not part of any share?
>
>
> --
> Sent via pgsql-novice mailing list (pgsql-novice(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-novice
>

Em Qua, 2009-04-22 às 09:28 -0400, Bruce Momjian escreveu:
> I am moving this email over to the bugs list. Folks, here is a history
> of the bug report; it seems he can't install in /data on Windows:
> http://archives.postgresql.org//pgsql-novice/2009-04/msg00079.php

In this email [1] he said:

"If I pass a different directory, such as C:/PgData38, it runs fine."

Isn't that caused by spaces in the path, like in
"C:\Program Files\PostgreSQL\8.3\data"

May be the some parts of install script aren't quoting the path?

[1] http://archives.postgresql.org//pgsql-novice/2009-04/msg00090.php

Att.
Dickson S. Guedes
mail/xmpp: guedes(at)guedesoft(dot)net - skype: guediz
http://guedesoft.net - http://planeta.postgresql.org.br