From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Paul Breen <paulb(at)computerpark(dot)co(dot)uk> |
Cc: | pgsql-interface(at)postgresql(dot)org, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Postmaster crashes with "Serverloop: select failed" message |
Date: | 2001-01-05 17:10:04 |
Message-ID: | 10365.978714604@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Paul Breen <paulb(at)computerpark(dot)co(dot)uk> writes:
> The problem is that the Postmaster has crashed twice now and both times
> the last message in the Postmaster's log was:
> /usr/local/pgsql/bin/postmaster: ServerLoop: select failed: No child
> processes
This sounds like the bug we recently recognized that the SIGCHLD signal
processor has to save and restore errno. There is a fix in current
sources. I do not have a patch for 7.0.* handy, but you could probably
adapt the change that was applied:
The additions to reaper() are the only critical part, I think.
> We also seem to get a large number of the following message in our
> Postmaster's log:
> pq_recvbuf: unexpected EOF on client connection
> Are these connected? What do the messages mean?
No, those just mean that some client is disconnecting without bothering
to send the "I'm done" message. It's pretty harmless from the DB's
point of view. Do you have a client that crashes a lot?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Pilosov | 2001-01-05 18:50:18 | Re: running pgsql 7 under Jail'ed virtual machine on FreeBSD 4.2 |
Previous Message | Dave VanAuken | 2001-01-05 14:11:13 | RE: running pgsql 7 under Jail'ed virtual machine on FreeBSD 4.2 |