Обсуждение: Unable to connect
OS: Windows 2000 Professional SP2 LAN Card: Wireless DLink DWL-650+ postmaster start but any attemp to connect generates the following message: LOG: incomplete startup packet LOG: select() failed in statistics buffer: Se intent¾ realizar una operaci¾n en un elemento que no es un socket. From time to time I got also this message: LOG: statistics collector process (PID XXXX) was terminated by signal 1 LOG: select() failed in statistics buffer: Se intent¾ realizar una operaci¾n en un elemento que no es un socket. Regards.
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
Hi! First of all, I'd strongly suggest you move to a supported servicepack level (supported by MS that is - pg hasn't pickeda level yet). There are a *lot* of important fixes there. Second - are you running any firewall software, or other stuff that might do something at the network layer? If so, try disablingit. //Magnus >-----Original Message----- >From: Sergio Samayoa [mailto:sergiosamayoa@icon.com.gt] >Sent: den 21 maj 2004 00:50 >To: pgsql-hackers-win32@postgresql.org >Subject: [pgsql-hackers-win32] Unable to connect > > >OS: Windows 2000 Professional SP2 >LAN Card: Wireless DLink DWL-650+ > >postmaster start but any attemp to connect generates the >following message: > >LOG: incomplete startup packet >LOG: select() failed in statistics buffer: Se intent¾ realizar una >operaci¾n en > un elemento que no es un socket. > >From time to time I got also this message: > >LOG: statistics collector process (PID XXXX) was terminated >by signal 1 >LOG: select() failed in statistics buffer: Se intent¾ realizar una >operaci¾n en > un elemento que no es un socket. > >Regards. > > >---------------------------(end of >broadcast)--------------------------- >TIP 7: don't forget to increase your free space map settings >
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 specificsetting that breaks it? //Magnus > -----Original Message----- > From: Sergio Samayoa [mailto:sergiosamayoa@icon.com.gt] > Sent: Friday, May 21, 2004 6:30 PM > To: pgsql-hackers-win32@postgresql.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 > >
Hi Magnus. I uninstall the %!@#&! proxy client (you known what i mean with %!@#&!...). I got postgres running !!! I never suspect that proxy client was the source of the problem since I have disabled almost all the time because I use it only on our main offices. Thank you for your patience and support. May be this can be added to FAQ. Tell me if you think that worth the effort and I can write it. Regars, > -----Mensaje original----- > De: Magnus Hagander [mailto:mha@sollentuna.net] > Enviado el: Lunes, 24 de Mayo de 2004 02:43 a.m. > Para: sergiosamayoa@icon.com.gt; pgsql-hackers-win32@postgresql.org > Asunto: RE: [pgsql-hackers-win32] Unable to connect > > > 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
FOLLOW UP: I install again ISA Proxy Client (because I come to HQ and need Internet access) and no problem with PostgreSQL. Regards. > -----Mensaje original----- > De: Sergio Samayoa [mailto:sergiosamayoa@icon.com.gt] > Enviado el: Lunes, 24 de Mayo de 2004 11:50 a.m. > Para: Magnus Hagander; pgsql-hackers-win32@postgresql.org > Asunto: RE: [pgsql-hackers-win32] Unable to connect > Importancia: Alta > > > Hi Magnus. > I uninstall the %!@#&! proxy client (you known what i mean with > %!@#&!...). > I got postgres running !!! > I never suspect that proxy client was the source of the problem > since I have disabled almost all the time because I use it only > on our main offices. > Thank you for your patience and support. > May be this can be added to FAQ. > Tell me if you think that worth the effort and I can write it. > > Regars, > > > -----Mensaje original----- > > De: Magnus Hagander [mailto:mha@sollentuna.net] > > Enviado el: Lunes, 24 de Mayo de 2004 02:43 a.m. > > Para: sergiosamayoa@icon.com.gt; pgsql-hackers-win32@postgresql.org > > Asunto: RE: [pgsql-hackers-win32] Unable to connect > > > > > > 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 >
PostgreSQL and ISA Proxy client: Socket operation on non-socket. (was: Unable to connect)
От
"Sergio Samayoa"
Дата:
ups! I disable the ISA Proxy Client and the problem back! The conclusion: There is no problem using PostgreSQL with ISA Proxy Client as far as isnt disabled. Socket error (WSAENOTSOCK, #10038, "Socket operation on non-socket.") occurs with ISA Proxy Client disabled. Instead of disabling ISA Proxy Client better uninstall it. Regards. > -----Mensaje original----- > De: Sergio Samayoa [mailto:sergiosamayoa@icon.com.gt] > Enviado el: Miércoles, 26 de Mayo de 2004 06:46 p.m. > Para: Magnus Hagander; pgsql-hackers-win32@postgresql.org > Asunto: RE: [pgsql-hackers-win32] Unable to connect > > > FOLLOW UP: > I install again ISA Proxy Client (because I come to HQ and need > Internet access) and no problem with PostgreSQL. > > Regards.