starmonkey
June 19th, 2006, 10:20 PM
Hey fellahs,
I'm currently running lighttpd (from synaptic) + php5, which I compiled from source as fast-cgi. MySQL was installed via synaptic also. For mysql support in php, I need the mysql headers, but I kinda fudged it and compiled against mysql-standard-5.0.22-linux-i686-glibc23 source that I downloaded from mysql's site.
./configure --prefix=/usr/lib/php5 --enable-fastcgi --enable-force-cgi-redirect \
--with-mysql=/home/blah/files/mysql-standard-5.0.22-linux-i686-glibc23 \
--with-mysql-sock=/var/run/mysqld/mysqld.sock \
--with-pdo-mysql=/home/blah/files/mysql-standard-5.0.22-linux-i686-glibc23 \
--with-zlib --with-gd --with-pear \
--with-curl
This seems to work fine for phpMyAdmin (tested this morning against MySQL - 5.0.22-Debian_0ubuntu6.06-log) but bombs out on a web-application that I'm running. Lighttpd's error log reports the following:
2006-06-20 12:11:59: (mod_fastcgi.c.2430) unexpected end-of-file (perhaps the fastcgi process died): pid: 4536 socket: unix:/tmp/php5-fastcgi.socket-3
2006-06-20 12:11:59: (mod_fastcgi.c.3215) response not received, request sent: 913 on socket: unix:/tmp/php5-fastcgi.socket-3 for /path/to/webapp/index.php , closing connection
The php error log shows nothing.
I read lighttpd's fastcgi troubleshooting docco (http://www.lighttpd.net/documentation/fastcgi.html#troubleshooting) but it didn't really enlighten me. I'm getting lighttpd to spawn the php children internally.
I deduce that my dodgy method of compiling mysql support into php5 is to blame - but in turn I blame synaptic for not having a mysql-dev or mysql-server-dev package that will give me the header files!!!!!
So - am I blind? What's the best way to handle this kind of thing? I don't want to use apache/php from syn - I want to use lighttpd.
cheers,
sm
I'm currently running lighttpd (from synaptic) + php5, which I compiled from source as fast-cgi. MySQL was installed via synaptic also. For mysql support in php, I need the mysql headers, but I kinda fudged it and compiled against mysql-standard-5.0.22-linux-i686-glibc23 source that I downloaded from mysql's site.
./configure --prefix=/usr/lib/php5 --enable-fastcgi --enable-force-cgi-redirect \
--with-mysql=/home/blah/files/mysql-standard-5.0.22-linux-i686-glibc23 \
--with-mysql-sock=/var/run/mysqld/mysqld.sock \
--with-pdo-mysql=/home/blah/files/mysql-standard-5.0.22-linux-i686-glibc23 \
--with-zlib --with-gd --with-pear \
--with-curl
This seems to work fine for phpMyAdmin (tested this morning against MySQL - 5.0.22-Debian_0ubuntu6.06-log) but bombs out on a web-application that I'm running. Lighttpd's error log reports the following:
2006-06-20 12:11:59: (mod_fastcgi.c.2430) unexpected end-of-file (perhaps the fastcgi process died): pid: 4536 socket: unix:/tmp/php5-fastcgi.socket-3
2006-06-20 12:11:59: (mod_fastcgi.c.3215) response not received, request sent: 913 on socket: unix:/tmp/php5-fastcgi.socket-3 for /path/to/webapp/index.php , closing connection
The php error log shows nothing.
I read lighttpd's fastcgi troubleshooting docco (http://www.lighttpd.net/documentation/fastcgi.html#troubleshooting) but it didn't really enlighten me. I'm getting lighttpd to spawn the php children internally.
I deduce that my dodgy method of compiling mysql support into php5 is to blame - but in turn I blame synaptic for not having a mysql-dev or mysql-server-dev package that will give me the header files!!!!!
So - am I blind? What's the best way to handle this kind of thing? I don't want to use apache/php from syn - I want to use lighttpd.
cheers,
sm