php-fpm signal spamming system messages

[TobiG]

Good morning fellow BSD-lovers,

as the title suggests, I get a lot of system messages (dmesg) from php-fpm:

[392979] pid 66165 (php-fpm), jid 0, uid 80: exited on signal 3 (no core dump - bad address)
[393336] pid 67534 (php-fpm), jid 0, uid 80: exited on signal 3 (no core dump - bad address)
[393860] pid 68994 (php-fpm), jid 0, uid 80: exited on signal 3 (no core dump - bad address)
[393861] pid 68995 (php-fpm), jid 0, uid 80: exited on signal 3 (no core dump - bad address)

In my opinion, it is partly because of my php-fpm pool setup, where child processes are spawned when requests are received:

pm = ondemand
pm.max_children = 20
pm.max_requests = 0

After the workload is finished, the child processes are signaled to gracefully stop:

php-fpm()

SIGQUIT             graceful stop

But when it comes to FreeBSDs signal(), SIGQUIT should create a core image.

Num   Name             Default Action       Description
3     SIGQUIT          create core image    quit program

So my questions are: Is there a problem with my setup? Are there just differences between the signals used by php-fpm (Linux?) and BSD? Can I safely ignore them / mute them?

Iam running 14.0-RELEASE, but the issue was also present in 13.2-RELEASE.

Version        : 8.2.12
Installed on   : Thu Nov 23 18:00:43 2023 CET
Origin         : lang/php82
Architecture   : FreeBSD:14:amd64
Prefix         : /usr/local
Categories     : www lang devel
Licenses       : PHP301
Maintainer     : bofh@FreeBSD.org
WWW            : https://www.php.net/
Comment        : PHP Scripting Language (8.2.X branch)
Options        :
        CGI            : on
        CLI            : on
        DEBUG          : off
        DTRACE         : on
        EMBED          : on
        FPM            : on
        IPV6           : on
        LINKTHR        : on
        MYSQLND        : on
        PHPDBG         : off
        ZTS            : off

Thanks for any insights on this matter!

 

[suntzu00]

is ASLR enabled by any chance? can you disable it for php-fpm and see if you can reproduce it?

elfctl -e +noaslr /usr/local/sbin/php-fpm (stop the service -> disable ASRL -> start the service)

 

[yuripv79]

After the workload is finished, the child processes are signaled to gracefully stop

Shouldn't php-fpm handle the SIGQUIT in that case? The "create core image" default action should apply only if the program does not handle the signal. And what exactly sends SIGQUIT to php-fpm processes?