-
Notifications
You must be signed in to change notification settings - Fork 7.8k
oops, unknown child (13560) exited with code 0. Please open a bug report #9513
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Okay, but why is PHP-FPM involved here? Don't you run ECS from the command line? |
@cmb69 Hi Christoph, we do use a Docker PHP-FPM Container for all out environments, where in some this issue appears in the console, and in others ECS aborts due to ECS-based maximum error limits that we cannot reproduce locally for some reasoning. |
I found the issue and its related likely to ECS rather than this repository. I will leave my findings here for anybody else that stumbles upon it. When you use Parallel Feature of ECS, and you have a huge codebase that you run it over, ECS will attempt to spawn children processes. ECS is configured to wait 120 seconds for children processes to finish which is an arbitrary value and not really working when you have a couple of thousand files. So, what happens? ECS aborts these processes after 120 seconds, thus its creating the errors from the console that I have posted above:
The solution for us was to change the ECS declaration in
|
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 where I assume the pipeline was running. 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. Btw the fact that it stopped killing processes meant that it was just not happening for this particular case but there was still a bug in FPM in terms of displaying the alert - it should not really be displayed. |
Hey @bukka , thanks for still checking and figuring something out. MUCH appreciated. 👍 |
Description
We upgraded from ECS ^8.3 to ^10.2 and updated the dependencies just as well (CS Fixer and Slavomat Fixers). Now, if we want to run ECS with our fixers on our grown codebase, we see this in our local env:
We have a grown ECS file with 312 lines, so I'd rather not share it here. Instead, here are the Fixers we
use
:Our pipeline aborts with this error, which is probably more related to ECS itself, but its most likely caused by the errors I've pasted above:
PHP Version
PHP 8.0.24
Operating System
No response
The text was updated successfully, but these errors were encountered: