Change Details

``` $ /usr/local/etc/rc.d/php-fpm start Performing sanity check on php-fpm configuration: [17-Feb-2018 14:46:07] NOTICE: configuration file /usr/local/etc/php-fpm.conf test is successful Starting php_fpm. $ /usr/home/dereckson # /usr/local/etc/rc.d/php-fpm status php_fpm is not running. ```

On a FreeBSD server, this can happens after a PHP package: ``` $ /usr/local/etc/rc.d/php-fpm start Performing sanity check on php-fpm configuration: [17-Feb-2018 14:46:07] NOTICE: configuration file /usr/local/etc/php-fpm.conf test is successful Starting php_fpm. $ /usr/local/etc/rc.d/php-fpm status php_fpm is not running. ``` We edit the RC service to use different paths than the default one. We should document the `roles/webserver-legacy/php-sites/php-fpm` should be run again afterwards. Alternatively, we can also deploy to another service name or reach the package maintainer with our multi-instance solution.

On a FreeBSD server, this can happens after a PHP package: ``` $ /usr/local/etc/rc.d/php-fpm start Performing sanity check on php-fpm configuration: [17-Feb-2018 14:46:07] NOTICE: configuration file /usr/local/etc/php-fpm.conf test is successful Starting php_fpm. $ /usr/home/dereckson # /usr/local/etc/rc.d/php-fpm status php_fpm is not running. ``` We edit the RC service to use different paths than the default one. We should document the `roles/webserver-legacy/php-sites/php-fpm` should be run again afterwards. Alternatively, we can also deploy to another service name or reach the package maintainer with our multi-instance solution.