Re: BUG #9721: Fatal error on startup: no free slots in PMChildFlags array

On 25.03.2014 17:02, Tom Lane wrote:
> Daniel Hahler <postgresql(at)thequod(dot)de> writes:
>> On 25.03.2014 15:36, Alvaro Herrera wrote:
>>> Tom Lane wrote:
>>>> postgresql(at)thequod(dot)de writes:
>>>>> PostgreSQL just failed to startup after a reboot (which was forced via
>>>>> remote Ctrl-Alt-Delete on the PostgreSQL's containers host):
>
>>>> ... in short, I want to see the rest of the log not just this part.
>
>> That was the whole log.
>
> Oh. So actually, "failed to startup" was a complete misdescription, and
> what you should've said was "it appeared to be running normally, but I
> saw this burst of weird messages in the postmaster log, so I decided to
> restart it"?

Sorry, "failed to startup" was a misdescription, because I did not remember that OpenVZ suspends containers on reboots.
I should have said "crashed half an hour after being resumed".

I have not restarted PostgreSQL though, but started it when noticing that it wasn't running (anymore).

From the logs (again):
2014-03-24 13:32:47 CET LOG: could not receive data from client: Connection reset by peer
2014-03-25 12:32:17 CET FATAL: no free slots in PMChildFlags array
2014-03-25 12:32:17 CET LOG: process 9975 releasing ProcSignal slot 108, but it contains 0
2014-03-25 12:32:17 CET LOG: process 9974 releasing ProcSignal slot 109, but it contains 0
2014-03-25 12:32:17 CET LOG: process 9976 releasing ProcSignal slot 110, but it contains 0

I have noticed it, and started it:

2014-03-25 12:38:43 CET LOG: database system was interrupted; last known up at 2014-03-24 18:22:38 CET

If you expect more information from the logs (in case this happens again), I would appreciate some hint about what would be important to enable in the configuration.

Regards,
Daniel.

--
http://daniel.hahler.de/