ALERT: oops, unknown child (103) exited with code 0.

[lfluvisotto]

Description

[20-Oct-2022 15:31:40] NOTICE: [pool www] 'user' directive is ignored when FPM is not running as root
[20-Oct-2022 15:31:40] NOTICE: [pool www] 'user' directive is ignored when FPM is not running as root
[20-Oct-2022 15:31:40] NOTICE: [pool www] 'group' directive is ignored when FPM is not running as root
[20-Oct-2022 15:31:40] NOTICE: [pool www] 'group' directive is ignored when FPM is not running as root
[20-Oct-2022 15:31:40] NOTICE: fpm is running, pid 1
[20-Oct-2022 15:31:40] NOTICE: ready to handle connections
[20-Oct-2022 15:31:40] NOTICE: systemd monitor interval set to 10000ms
[20-Oct-2022 16:50:02] ALERT: oops, unknown child (103) exited with code 0. Please open a bug report (https://github.com/php/php-src/issues).

PHP Version

8.1.8

Operating System

Ubuntu 22.04

[iluuu1994]

@lfluvisotto This version is a couple months old (07 Jul 2022). Could you try with the newest 8.1 version? Is there any additional information you can provide? This is not nearly enough to identify the problem.

[bukka]

Could you also then provide your FPM config and some context when this happens - the only thing that I see that it's after start when you start FPM as not a root user but might need a bit more info how you start FPM. Please try to also set log_level to debug so more info is visible.

[bukka]

Possibly the same issue as #9792

[github-actions]

No feedback was provided. The issue is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so. Thank you.

[bukka]

I have created an issue #10315 and PR #10319 that fixes it. This happened most likely due to some orphan process that got FPM master as a new parent because the master is an init process (PID 1) - that's how it runs in Docker and it is also visible in the logs:

[20-Oct-2022 15:31:40] NOTICE: fpm is running, pid 1

The fix replaces the ALERT with DEBUG message for this case because it is really not a problem or something that can be changed. Please update this issue if you think that your issue is different.