On Wed, 30 Mar 2022 09:30:39 -0500 ITwrx <li...@itwrx.org> wrote: > > Hi ITwrx > > > > you will need to check your rc.conf.local and update it to start up > > the php8.0 fpm > > > > it is possible (im not saying it is recommended) but it is possible > > to run different versions of php fpm (with different socket files) > > for different applications on the same server ... > > but it sounds like you just need to remove the php7.4 fpm line in > > your rc.conf.local and replace it with a line that would startup > > your php8 fpm > > > > I hope this helps, > > > > > > > > On Mon, 28 Mar 2022 at 20:10, ITwrx <li...@itwrx.org> wrote: > > > > > I'm running php7.4 and php8 at the same time on an OpenBSD 7.0 > > > machine i'm testing as a web server. I'm pretty sure they were > > > both starting up fine until yesterday (it's been a while) after i > > > updated with pkg_add -u and syspatch. Now, php8 fails to start > > > with: > > > > > > ERROR: Another FPM instance seems to already listen on > > > /var/www/run/php-fpm.sock > > > ERROR: FPM initialization failed > > > > > > This seems to be due to the fact that php8.0 became the new > > > default, but it looks like php74 is still trying to use > > > php-fpm.sock instead of php-fpm74.sock, or whatever it's supposed > > > to be called once it's not the default anymore. > > > > > > Am i missing something, or is this a bug? If the latter, is this > > > email sufficient to get it looked at, or i would need to report it > > > more formally? > > > > > > Thanks, > > > ITwrx > > > > > > > > > > This was accidentally sent to Tom Smyth directly, previously. Sorry > about that. I'm new to Claws mail and using it just for mailing lists, > and didn't think to check how it was handling replies. > > Thanks for your reply. > > If i get rid of php74_fpm it will just start php8 as default and only > php version, which is not what i want. It seems to me that the socket > file used to respect the php version by creating php-fpm74.sock, > php-fpm80.sock, etc, and not just create "php-fpm.sock", causing > a collision. Or maybe the non-default php sockets use the version > number but not the default version's socket? Maybe when php80 became > the default, php74 was supposed to be modified to create > php74-fpm.sock since it's not the default anymore, but that was > overlooked due to the assumption that people should just use one or > the other? Am i imagining that, or this new behavior is a bug? What > is responsible for designating what the socket is named? is it > configurable, or hardcoded in the package/port source? > > I already had/have the /etc/php-7.4/php-fpm.conf and > /etc/php-8.0/php-fpm.conf files configured with > "www/run/php74-fpm.sock" and "www/run/php80-fpm.sock" respectively and > i believe that was working prior to the update, so they already know > what socket to listen on, but the socket files themselves are not > being created properly now. > > thanks, > ITwrx
it seems both php versions only expect to use /etc/php-fpm.conf and therefore i can't specify different folders by version for the socket. Is there no way to name separate php-fpm.conf files per version so that this will work? Seems like a missed opportunity for OpenBSD and users when 3 versions are already packaged.
