K2GO-386 fix(rootfs): stop php-fpm running idle by default (barrier 1) - #543
Merged
Conversation
An idle php-fpm (enabled unconditionally by the nginx role) is the disk-fill offender: orphaned off proot by a relaunch/restore it busy-loops on epoll_wait ENOSYS (~600 MB/min) and fills /data. Move php-fpm ownership from nginx to the roles that use it, in one carried patch: 0002-php-fpm-role-ownership.patch (tools/upstream-patches): - nginx no longer manages php-fpm (drops both the proot enable/restart block and the non-proot systemd restart); nginx does not need it. - the Matomo role enables its own php-fpm. So on the default build (no php-consuming role) php-fpm stays installed but not enabled -> never runs -> cannot orphan and fill the disk. Carried via tools/upstream-patches (WIP); it only affects our build until presented upstream, where it pairs with every IIAB php role self-managing its php. The app-side free-space guard (barrier 2, the general net) is tracked on K2GO-386.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
An idle php-fpm (enabled unconditionally by the nginx role) is the disk-fill offender: orphaned off proot by a relaunch/restore it busy-loops on epoll_wait ENOSYS (~600 MB/min) and fills /data. Move php-fpm ownership from nginx to the roles that use it, in one carried patch:
0002-php-fpm-role-ownership.patch (tools/upstream-patches):
So on the default build (no php-consuming role) php-fpm stays installed but not enabled -> never runs -> cannot orphan and fill the disk. Carried via tools/upstream-patches (WIP); it only affects our build until presented upstream, where it pairs with every IIAB php role self-managing its php.
The app-side free-space guard (barrier 2, the general net) is tracked on K2GO-386.