>Von: Adrian
Klaver <adrian.klaver@xxxxxxxxxxx>
>An: Thomas.Deboben.ext@xxxxxxxxxxxxxxxxx,
pgsql-general@xxxxxxxxxxxxxx
>Datum: 19.12.2016
19:05
>Betreff: Re:
Windows installation - could not connect to server: Connection
refused (0x0000274D/10061)
>
>On 12/16/2016 07:01 AM, Thomas.Deboben.ext@xxxxxxxxxxxxxxxxx
wrote:
>>>Von:
Adrian Klaver <adrian.klaver@xxxxxxxxxxx>
>>>An:
Thomas.Deboben.ext@xxxxxxxxxxxxxxxxx,
>> pgsql-general@xxxxxxxxxxxxxx
>>>Datum:
09.12.2016 22:21
>>>Betreff:
Re: Windows installation - could not connect
>> to server: Connection refused
(0x0000274D/10061)
>>>
>
>>>> This has worked for
different version, but now we get sometimes trouble
>>>
>>>Which version did it work
on?
>> I'm working with PostgreSQL
9.5.0.1.
>> We download the Win x86-32
and Win x86-64 installation packages from
>> http://www.enterprisedb.com/products-services-training/pgdownload#windows
>
>That is what you are using now but
what where you using when, from first
>post:
>
>"This has worked for different
version, but now we get sometimes trouble
>..."
>
I ment different versions fo our product.
But I had also installer including PostgreSQL
9.3.4.1, 9.3.6.1 and 9.4.4.3.
>>>> So far I wasn't able
to reproduce this error by my self, but I know from
>>>> about 5 issues inside
the last month.
>>>> As I'm not able to
reproduce I would appreciate any help from you to
>>>> find out what causes
this error.
>>>
>>>The error is pretty straight
forward the server cannot be found at
>>>localhost on port 5432,
so:
>> Yes we use the standard port
5432
>>
>>>1) Do you know that the
server is actually up and running at the point
>>>you run the scripts?
>> Atually I havn't really checked
when the installer will start the service.
>> And as I said, I'm not able
to get this error reproduced.
>
>Seems it would be helpful to put
something in the script to check the
>server status and log it before
trying to connect to it.
How can I check the server status?
Is this simply if the postgres service
is running, or if some sql command can connect the postgres port?
>>>
>>>2) Is the server listening
on port 5432?
>> Yes.
>>>
>>>3) Is Windows properly mapping
localhost?
>> Yes.
>>
>> When I got remote access to
these machines after some time
>> the service was running and
I could lauch the sql script from pgAdmin
>> without any problem.
>
>To me indicates this is an order
of execution issue. The script is
>running the connect/create scripts
before the server is up and available
>for connections.
>
But the first failing call is inside
the original PostgreSQL installer package,
where I have no influence on.
So already here is the problem.
This is from bitrock_installer.log
...
[14:58:49] Installing the adminpack
module in the postgres database...
Executing C:\Program Files\PostgreSQL\9.5\bin\psql.exe
-c "CREATE EXTENSION adminpack" -d postgres
Script exit code: 2
...
But the lines above seems to be fine
...
Starting the database server...
Executing cscript //NoLogo "C:\Program
Files\PostgreSQL\9.5\installer\server\startserver.vbs" postgres
Script exit code: 0
Script output:
Starting postgres
Service postgres started successfully
startserver.vbs ran to completion
...
>>
>>>
>>>> All installations do
run on Windows 7 Pro x64.
>>>>
>>>> Best regards,
>>>> Thomas
Deboben
>>>
>>>
>>>--
>>>Adrian Klaver
>>>adrian.klaver@xxxxxxxxxxx
>>
>> Many thanks,
>> Thomas
>--
>Adrian Klaver
>adrian.klaver@xxxxxxxxxxx
Thanks,
Thomas
