Skip to content

Commit

Permalink
chore: lint markdown php_fpm_pool.md
Browse files Browse the repository at this point in the history
  • Loading branch information
Ivan Golman committed Nov 7, 2024
1 parent a8d2685 commit 869ba3f
Showing 1 changed file with 2 additions and 3 deletions.
5 changes: 2 additions & 3 deletions documentation/php_fpm_pool.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,6 @@ More info: <https://www.php.net/manual/en/install.fpm.php>
| `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'
Expand All @@ -44,15 +43,15 @@ More info: <https://www.php.net/manual/en/install.fpm.php>
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.
```

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:

Expand Down

0 comments on commit 869ba3f

Please sign in to comment.