Actions
Bug #862
closedfcgi + php + memcache problems
Status:
Invalid
Priority:
Normal
Category:
mod_fastcgi
Target version:
-
ASK QUESTIONS IN Forums:
Description
Trying to use memcache with php via mod_fcgi renders the following with debug set to 1:
titan:~# /etc/init.d/lighttpd restart Restarting lighttpd: lighttpd. titan:~# 2006-09-24 18:41:03: (mod_fastcgi.c.1323) --- fastcgi spawning local proc: /usr/bin/php4-cgi port: 0 socket /tmp/php-fastcgi.socket min-procs: 1 max-procs: 1 2006-09-24 18:41:03: (mod_fastcgi.c.1348) --- fastcgi spawning port: 0 socket /tmp/php-fastcgi.socket current: 0 / 1 2006-09-24 18:41:03: (mod_fastcgi.c.1048) the fastcgi-backend /usr/bin/php4-cgi failed to start: 2006-09-24 18:41:03: (mod_fastcgi.c.1063) terminated by signal: 11 2006-09-24 18:41:03: (mod_fastcgi.c.1068) to be exact: it seg-fault, crashed, died, ... you get the idea. 2006-09-24 18:41:03: (mod_fastcgi.c.1070) If this is PHP try to remove the byte-code caches for now and try again. 2006-09-24 18:41:03: (mod_fastcgi.c.1356) [ERROR]: spawning fcgi failed. 2006-09-24 18:41:03: (server.c.834) Configuration of plugins failed. Going down.
Testing /usr/bin/php4-cgi from the command line generates no error.
Versions:
debian sarge
lighttpd 1.4.11
php 4.3.10
memcache 2.0.4
memcache installed using:
pear install memcache
Ideas?
-- andreas
Updated by Anonymous over 18 years ago
As usual the solution comes right after writing the bug report... pear doesn't install the files with the correct permissions. It is possibly a side effect of my 007 umask.
Keep up the good work!
-- andreas
Updated by stbuehler over 16 years ago
- Status changed from New to Fixed
- Resolution set to invalid
Actions
Also available in: Atom