www/lighttpd 1.4.45 broken mod_fastcgi for PHP

Radek Krejča radek.krejca at starnet.cz
Wed Mar 1 23:39:47 UTC 2017


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
> https://www.lighttpd.net/2017/1/14/1.4.45/
> 
> Because it seems like Lighttpd is trying to find / kill child,
> complaints that there is not this PID anymore but it is still here and
> PHP is running.

[Radek Krejca] Lighttpd looks really broken in this version, I have problems too:

Feb 28 07:10:35 cutter kernel: pid 568 (lighttpd), uid 80: exited on signal 11
Feb 28 10:03:34 cutter kernel: pid 31145 (lighttpd), uid 80: exited on signal 11
Feb 28 10:23:22 cutter kernel: pid 42116 (lighttpd), uid 80: exited on signal 11
Feb 28 10:55:12 cutter kernel: pid 43447 (lighttpd), uid 80: exited on signal 11
Feb 28 14:43:32 cutter kernel: pid 45541 (lighttpd), uid 80: exited on signal 11

I have made script for clean php processess and start lighttpd again, because of it is very important server for me.

Radek


More information about the freebsd-ports mailing list