Could you send me a truss(1) output of the relevant process?
On 17-03-01 11:36:02, Miroslav Lachman wrote:
> 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
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
>
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
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
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
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
