Thomas Hallgren wrote:
With great help from Magnus, who advised me to use lspfix from cexx.org
to list my lsp's, I found that I had gapsp.dll, Neoteris DNS Provider
installed. An uninstall of the Neoteris software made this problem go away.
I guess the question is, why is a DNS Provider
With great help from Magnus, who advised me to use lspfix from
cexx.org to list my lsp's, I found that I had gapsp.dll,
Neoteris DNS Provider
installed. An uninstall of the Neoteris software made this
problem go away.
I guess the question is, why is a DNS Provider software
blocking
Magnus Hagander [EMAIL PROTECTED] writes:
To reiterate the basic point: The broken LSP breaks a fundamental
promise in the sockets API that we absolutely require. The bug is
completely within the LSP.
ISTM that maybe what we have here is a documentation shortcoming.
I'm thinking that our
To reiterate the basic point: The broken LSP breaks a fundamental
promise in the sockets API that we absolutely require. The bug is
completely within the LSP.
ISTM that maybe what we have here is a documentation shortcoming.
I'm thinking that our Windows FAQ ought to suggest
Martijn van Oosterhout wrote:
On Thu, Sep 29, 2005 at 08:50:30AM +0200, Thomas Hallgren wrote:
Hi,
I've installed PostgreSQL 8.1-beta2 as a service on my Windows-XP box.
It runs fine but I get repeated messages like this in the log:
2005-09-29 00:41:09 FATAL: could not duplicate socket
I added some traces to the code. I know that the following happens when
I start a postmaster.
StartupDatabase will call internal_fork_exec, it calls
write_inheritable_socket 4 times and succeeds.
During the first iteration of ServerLoop:
StartBackgroundWriter will call internal_fork_exec
On Sun, Oct 02, 2005 at 12:20:05PM +0200, Thomas Hallgren wrote:
I added some traces to the code. I know that the following happens when
I start a postmaster.
snip
In the second iteration of ServerLoop, pgstat_forkexec will again call
will call internal_fork_exec. This time it fails.
IIRC, the win32 installer will enable autovacuum by default.
And yes,
autovacuum was my first thought as well after Thomas last
mail - that
would be a good explanation to why it happens when the postmaster is
idle.
I used the win32 installer defaults so autovacuum is
probably
Magnus Hagander wrote:
Right. Please try turning it off and see if the problem goes away.
It does (go away).
- thomas
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
Magnus Hagander wrote:
Right. Please try turning it off and see if the problem goes away.
No, wait! It does *not* go away. Do I need to do anything more than
setting this in my postgresql.conf file:
autovacuum = false# enable autovacuum subprocess?
and restart the service?
Right. Please try turning it off and see if the problem goes away.
No, wait! It does *not* go away. Do I need to do anything
more than setting this in my postgresql.conf file:
autovacuum = false# enable autovacuum subprocess?
and restart the service?
The two zombie
On Fri, Sep 30, 2005 at 08:29:07AM +0200, Thomas Hallgren wrote:
Magnus Hagander wrote:
Right. Please try turning it off and see if the problem goes away.
No, wait! It does *not* go away. Do I need to do anything more than
setting this in my postgresql.conf file:
autovacuum = false
Alvaro Herrera [EMAIL PROTECTED] writes:
If it's two zombies per minute, then I bet it's the stat collector and
stat bufferer. They are restarted by the postmaster if not found to be
running.
That would make some sense, because the stat processes need to set up new
sockets (for the pipe
If it's two zombies per minute, then I bet it's the stat
collector and
stat bufferer. They are restarted by the postmaster if not
found to
be running.
That would make some sense, because the stat processes need
to set up new sockets (for the pipe between them). The
autovacuum
Tom Lane wrote:
However, why two zombies? That would mean that the grandchild process
started, which should mean that the pipe was already created ...
To clarify, I talk about the tcpview window and connections, and thus
zombi-connections. They both belong to the same pid and seems to
Hi,
I've installed PostgreSQL 8.1-beta2 as a service on my Windows-XP box.
It runs fine but I get repeated messages like this in the log:
2005-09-29 00:41:09 FATAL: could not duplicate socket 1880 for use
in backend: error code 10038
and for each message printed, a new postgres process
Hi,
I've installed PostgreSQL 8.1-beta2 as a service on my
Windows-XP box.
It runs fine but I get repeated messages like this in the log:
2005-09-29 00:41:09 FATAL: could not duplicate socket
1880 for use in backend: error code 10038
and for each message printed, a new postgres
Nope, no anti-virus and no firewall (other then the box that fronts my
home-network to the outside world).
- thomas
Magnus Hagander wrote:
Hi,
I've installed PostgreSQL 8.1-beta2 as a service on my
Windows-XP box.
It runs fine but I get repeated messages like this in the log:
On Thu, Sep 29, 2005 at 08:50:30AM +0200, Thomas Hallgren wrote:
Hi,
I've installed PostgreSQL 8.1-beta2 as a service on my Windows-XP box.
It runs fine but I get repeated messages like this in the log:
2005-09-29 00:41:09 FATAL: could not duplicate socket 1880 for use
in backend:
Message-
From: Thomas Hallgren [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 29, 2005 9:48 AM
To: Magnus Hagander
Cc: PostgreSQL-development
Subject: Re: [HACKERS] Socket problem using beta2 on Windows-XP
Nope, no anti-virus and no firewall (other then the box that
fronts my home
Hallgren [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 29, 2005 9:48 AM
To: Magnus Hagander
Cc: PostgreSQL-development
Subject: Re: [HACKERS] Socket problem using beta2 on Windows-XP
Nope, no anti-virus and no firewall (other then the box that
fronts my home-network to the outside world
On Thu, Sep 29, 2005 at 11:43:37PM +0200, Thomas Hallgren wrote:
2. It happens while the postmaster is idle. If I leave it idle for a
while and then come back, I'll have a whole bunch of new processes in my
task-manager and zombies in tcpview.
Hmm ... how many processes? Did you enable
2. It happens while the postmaster is idle. If I leave it
idle for a
while and then come back, I'll have a whole bunch of new
processes in
my task-manager and zombies in tcpview.
Hmm ... how many processes? Did you enable autovacuum
perchance? If so, does the number of processes
Magnus Hagander wrote:
IIRC, the win32 installer will enable autovacuum by default. And yes,
autovacuum was my first thought as well after Thomas last mail - that
would be a good explanation to why it happens when the postmaster is
idle.
I used the win32 installer defaults so autovacuum is
24 matches
Mail list logo
