mod_proxy_core not creating sockets

Hi,

I'm using lighttpd-1.4.18 with mod_fastcgi.so for serving
.php documents.
Every now and then I try to use the latests -svn build to do
the same, but 
somehow I fail to do so: lighttpd starts up, but when asked
to serve a 
.php page (just calling phpinfo()), the errorlog shows:

mod_proxy_core.c.2324: (trace) selected backend:
unix:/tmp/php-fastcgi.sock, state: 1
mod_proxy_core.c.1406: (trace) proxy_state_engine: state=0
mod_proxy_core.c.940: (error)
connect(unix:/tmp/php-fastcgi.sock) failed: No such file or
directory (2)
mod_proxy_core.c.1455: (trace) connecting to address
unix:/tmp/php-fastcgi.sock (0x808aca0) failed, disabling for
60 sec
mod_proxy_core.c.2416: (trace) write failed, restarting
request
mod_proxy_core.c.2324: (trace) selected backend:
unix:/tmp/php-fastcgi.sock, state: 1
mod_proxy_core.c.2336: (trace) backlog: all addresses are
down, putting /phpinfo.php (6) into the backlog, retry = 1

And indeed: the sockets that mod_proxy_core should connect
to do NOT 
exist. The lighttpd.conf for lighttpd-1.5 is the *same* as
the one for 1.4
except of course the changes needed for
mod_proxy_backend_fastcgi to work:
http:/
/nerdbynature.de/bits/lighttpd-svn/2026/

When starting lighttpd-1.4, the socket files are created
almost 
instantly, with 1.5, no sockets are created. I tried to take
the configuration 
examples from the website[0] as well as a .conf from #922,
but to no 
avail. I still suspect a configuration issue on my side, but
I dunno where 
to look.

Thanks for ideas,
Christian.

[0] 
http://trac.lighttpd.net/trac/wiki/Docs:ModProxyCore
-- 
BOFH excuse #271:

The kernel license has expired

On 2007-11-26 02:58:01 +0100, Christian Kujau wrote:
> I'm using lighttpd-1.4.18 with mod_fastcgi.so for
serving .php documents.
> Every now and then I try to use the latests -svn build
to do the same, but 
> somehow I fail to do so: lighttpd starts up, but when
asked to serve a 
> .php page (just calling phpinfo()), the errorlog
shows:
> 
> mod_proxy_core.c.2324: (trace) selected backend: 
> unix:/tmp/php-fastcgi.sock, state: 1
> mod_proxy_core.c.1406: (trace) proxy_state_engine:
state=0
> mod_proxy_core.c.940: (error)
connect(unix:/tmp/php-fastcgi.sock) failed: 
> No such file or directory (2)
> mod_proxy_core.c.1455: (trace) connecting to address 
> unix:/tmp/php-fastcgi.sock (0x808aca0) failed,
disabling for 60 sec
> mod_proxy_core.c.2416: (trace) write failed, restarting
request
> mod_proxy_core.c.2324: (trace) selected backend: 
> unix:/tmp/php-fastcgi.sock, state: 1
> mod_proxy_core.c.2336: (trace) backlog: all addresses
are down, putting 
> /phpinfo.php (6) into the backlog, retry = 1
> 
> And indeed: the sockets that mod_proxy_core should
connect to do NOT 
> exist. The lighttpd.conf for lighttpd-1.5 is the *same*
as the one for 1.4
> except of course the changes needed for
mod_proxy_backend_fastcgi to work:
> http:/
/nerdbynature.de/bits/lighttpd-svn/2026/
> 
> When starting lighttpd-1.4, the socket files are
created almost 
> instantly, with 1.5, no sockets are created. I tried to
take the 
> configuration examples from the website[0] as well as a
.conf from #922, 
> but to no avail. I still suspect a configuration issue
on my side, but I 
> dunno where to look.
> 
> Thanks for ideas,
> Christian.

1.5 does not spawn the backends itself. you need to launch
them with
spawn-fcgi

  darix

-- 
           openSUSE - SUSE Linux is my linux
               openSUSE is good for you
                   www.opensuse.org

On Mon, 26 Nov 2007, Marcus Rueckert wrote:
> 1.5 does not spawn the backends itself. you need to
launch them with
> spawn-fcgi

ah, I somehow missed that one in the docs.

Thanks you!
Christian
-- 
BOFH excuse #43:

boss forgot system password