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

Re: Workaround for bug #4608?

From: Robert Campbell <rrc7cz(at)gmail(dot)com>
To: "Obe, Regina" <robe(dot)dnd(at)cityofboston(dot)gov>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-novice(at)postgresql(dot)org
Subject: Re: Workaround for bug #4608?
Date: 2009-04-22 13:55:35
Message-ID: b57c4e1c0904220655w2eff15cft3c06450f8cc0633d@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackerspgsql-novice
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.
>

In response to

Responses

pgsql-novice by date

Next:From: Obe, ReginaDate: 2009-04-22 14:02:42
Subject: Re: Workaround for bug #4608?
Previous:From: Obe, ReginaDate: 2009-04-22 13:40:25
Subject: Re: Workaround for bug #4608?

pgsql-hackers by date

Next:From: Obe, ReginaDate: 2009-04-22 14:02:42
Subject: Re: Workaround for bug #4608?
Previous:From: Obe, ReginaDate: 2009-04-22 13:40:25
Subject: Re: Workaround for bug #4608?

pgsql-bugs by date

Next:From: Obe, ReginaDate: 2009-04-22 14:02:42
Subject: Re: Workaround for bug #4608?
Previous:From: Obe, ReginaDate: 2009-04-22 13:40:25
Subject: Re: Workaround for bug #4608?

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