Missing socket for FastCGI in Lighttpd

[Gustavo Narea]

If I enable FastCGI in Lighttpd, Lighty crashes because FastCGI's configuration refers to a missing socket file: /tmp/php.socket

In the errors log file, people will find something like:
=====
2008-05-30 12:40:58: (log.c.75) server started
2008-05-30 12:40:58: (mod_fastcgi.c.1029) the fastcgi-backend /usr/bin/php-cgi failed to start:
2008-05-30 12:40:58: (mod_fastcgi.c.1033) child exited with status 9 /usr/bin/php-cgi
2008-05-30 12:40:58: (mod_fastcgi.c.1036) If you're trying to run PHP as a FastCGI backend, make sure you're using the FastCGI-enabled version.
You can find out if it is the right one by executing 'php -v' and it should display '(cgi-fcgi)' in the output, NOT '(cgi)' NOR '(cli)'.
For more information, check http://trac.lighttpd.net/trac/wiki/Docs%3AModFastCGI#preparing-php-as-a-fastcgi-programIf this is PHP on Gentoo, add '$
2008-05-30 12:40:58: (mod_fastcgi.c.1340) [ERROR]: spawning fcgi failed.
2008-05-30 12:40:58: (server.c.908) Configuration of plugins failed. Going down.
=====

The work-around is:
sudo touch /tmp/php.socket
sudo chown www-data /tmp/php.socket

(Using Hardy)

[Stefan Bühler (stbuehler)]

I seriously doubt this.

lighty first creates the socket, then tries to spawn the backend, so if the socket creation/bind would fail, it wouldn't event fork.

And i can't imagine that your sudo commands fix anything (even if your /tmp permissions would be broken and not allow lighty to create a socket in it).

Use strace on lighty (strace -ff lighttpd -D -f /etc/lighttpd/lighttpd.conf) to see what happens.

otoh, i guess this is way too old to find out what really happened.

[Jeremy Bícha (jbicha)]

I believe this is a duplicate of bug 236027. Please see if installing php5-cgi fixes this.

[Launchpad Janitor (janitor)]

[Expired for lighttpd (Ubuntu) because there has been no activity for 60 days.]