Logger process and "LOG: could not close client or listen socket: Bad file descriptor" - Mailing list pgsql-hackers

From Michael Paquier
Subject Logger process and "LOG: could not close client or listen socket: Bad file descriptor"
Date
Msg-id ZOvvuQe0rdj2slA9@paquier.xyz
Whole thread Raw
Responses Re: Logger process and "LOG: could not close client or listen socket: Bad file descriptor"
List pgsql-hackers
Hi all,
(Heikki in CC.)

After b0bea38705b2, I have noticed that the syslogger is generating a
lot of dummy LOG entries:
2023-08-28 09:40:52.565 JST [24554]
LOG:  could not close client or listen socket: Bad file descriptor

The only reason why I have noticed this issue is because I enable the
logging collector in my development scripts.  Note that the pg_ctl
test 004_logrotate.pl, the only one with logging_collector set, is
equally able to reproduce the issue.

The root of the problem is ClosePostmasterPorts() in syslogger.c,
where we close the postmaster ports, but all of them are still set at
0, leading to these spurious logs.

From what I can see, this is is a rather old issue, because
ListenSocket[] is filled with PGINVALID_SOCKET *after* starting the
syslogger.  It seems to me that we should just initialize the array
before starting the syslogger, so as we don't get these incorrect
logs?

Thoughts?  Please see the attached.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Peter Smith
Date:
Subject: Re: subscription/015_stream sometimes breaks
Next
From: Michael Paquier
Date:
Subject: Re: pg_stat_get_backend_subxact() and backend IDs?