SEO

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 is created. To make
things worse, those processes do not die when I stop the service.

I use sysinternals tcpview to monitor my sockets. I know that no other
process is using 1880. Each started postgres process will occupy two,
seemingly random ports that apparently form a loop somehow. This is a
typical entry:

<non-existent>:3136 TCP 127.0.0.1:1554 127.0.0.1:1555 ESTABLISHED
<non-existent>:3136 TCP 127.0.0.1:1555 127.0.0.1:1554 ESTABLISHED

The weird thing is that there is no process with pid 3136 (hence the
name <non-existent>). There is a postgres process with another pid in my
process listing. If I kill that, the <non-existstent> entries go away.

Looks like pid 3136 is talking to itself. A pipe() followed by failure
to start the new process perhaps?

Regards,
Thomas Hallgren


---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

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: error code 10038

That's from postmaster.c:write_inheritable_socket(). Error 10038 is
WSAENOTSOCK. Very odd, time to get out the debugger? Get a backtrace at
least.

Hope this helps,
--
Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQFDO6GaIB7bNG8LQkwRAksxAJ9aD744uRxsUS4l7SuURx +pH8YNJwCeLyvN
buW5dkjUrM4lwfWcK7Ynnhg=
=i/d3
-----END PGP SIGNATURE-----

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 1880 for use
>>in backend: error code 10038
>>
>>
>
>That's from postmaster.c:write_inheritable_socket(). Error 10038 is
>WSAENOTSOCK. Very odd, time to get out the debugger? Get a backtrace at
>least.
>
>
I finally managed to debug the postmaster and I'm now pretty sure the
message is not from the postmaster itself. I put a breakpoint where the
message is printed (postmaster.c:3762) and in errstart() where elevel >=
ERROR (elog.c:152) but I never get there although the message is
printed. I know that my debugger works because if I put a break on
elog.c:194 it stops for other messages.

Regards,
Thomas Hallgren



---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq