Project

General

Profile

Actions

Bug #2649

closed

spawn-fcgi: socket is already in use, can't spawn

Added by hadmut almost 9 years ago. Updated almost 9 years ago.

Status:
Invalid
Priority:
Normal
Target version:
-

Description

Hi,

I'm trying to run lighttpd (1.4.33) with spawn-fcgi (1.6.3) in order to use with fcgi scripts written in ruby.

configuration like

fastcgi.server += (
".frb" => (
"localhost" => ( "socket" => "/var/run/lighttpd/fastcgi.sock",
"bin-path" => "/usr/bin/spawn-fcgi -U www-data -s /var/run/lighttpd/fastcgi.sock /var/www/fcgi-bin/time.frb"
)
)
)

which does not work, server aborts with

spawn-fcgi: socket is already in use, can't spawn
spawn-fcgi: socket is already in use, can't spawn
spawn-fcgi: socket is already in use, can't spawn

Reason: lighttpd creates the unix domain socket before running the program given in bin-path. spawn-fcgi on the other hand insists on creating the socket by itself and aborts if that does already exist.

Proof: If I remove the bin-path parameter from the config, remove the socket manually, launch spawn-fcgi (before lighttpd in order to allow it to create the socket) and then start lighttpd, things work as expected.

regards

Actions #1

Updated by stbuehler almost 9 years ago

  • Status changed from New to Invalid

In no way did we document anywhere that this is supposed to work. spawn-fcgi is designed to be used to spawn outside lighttpd.

Actions

Also available in: Atom