Re: issue with move to php8 as default
rc.conf.local cool! thanks! Just in case it helps someone in the future, i added: php74_fpm_flags=-y /etc/php74-fpm.conf php80_fpm_flags=-y /etc/php80-fpm.conf to rc.conf.local, which each reference listen = /var/www/run/php74/php-fpm.sock and listen = /var/www/run/php80/php-fpm.sock respectively. This works.
Re: issue with move to php8 as default
On 2022-03-30, ITwrx wrote: >> The php-fpm ports default to using /etc/php-fpm.conf. >> >> If you are running both php74_fpm and php80_fpm together then you must >> change this default for at least one of them and point it at its own >> configuration file e.g. >> >> php74_fpm_flags=-y /etc/php-fpm-7.4.conf >> >> Nothing has changed in this respect. > > Thanks. i'm guessing that goes in the port source code/make file. i'll > check it out. rc.conf.local > I think it would be nice if each PHP version defaulted to using it's own > versioned config file since OpenBSD already packages three versions, > unless there's some downside i'm not thinking of. This would make > OpenBSD even more attractive and convenient for php app hosting by > default. Just for maintainer's consideration... > > Thanks for all the responses. I wasn't getting any of them through claws > mail for some reason. Moved this account to tbird now. > > Thanks, > ITwrx > > -- Please keep replies on the mailing list.
Re: issue with move to php8 as default
The php-fpm ports default to using /etc/php-fpm.conf. If you are running both php74_fpm and php80_fpm together then you must change this default for at least one of them and point it at its own configuration file e.g. php74_fpm_flags=-y /etc/php-fpm-7.4.conf Nothing has changed in this respect. Thanks. i'm guessing that goes in the port source code/make file. i'll check it out. I think it would be nice if each PHP version defaulted to using it's own versioned config file since OpenBSD already packages three versions, unless there's some downside i'm not thinking of. This would make OpenBSD even more attractive and convenient for php app hosting by default. Just for maintainer's consideration... Thanks for all the responses. I wasn't getting any of them through claws mail for some reason. Moved this account to tbird now. Thanks, ITwrx
Re: issue with move to php8 as default
You seem to have missed my reply: https://marc.info/?l=openbsd-misc=164855890727816=2 On 2022-03-30, ITwrx wrote: > On Wed, 30 Mar 2022 09:30:39 -0500 > ITwrx 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 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. > > -- Please keep replies on the mailing list.
Re: issue with move to php8 as default
On Wed, 30 Mar 2022 09:30:39 -0500 ITwrx 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 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.
issue with move to php8 as default
> 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 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
Re: issue with move to php8 as default
On 2022-03-28, ITwrx 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. The php-fpm ports default to using /etc/php-fpm.conf. If you are running both php74_fpm and php80_fpm together then you must change this default for at least one of them and point it at its own configuration file e.g. php74_fpm_flags=-y /etc/php-fpm-7.4.conf Nothing has changed in this respect. -- Please keep replies on the mailing list.
Re: issue with move to php8 as default
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 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 > > -- Kindest regards, Tom Smyth.
issue with move to php8 as default
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
