Resolved NOTICE: [pool plesk] child 14939 exited with code 0 after 31.033533 seconds from start

[Linulex]

Server operating system version

CentOS Linux 7.9.2009 (Core)

Plesk version and microupdate number

Plesk Obsidian 18.0.50

After the update to plesk 18.0.50 last evening i have these notices in /var/log/sw-cp-server/sw-engine.log

all fpm settings in /opt/plesk/php/X.X/etc/php-fpm.conf are set to log_level = warning, but i think this is in the seperate plesk admin webserver beecause it says "pool plesk" and not a domainname.
Does anyone know where that fpm config is? or what this messages could mean?

[02-Feb-2023 09:57:18] NOTICE: [pool plesk] child 14942 started
[02-Feb-2023 09:57:47] NOTICE: [pool plesk] child 14939 exited with code 0 after 31.033533 seconds from start
[02-Feb-2023 09:57:47] NOTICE: [pool plesk] child 15010 started
[02-Feb-2023 09:57:48] NOTICE: [pool plesk] child 14940 exited with code 0 after 31.032154 seconds from start
[02-Feb-2023 09:57:48] NOTICE: [pool plesk] child 15012 started
[02-Feb-2023 09:57:49] NOTICE: [pool plesk] child 14942 exited with code 0 after 31.032191 seconds from start
[02-Feb-2023 09:57:49] NOTICE: [pool plesk] child 15014 started
[02-Feb-2023 09:58:18] NOTICE: [pool plesk] child 15010 exited with code 0 after 31.032603 seconds from start
[02-Feb-2023 09:58:18] NOTICE: [pool plesk] child 15095 started
[02-Feb-2023 09:58:19] NOTICE: [pool plesk] child 15012 exited with code 0 after 31.033900 seconds from start
[02-Feb-2023 09:58:19] NOTICE: [pool plesk] child 15097 started
[02-Feb-2023 09:58:20] NOTICE: [pool plesk] child 15014 exited with code 0 after 31.034688 seconds from start
[02-Feb-2023 09:58:20] NOTICE: [pool plesk] child 15099 started
[02-Feb-2023 09:58:50] NOTICE: [pool plesk] child 15095 exited with code 0 after 31.027284 seconds from start
[02-Feb-2023 09:58:50] NOTICE: [pool plesk] child 15156 started
[02-Feb-2023 09:58:51] NOTICE: [pool plesk] child 15097 exited with code 0 after 31.027248 seconds from start
[02-Feb-2023 09:58:51] NOTICE: [pool plesk] child 15160 started
[02-Feb-2023 09:58:52] NOTICE: [pool plesk] child 15099 exited with code 0 after 31.027568 seconds from start
[02-Feb-2023 09:58:52] NOTICE: [pool plesk] child 15162 started
[02-Feb-2023 09:59:21] NOTICE: [pool plesk] child 15156 exited with code 0 after 31.030392 seconds from start
[02-Feb-2023 09:59:21] NOTICE: [pool plesk] child 15291 started
[02-Feb-2023 09:59:22] NOTICE: [pool plesk] child 15160 exited with code 0 after 31.030494 seconds from start
[02-Feb-2023 09:59:22] NOTICE: [pool plesk] child 15293 started
[02-Feb-2023 09:59:23] NOTICE: [pool plesk] child 15162 exited with code 0 after 31.029617 seconds from start
[02-Feb-2023 09:59:23] NOTICE: [pool plesk] child 15295 started
[02-Feb-2023 09:59:52] NOTICE: [pool plesk] child 15291 exited with code 0 after 31.031145 seconds from start
[02-Feb-2023 09:59:52] NOTICE: [pool plesk] child 15384 started
[02-Feb-2023 09:59:53] NOTICE: [pool plesk] child 15293 exited with code 0 after 31.031136 seconds from start
[02-Feb-2023 09:59:53] NOTICE: [pool plesk] child 15386 started
[02-Feb-2023 09:59:54] NOTICE: [pool plesk] child 15295 exited with code 0 after 31.031986 seconds from start
[02-Feb-2023 09:59:54] NOTICE: [pool plesk] child 15394 started

thanks in advance
Jan

 

[scsa20]

Should be in /etc/sw-engine/sw-engine-fpm.conf (you could do a systemctl status on sw-engine.service and it should point you where the config file is, but on my CentOS 7 deployment, it shows in /etc/sw-engine/sw-engine-fpm.conf)

 

[scsa20]

Also in terms of what that messages is, it's just a noticed that a child process exited, which is normal since PHP will start a new child process and kills it after awhile, so it could be ignored (and why it's called a NOTICE instead of a warning or something).

 

[Linulex]

Should be in /etc/sw-engine/sw-engine-fpm.conf (you could do a systemctl status on sw-engine.service and it should point you where the config file is, but on my CentOS 7 deployment, it shows in /etc/sw-engine/sw-engine-fpm.conf)

Thank you and found it. Added log_level = warning and now its gone. But strange it surfaced after the update. I shall cincult the backups to see if it was changed
On reflection, i should have known that, silly me.

I know it can be ignored, but a few plesk version before there where some errors that poluted the log so hard that it growed to extreme propartions. So hard that it took almost all server space in a few days. So now i monitor the size of the plesk log and have it send a mail if it goes over 2 MB (2097152 bytes) so i can correct the error before all server space is eaten by the log.

regards
Jan