I’m trying to setup wordpress w/ PDO, with php5 and lighttpd. Trouble is, I get nothing

It seems the server executes the request, but the browser receives an empty reply. I see no error in the server log files, no crash, nothing.
The only message I’ve been able to receive for now is the plugin complaining about an unsupported PDO driver – when I alter the “DB_TYPE” parameter on purpose to trigger an error: at least some of the files are parsed and executed. As soon as I revert back to the proper configuration (DB_TYPE = “sqlite”), I only receive blank pages
php_info() reports no issue, PDO driver is properly loaded.

I also tried to run the CLI version of PHP5 to get more info, with no luck. When I use ‘strace’ to see the system call, everything looks normal, but the execution stops without any obvious error:
{{{
lstat64(“/var”, {st_mode=S_IFDIR|0755, st_size=336, …}) = 0
lstat64(“/var/www”, {st_mode=S_IFDIR|0755, st_size=152, …}) = 0
lstat64(“/var/www/wordpress”, {st_mode=S_IFDIR|0775, st_size=944, …}) = 0
lstat64(“/var/www/wordpress/wp-content”, {st_mode=S_IFDIR|0775, st_size=232, …}) = 0
lstat64(“/var/www/wordpress/wp-content/pdo”, {st_mode=S_IFDIR|0775, st_size=136, …}) = 0
lstat64(“/var/www/wordpress/wp-content/pdo/PDOEngine.php”, {st_mode=S_IFREG|0664, st_size=16641, …}) = 0
gettimeofday({1237646717, 948278}, NULL) = 0
open(“/var/www/wordpress/wp-content/pdo/PDOEngine.php”, O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0664, st_size=16641, …}) = 0
read(3, “$m){\n\t\t\t$output “…, 8192) = 8192
read(3, “truct($value,$node->$key); \n “…, 8192) = 257
read(3, “”…, 8192) = 0
read(3, “”…, 8192) = 0
close(3) = 0
gettimeofday({1237646717, 999405}, NULL) = 0
lstat64(“/var”, {st_mode=S_IFDIR|0755, st_size=336, …}) = 0
lstat64(“/var/www”, {st_mode=S_IFDIR|0755, st_size=152, …}) = 0
lstat64(“/var/www/wordpress”, {st_mode=S_IFDIR|0775, st_size=944, …}) = 0
lstat64(“/var/www/wordpress/wp-includes”, {st_mode=S_IFDIR|0775, st_size=2400, …}) = 0
lstat64(“/var/www/wordpress/wp-includes/wp-db.php”, {st_mode=S_IFREG|0664, st_size=25032, …}) = 0
gettimeofday({1237646718, 16978}, NULL) = 0
open(“/var/www/wordpress/wp-includes/wp-db.php”, O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0664, st_size=25032, …}) = 0
read(3, “<?php\n/**\n * WordPress DB Class\n “…, 8192) = 8192
read(3, “db) {\n\t\tif (!@mysql_select_db($db”…, 8192) = 8192
read(3, “\t\tforeach ( (array) array_keys($d”…, 8192) = 8192
brk(0x74f000) = 0x74f000
read(3, “tring false on failure, version n”…, 8192) = 456
read(3, “”…, 8192) = 0
read(3, “”…, 8192) = 0
close(3) = 0
close(2) = 0
close(1) = 0
munmap(0×40020000, 4096) = 0
close(0) = 0
munmap(0x4001f000, 4096) = 0
brk(0x6cb000) = 0x6cb000
munmap(0x40abe000, 528384) = 0
open(“/dev/urandom”, O_RDONLY) = 0
read(0, “\31\303cq”…, 4) = 4
close(0) = 0
open(“/dev/urandom”, O_RDONLY) = 0
read(0, “\210\337\22m”…, 4) = 4
close(0) = 0
open(“/dev/urandom”, O_RDONLY) = 0
read(0, “1\22~v”…, 4) = 4
close(0) = 0
setitimer(ITIMER_PROF, {it_interval={0, 0}, it_value={0, 0}}, NULL) = 0
munmap(0x40a3c000, 93572) = 0
munmap(0x40a53000, 364456) = 0
munmap(0x409b0000, 50136) = 0
munmap(0x409cc000, 457360) = 0
munmap(0×40993000, 117656) = 0
brk(0×645000) = 0×645000
exit_group(255) = ?
}}}

I’m out of idea to solve this issue. Any hints?

Hi Michael
the error is not so much a plugin error but sqlite/pdo telling you that the query is incorrect. in this case it is telling you that wp_options does not exist, which is indicative that something has gone wrong in the installation.
can you post your wp-config here please? or if you would rather do so offline, mail me at the address provided in http://rathercurious.net/about

Error occurred at line 335 in Function prepareQuery.
Error message was: Problem preparing the PDO SQL Statement. Error was Array ( [0] => HY000 [1] => 1 [2] => no such table: wp_options )

(There’s more, but I wasn’t sure how much detail you needed.) I’m running PHP v. 5.2.3 with Apache 2.2.4 on Ubuntu 7.10, with pdo_sqlite v. 1.10.2.6 and version 3.2.8 of the SQLite library. I think it’s awesome that you developed this, and I appreciate any help you can offer.

-Michael

Thanks! That did the trick. Once that was done, though, I had to go in and tweak my Apache settings, since the Apache processes suddenly ballooned up to 13-16 MB each and ate up all of my VPS’ memory. Reducing the number of Apache processes did the trick, though.

– Bryce