Обсуждение: JDBC Connection broken (followup)
Oh, tried this with Windows firewall off, and AV off too. Here's the logging of the last few successful, and then the unsuccessful.... 2009-08-17 00:56:58 PDTLOG: 00000: connection received: host=127.0.0.1 port=3233 2009-08-17 00:56:58 PDTLOCATION: BackendInitialize, .\src\backend\postmaster\postmaster.c:3205 2009-08-17 00:56:58 PDTLOG: 00000: connection authorized: user=mjb database=retain 2009-08-17 00:56:58 PDTLOCATION: BackendInitialize, .\src\backend\postmaster\postmaster.c:3283 2009-08-17 00:56:58 PDTLOG: 00000: disconnection: session time: 0:00:00.016 user=mjb database=retain host=127.0.0.1 port=3233 2009-08-17 00:56:58 PDTLOCATION: log_disconnections, .\src\backend\tcop\postgres.c:4024 2009-08-17 00:56:58 PDTLOG: 00000: connection received: host=127.0.0.1 port=3234 2009-08-17 00:56:58 PDTLOCATION: BackendInitialize, .\src\backend\postmaster\postmaster.c:3205 2009-08-17 00:56:58 PDTLOG: 00000: connection authorized: user=mjb database=retain 2009-08-17 00:56:58 PDTLOCATION: BackendInitialize, .\src\backend\postmaster\postmaster.c:3283 2009-08-17 00:56:58 PDTLOG: 00000: disconnection: session time: 0:00:00.000 user=mjb database=retain host=127.0.0.1 port=3234 2009-08-17 00:56:58 PDTLOCATION: log_disconnections, .\src\backend\tcop\postgres.c:4024 2009-08-17 00:56:58 PDTLOG: 00000: connection received: host=127.0.0.1 port=3235 2009-08-17 00:56:58 PDTLOCATION: BackendInitialize, .\src\backend\postmaster\postmaster.c:3205 2009-08-17 00:56:58 PDTLOG: XX000: could not receive data from client: An operation was attempted on something that is nota socket. 2009-08-17 00:56:58 PDTLOCATION: pq_recvbuf, .\src\backend\libpq\pqcomm.c:769 2009-08-17 00:56:59 PDTLOG: 08P01: incomplete startup packet 2009-08-17 00:56:59 PDTLOCATION: ProcessStartupPacket, .\src\backend\postmaster\postmaster.c:1469
On 17/08/2009 4:00 PM, Michael Bell wrote: > Oh, tried this with Windows firewall off, and AV off too. Here's the logging of the last few successful, and then the unsuccessful.... It might be useful if you could: - in pg_hba.conf, set 127.0.0.1 to "trust" or change the password of the user you'll be testing with to something generic; then - use Wireshark (http://wireshark.org/) to capture traffic on the loopback interface during a failed login attempt that results in the "incomplete startup packet" error. - Change pg_hba.conf back / reset the password you changed - Post the packet trace (libpcap format) or, if it's too big, put it up somewhere people can download it and post a link to it. Doing so may or may not help - but if the results look normal you at least know the client is sending the right startup packet and it's a server side problem. "An operation was attempted on something that is not a socket" makes you wonder if the socket was closed, the backend is getting FDs (handles) mixed up, or something. I was about to suggest trying to get a log with Process Monitor (from Sysinternals) but it doesn't look like Process Monitor records TCP/IP socket activity, so it won't be much use. Sigh. Maybe the wireshark trace will be informative... -- Craig Ringer > 2009-08-17 00:56:58 PDTLOCATION: BackendInitialize, .\src\backend\postmaster\postmaster.c:3205 > 2009-08-17 00:56:58 PDTLOG: XX000: could not receive data from client: An operation was attempted on something that isnot a socket. > 2009-08-17 00:56:58 PDTLOCATION: pq_recvbuf, .\src\backend\libpq\pqcomm.c:769 > 2009-08-17 00:56:59 PDTLOG: 08P01: incomplete startup packet > 2009-08-17 00:56:59 PDTLOCATION: ProcessStartupPacket, .\src\backend\postmaster\postmaster.c:1469 > > > > >
Thanks for replying. I changed the pg_hba.conf to trust (I don't care about the password, this is just a test system, installedfrom scratch). However, unfortunately WinPCap cannot capture loopback traffic, so that doesn't help us much :) Other side notes: tried LSPFix - it found no problems. And I use this box to test MS SQL, MySQL regularly with no issues. ----- Original Message ---- From: Craig Ringer <craig@postnewspapers.com.au> To: pgsql-jdbc@postgresql.org Sent: Monday, August 17, 2009 3:17:52 AM Subject: Re: [JDBC] JDBC Connection broken (followup) On 17/08/2009 4:00 PM, Michael Bell wrote: > Oh, tried this with Windows firewall off, and AV off too. Here's the logging of the last few successful, and then the unsuccessful.... It might be useful if you could: - in pg_hba.conf, set 127.0.0.1 to "trust" or change the password of the user you'll be testing with to something generic; then - use Wireshark (http://wireshark.org/) to capture traffic on the loopback interface during a failed login attempt that results in the "incomplete startup packet" error. - Change pg_hba.conf back / reset the password you changed - Post the packet trace (libpcap format) or, if it's too big, put it up somewhere people can download it and post a link to it. Doing so may or may not help - but if the results look normal you at least know the client is sending the right startup packetand it's a server side problem. "An operation was attempted on something that is not a socket" makes you wonder if the socket was closed, the backend isgetting FDs (handles) mixed up, or something. I was about to suggest trying to get a log with Process Monitor (from Sysinternals)but it doesn't look like Process Monitor records TCP/IP socket activity, so it won't be much use. Sigh. Maybe the wireshark trace will be informative... -- Craig Ringer > 2009-08-17 00:56:58 PDTLOCATION: BackendInitialize, .\src\backend\postmaster\postmaster.c:3205 > 2009-08-17 00:56:58 PDTLOG: XX000: could not receive data from client: An operation was attempted on something that isnot a socket. > 2009-08-17 00:56:58 PDTLOCATION: pq_recvbuf, .\src\backend\libpq\pqcomm.c:769 > 2009-08-17 00:56:59 PDTLOG: 08P01: incomplete startup packet > 2009-08-17 00:56:59 PDTLOCATION: ProcessStartupPacket, .\src\backend\postmaster\postmaster.c:1469 > > > > > -- Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-jdbc