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

Re: Unable to connect

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: <sergiosamayoa(at)icon(dot)com(dot)gt>, <pgsql-hackers-win32(at)postgresql(dot)org>
Subject: Re: Unable to connect
Date: 2004-05-24 08:42:34
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCE171699@algol.sollentuna.se (view raw or flat)
Thread:
Lists: pgsql-hackers-win32
This looks very weird. I've tried on several different OSes, and not seen anything like it.

Could you please look at the steps in this KB article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;817571

I have seen similar things with the MS Proxy client before, could be it's not just "third party". 

Do you have any non-standard config settings set in postgresql.conf? If so, can you try without them to see if it's a specific setting that breaks it?

//Magnus

> -----Original Message-----
> From: Sergio Samayoa [mailto:sergiosamayoa(at)icon(dot)com(dot)gt] 
> Sent: Friday, May 21, 2004 6:30 PM
> To: pgsql-hackers-win32(at)postgresql(dot)org
> Subject: Re: [pgsql-hackers-win32] Unable to connect
> 
> I just downloaded latest sanpshot (21.05.2004) but still cant connect.
> I already stop antivirus software, proxy client and FireBird server
> 
> psql message:
> 
> psql: could not receive server response to SSL negotiation packet:
> Connection re
> set by peer (0x00002746/10054)
> 
> Server log:
> 
>  DEBUG:  00000: forked new backend, pid=1240 socket=732
>  LOCATION:  BackendStartup, postmaster.c:2324
>  DEBUG:  00000: Attaching to 015B0000
>  LOCATION:  PGSharedMemoryCreate, pg_shmem.c:262
>  LOG:  00000: connection received: host=127.0.0.1 port=1389
>  LOCATION:  BackendInit, postmaster.c:2481
> 127.0.0.1(1389) LOG:  XX000: could not receive data from 
> client: Se intentĀ¾ real izar una operaciĀ¾n en un elemento que 
> no es un socket.
> 
> 127.0.0.1(1389) LOCATION:  pq_recvbuf, pqcomm.c:678
> 127.0.0.1(1389) LOG:  08P01: incomplete startup packet
> 127.0.0.1(1389) LOCATION:  ProcessStartupPacket, postmaster.c:1246
> 127.0.0.1(1389) DEBUG:  00000: proc_exit(0)
> 127.0.0.1(1389) LOCATION:  proc_exit, ipc.c:95
> 127.0.0.1(1389) DEBUG:  00000: shmem_exit(0)
> 127.0.0.1(1389) LOCATION:  shmem_exit, ipc.c:126
> 127.0.0.1(1389) DEBUG:  00000: exit(0)
> 127.0.0.1(1389) LOCATION:  proc_exit, ipc.c:113
>  DEBUG:  00000: reaping dead processes
>  LOCATION:  reaper, postmaster.c:1885
>  DEBUG:  00000: waiting on 2 children
>  LOCATION:  win32_waitpid, postmaster.c:3596
>  DEBUG:  00000: child process (PID 1240) exited with exit code 0
>  LOCATION:  LogChildExit, postmaster.c:2169
>  DEBUG:  00000: waiting on 1 children
>  LOCATION:  win32_waitpid, postmaster.c:3596
> 
> 
> ---------------------------(end of 
> broadcast)---------------------------
> TIP 6: Have you searched our list archives?
> 
>                http://archives.postgresql.org
> 
> 

Responses

pgsql-hackers-win32 by date

Next:From: Thomas KellererDate: 2004-05-24 10:26:53
Subject: tcpip_socket parameter in postgresql.conf
Previous:From: Bruce MomjianDate: 2004-05-24 02:09:10
Subject: Re: nightly win32 builds

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