[pgpool-general: 7563] Resource temporarily unavailable

Rozmus Andrzej Andrzej.Rozmus at asseco.pl
Mon May 10 22:55:29 JST 2021


Hello Tatsuo,
We have encountered such a problem today:
FATAL:  failed to fork a child
DETAIL:  system call fork() failed with reason: Resource temporarily unavailable
It seems to be strange because all necessary resources (CPU, RAM) should be available, number of allowed proccesses that can be created by postgres user (pgpool is registered in systemd and works with postgres account) is definitely enough to cover 2048 processes (1024 processe of pgpool and 1024 processes of postgresql). Pgpool hanged with only two subprocesses started:

Main PID: 9584 (pgpool)
    Tasks: 3 (limit: 1024)
   CGroup: /system.slice/pgpool-II-11.service
           ├─ 9584 /usr/pgpool-11/bin/pgpool -f /etc/pgpool-II-11/pgpool.conf -n -D
           ├─10596 pgpool: health check process(0)
           └─10597 pgpool: health check process(1)
Do you have any suggestions what could cause this problem? We have changed „TasksMax” option from default 512 to 1024 for postgresql and pgpool services but as i wrote before – number of processes that can be created by postgres user is far above 2048. I have also checked typical number of running processes in our system (about 500) to exclude problem with insufficient value of kernel.pid_max (32768) parameter.
Best regards and thank you in advance for help.

Andrzej Rozmus
Starszy Technolog
Departament Systemów Administracji Rządowej
Dział Ministerstwo Finansów
Zespół Projektowy AIS/AES
Asseco Poland S.A.
ul. Branickiego 13
02-972 Warszawa
tel. kom. +48 502 270 059
andrzej.rozmus at asseco.pl

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pgpool.net/pipermail/pgpool-general/attachments/20210510/a6af5368/attachment.htm>


More information about the pgpool-general mailing list