[BlueOnyx:27068] Re: php-fpm failure due to port clash

[Michael Stauber]

Hi Darren,

> I've encountered a problem where php-fpm (in this case 8.1) failed to start after installing an update to it, and php-fpm 8.2 fresh. I traced this back to one of the vsite configs in /etc/php-fpm-8.1.d where it had been assigned port 9100, which clashed with node_explorer.
> 
> I've temporarily renamed the specific vsites fpm config so I could get php-fpm running again (meaning this particular vsite is down, but the rest are up), but presumably this port should never be used for a vsite.
> How do I resolve the port conflict, and prevent this from happening in the future?

Which version of BlueOnyx is this on?

Back on 9th May of this year I fixed this in BlueOnyx 5210R and 5211R:

https://devel.blueonyx.it/trac/changeset/5261/BlueOnyx/5210R/platform/base-apache.mod

https://devel.blueonyx.it/trac/changeset/5260/BlueOnyx/5211R/platform/base-apache.mod

They now have a check to determine if the intended PHP-FPM port is in 
usage and if so, it will check again until it finds a port that is free.

That should actually have taken care of that particular problem.

-- 
With best regards

Michael Stauber