[pgpool-general: 6257] Re: forked new pcp worker followed by exit - all day long

[Bo Peng]

Hi,

These messages are normal.

When a PCP command is issued to the Pgpool-II, a new PCP child process 
is forked to handle the command and these log messages just shows 
the fork and exit status of these PCP child process.

Please see this FAQ:
https://www.pgpool.net/mediawiki/index.php/FAQ#Why_am_I_getting_.22LOG:_forked_new_pcp_worker_...2C.22_and_.22LOG:_PCP_process_with_pid:_xxxx_exit_with_SUCCESS..22_messages_in_pgpool_log.3F

Could you check if the application issues PCP command to pgpool?

On Thu, 25 Oct 2018 14:07:42 -0500
Alexander Dorogensky <amazinglifetime at gmail.com> wrote:

> I'm using pgpool-II 3.6.10, postgres 9.6 and
> 4 app nodes (with pgpool, each node connected to the other 3)
> and 2 primary/standby db nodes in streaming replication.
> 
> Below is the output from pgpool.log on one of the nodes.. It doesn't look
> normal to me.. is it?
> 
> 
> 2018-10-23 23:41:34: pid 14075: LOG:  forked new pcp worker, pid=9431
> socket=7
> 2018-10-23 23:41:34: pid 14075: LOG:  PCP process with pid: 9431 exit with
> SUCCESS.
> 2018-10-23 23:41:34: pid 14075: LOG:  PCP process with pid: 9431 exits with
> status 0
> 2018-10-23 23:41:34: pid 14075: LOG:  forked new pcp worker, pid=9433
> socket=7
> 2018-10-23 23:41:34: pid 14075: LOG:  PCP process with pid: 9433 exit with
> SUCCESS.
> 2018-10-23 23:41:34: pid 14075: LOG:  PCP process with pid: 9433 exits with
> status 0
> 2018-10-23 23:41:39: pid 14075: LOG:  forked new pcp worker, pid=9456
> socket=7
> 2018-10-23 23:41:39: pid 14075: LOG:  PCP process with pid: 9456 exit with
> SUCCESS.
> 2018-10-23 23:41:39: pid 14075: LOG:  PCP process with pid: 9456 exits with
> status 0
> 2018-10-23 23:41:39: pid 14075: LOG:  forked new pcp worker, pid=9458
> socket=7
> 2018-10-23 23:41:39: pid 14075: LOG:  PCP process with pid: 9458 exit with
> SUCCESS.
> 2018-10-23 23:41:39: pid 14075: LOG:  PCP process with pid: 9458 exits with
> status 0
> 2018-10-23 23:41:39: pid 14075: LOG:  forked new pcp worker, pid=9460
> socket=7
> 2018-10-23 23:41:39: pid 14075: LOG:  PCP process with pid: 9460 exit with
> SUCCESS.
> 2018-10-23 23:41:39: pid 14075: LOG:  PCP process with pid: 9460 exits with
> status 0
> 2018-10-23 23:41:45: pid 14075: LOG:  forked new pcp worker, pid=9482
> socket=7
> 2018-10-23 23:41:45: pid 14075: LOG:  PCP process with pid: 9482 exit with
> SUCCESS.
> 2018-10-23 23:41:45: pid 14075: LOG:  PCP process with pid: 9482 exits with
> status 0
> 2018-10-23 23:41:45: pid 14075: LOG:  forked new pcp worker, pid=9484
> socket=7
> 2018-10-23 23:41:45: pid 14075: LOG:  PCP process with pid: 9484 exit with
> SUCCESS.
> 2018-10-23 23:41:45: pid 14075: LOG:  PCP process with pid: 9484 exits with
> status 0
> 2018-10-23 23:41:45: pid 14075: LOG:  forked new pcp worker, pid=9486
> socket=7
> 2018-10-23 23:41:45: pid 14075: LOG:  PCP process with pid: 9486 exit with
> SUCCESS.
> 2018-10-23 23:41:45: pid 14075: LOG:  PCP process with pid: 9486 exits with
> status 0
> 2018-10-23 23:41:50: pid 14075: LOG:  forked new pcp worker, pid=9492
> socket=7
> 2018-10-23 23:41:50: pid 14075: LOG:  PCP process with pid: 9492 exit with
> SUCCESS.
> 2018-10-23 23:41:50: pid 14075: LOG:  PCP process with pid: 9492 exits with
> status 0
> 2018-10-23 23:41:50: pid 14075: LOG:  forked new pcp worker, pid=9494
> socket=7
> 2018-10-23 23:41:50: pid 14075: LOG:  PCP process with pid: 9494 exit with
> SUCCESS.
> 2018-10-23 23:41:50: pid 14075: LOG:  PCP process with pid: 9494 exits with
> status 0
> 2018-10-23 23:41:50: pid 14075: LOG:  forked new pcp worker, pid=9496
> socket=7
> 2018-10-23 23:41:50: pid 14075: LOG:  PCP process with pid: 9496 exit with
> SUCCESS.
> 2018-10-23 23:41:50: pid 14075: LOG:  PCP process with pid: 9496 exits with
> status 0


-- 
Bo Peng <pengbo at sraoss.co.jp>
SRA OSS, Inc. Japan