Thread: XP install problems
I'm trying to install 8.0-beta2-dev3 onto a windows XP pro sp1 box, but having problems. During install it gets as far as wanting to connect to instance to activate the procedural language files, but then fails to connect and reports an error 'connection refused <0x0000274D/10061> is the server running on host "127.0.0.1" and accepting TCP/IP connections on port 5432? If I let the rest of the install run it reports another failure to connect and 'server closed the connection unexpectedly...', but then a succesful install Opening up pgadmin shows the database, but any attemot to connect fails with 'could not receive server response to SSL negotiation packet. Connection reset by peer (0x00002746/10054)' The box is networked on my lan, is not running a firewall, and I've tried installing from my usual user (with admin privlages) and from administrator - both with the same results. I've tried installing using the default user, and adding a user explicitly myself. Anti virus software has been disabled. All options taken are the defaults. The postgres service appears to be running, and I can shut it down and restart it fine. Checking running processes shows that postmaster.exe, pc_ctl.exe, and three postgres.exe processes running. The log files, in postgresql/8.0-beta2-dev3/data/pg_log report a great many errors (incomplete startup packet etc) with the common line 'an operation was attempted on something that is not a socket' Perversly, if I try installing it on my server (windows 2000 a/s) then it all goes in fine, but I'd like a local install as I want to try some Delphi development against it. I've tralled through the lists/faqs, but without any success. What should I attempt next? Thanks Kevin Woolley
Kevin Woolley wrote: > > The log files, in postgresql/8.0-beta2-dev3/data/pg_log report a great many > errors (incomplete startup packet etc) with the common line 'an operation > was attempted on something that is not a socket' When I see that error in the Windows XP DHCP client, I can usually fix it by resetting the TCP/IP stack to its initial state using "netsh interface ip reset > rest.log". YMMV, else see the MS Knowledgebase for that error. Jochem
> > The log files, in postgresql/8.0-beta2-dev3/data/pg_log > report a great > > many errors (incomplete startup packet etc) with the common > line 'an > > operation was attempted on something that is not a socket' > > When I see that error in the Windows XP DHCP client, I can > usually fix it by resetting the TCP/IP stack to its initial > state using "netsh interface ip reset > rest.log". YMMV, else > see the MS Knowledgebase for that error. Also see FAQ item 3.2 at http://pginstaller.projects.postgresql.org/FAQ_windows.html. //Magnus
Magnus Hagander wrote: >>>The log files, in postgresql/8.0-beta2-dev3/data/pg_log >> >>report a great >> >>>many errors (incomplete startup packet etc) with the common >> >>line 'an >> >>>operation was attempted on something that is not a socket' >> >>When I see that error in the Windows XP DHCP client, I can >>usually fix it by resetting the TCP/IP stack to its initial >>state using "netsh interface ip reset > rest.log". YMMV, else >>see the MS Knowledgebase for that error. > > > Also see FAQ item 3.2 at > http://pginstaller.projects.postgresql.org/FAQ_windows.html. > Hello! I had this same error last week, and I have been pointed to that FAQ. True that it's mentioned as a problem related to a bug in windows, but, I have just installed other RDBMS (Oracle and FireBirdSQL) on my machine, and they run quite fine. My guess is that there should be a workaround so that the user won't have to experiment with this frustrating bug. Thanks. Arcadius.
OK, I'm not entirerly sure what happened here, but I have it working now. Problem seems to have been related to ISA server and the proxy client I'm using for that. For the record, and for anyone with similar problems, I did the following... 1. Ran netsh interface ip reset reset.log. Rebooted. Put back IP settings (I'm on a small lan and don't use DHCP, ip of machine 169.254.0.13, mask 255.255.255.0, gateway 169.254.0.1). No effect - still got socket error. 2. Downloaded and ran LSPFix.exe. Didn't report any errors, but stack was Wspwsp.dll (winsock proxy client, installed from ISA server, which I run on my internet gateway) Mswsock.dll Winrnr.dll CSLSP.DLL (Macfee AV) Rsvpsp.dll Let it attempt to repair (no errors reported). Rebooted. No - effect - still got socket error 3. Uninstalled Microsoft Proxy Client. Rebooted. No internet connection (of course). Still can't get get to Postgres 4. Reinstalled Proxy Client (from ISA Server). Rebooted. Internet connection back, and (wahoo) can connect to Postgres So, continued to play around. Found following 5. If I disable the Proxy Client, reboot, then get same socket error back when I connect to postgres (internet continues to work because gateway etc. set up) 6. Renable Firewall client, reboot, Postgres connect works again. (oddly it continues to work if you turn the proxy client off but don't reboot) So I conclude that the problem lies in the ISA server proxy client, which I presumably had installed but not enabled (18 months since configured). Reason for that is that if it is enabled then SSL upstream doesn't work as my broadband connection is via satellite and there's this weird mass proxy server at the groundstation in germany that I have to expicitly bypass from my ISA server for ssl because it doesn't handle that - and MS Firewall Proxy Client always routes through ISA even if you tell it not too in lan connection settings. Fortunatly loosing upstream ssl on my development box isn't an issue as anything I really need ssl for is done on my other machines. Ho hum. First time I've ever seen anything break like this - development box has been pretty solid up until now with other services/programs using tcpip. Anyway, thanks for the help guys. Kevin > -----Original Message----- > From: pgsql-hackers-win32-owner@postgresql.org > [mailto:pgsql-hackers-win32-owner@postgresql.org] On Behalf > Of Jochem van Dieten > Sent: 21 September 2004 12:02 > To: Kevin Woolley > Cc: pgsql-hackers-win32@postgresql.org > Subject: Re: [pgsql-hackers-win32] XP install problems > > Kevin Woolley wrote: > > > > The log files, in postgresql/8.0-beta2-dev3/data/pg_log > report a great > > many errors (incomplete startup packet etc) with the common > line 'an > > operation was attempted on something that is not a socket' > > When I see that error in the Windows XP DHCP client, I can > usually fix it by resetting the TCP/IP stack to its initial > state using "netsh interface ip reset > rest.log". YMMV, else > see the MS Knowledgebase for that error. > > Jochem > > ---------------------------(end of > broadcast)--------------------------- > TIP 1: subscribe and unsubscribe commands go to > majordomo@postgresql.org > >