Hi,
I use Lighttpd 1.4.45_1 on 11.0-RELEASE with mod_fastcgi and php-cgi. There are
no problems with this setup. Are you sure php-cgi processes are running are the
socket file is present?
On 17-03-01 00:36:46, Miroslav Lachman wrote:
> Hi,
> I upgraded from 1.4.44 to 1.4.45_1 and after service
Piotr Kubaj wrote on 2017/03/01 08:59:
Hi,
I use Lighttpd 1.4.45_1 on 11.0-RELEASE with mod_fastcgi and php-cgi. There are
no problems with this setup. Are you sure php-cgi processes are running are the
socket file is present?
Yes, there ara php-cgi processes. The strange thing is PHP web si
If FPM works fine, it looks to me more like PHP error than Lighttpd's. Could
you use truss(1) on Lighttpd's process to obtain more information?
On 17-03-01 10:56:29, Miroslav Lachman wrote:
> Piotr Kubaj wrote on 2017/03/01 08:59:
> > Hi,
> >
> > I use Lighttpd 1.4.45_1 on 11.0-RELEASE with mod_f
Piotr Kubaj wrote on 2017/03/01 11:13:
If FPM works fine, it looks to me more like PHP error than Lighttpd's. Could
you use truss(1) on Lighttpd's process to obtain more information?
Can it be related to this fix:
[mod_fastcgi] detect child exit, restart proactively
https://www.lighttpd.net/2
Bezüglich Steve Wills's Nachricht vom 01.03.2017 06:57 (localtime):
> Hi All,
>
> Thanks to everyone who tested.
>
> I've updated the patch and packages in the same location and fixed a
> number of issues. Please re-test if you can.
>
> The only remaining issue that I know of is building with libu
Hi,
>
> Piotr Kubaj wrote on 2017/03/01 11:13:
> > If FPM works fine, it looks to me more like PHP error than
> Lighttpd's. Could you use truss(1) on Lighttpd's process to obtain more
> information?
>
> Can it be related to this fix:
>
> [mod_fastcgi] detect child exit, restart proactively
> ht
On Mon, Feb 27, 2017 at 07:33:43AM -0300, Danilo G. Baio (dbaio) wrote:
> On Sat, Feb 25, 2017 at 09:42:38PM +0100, Olivier Duchateau wrote:
> > On Sat, 25 Feb 2017 16:48:17 -0300
> > "Danilo G. Baio (dbaio)" wrote:
> >
> > > On Sat, Feb 25, 2017 at 07:48:05PM +0100, Olivier Duchateau wrote:
> >
Le 27/02/2017 à 11:33, Danilo G. Baio (dbaio) a écrit :
> On Sat, Feb 25, 2017 at 09:42:38PM +0100, Olivier Duchateau wrote:
>> On Sat, 25 Feb 2017 16:48:17 -0300
>> "Danilo G. Baio (dbaio)" wrote:
>>
>>> On Sat, Feb 25, 2017 at 07:48:05PM +0100, Olivier Duchateau wrote:
For py3-* ports, you
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you
