From 869ba3f52b86fbf1fef31e8947cd7e46ad0ab954 Mon Sep 17 00:00:00 2001 From: Ivan Golman Date: Thu, 7 Nov 2024 20:03:37 +0100 Subject: [PATCH] chore: lint markdown php_fpm_pool.md --- documentation/php_fpm_pool.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/documentation/php_fpm_pool.md b/documentation/php_fpm_pool.md index 463c8705..e5fbda6f 100644 --- a/documentation/php_fpm_pool.md +++ b/documentation/php_fpm_pool.md @@ -28,7 +28,6 @@ More info: | `additional_config` | `Hash` | `{}` | Additional parameters in JSON | | `fpm_ini_control` | `[true, false]` | `false` | Whether to add a new `php.ini` file for FPM | - ## Examples 1. Install a FPM pool named 'default' @@ -44,7 +43,7 @@ More info: If more than `5` FPM pools are affected by a configuration change, this will lead to subsequent `5+` service restarts. However, `systemd` will deny this number of subsequent service restarts with the following error: - ``` + ```bash php8.1-fpm.service: Start request repeated too quickly. php8.1-fpm.service: Failed with result 'start-limit-hit'. Failed to start The PHP 8.1 FastCGI Process Manager. @@ -52,7 +51,7 @@ More info: This behavior is due to the `unified_mode true` setting of an `fpm_pool` custom resource, which is a [default setting](https://docs.chef.io/deprecations_unified_mode/) for `chef-clients v18+`. In this mode, notifications set as `:delayed` within a custom resource action (like `action :install`) are queued to be processed once the action completes (i.e., at the end of the resource `action :install` block), rather than waiting until the end of the Chef client run. - ### Possible Workaround + **Possible Workaround** In a wrapper cookbook, define a `ruby_block` with a call to the `sleep(X)` function, which will be called upon an `fpm_pool` resource update: