Custom Query (294 matches)
Results (37 - 39 of 294)
|#51||PHP v5.2.3 coredumps if using xcache r272 on pfSense HEAD||moo||DanielSHaischt|
At pfSense we are currently trying to integrate Xcache together with PHP 5.2.0. Unfortunatly XCache behaves quite unstable and causes lots of core dumps.
Disabling XCache, solves these issues.
I was able to track it down to the fact, that the following page allways results in a HTTP 500 if beeing saved and if using Xcache:
If trying to save the above page using EAccelerator I do not get a HTTP 500.
I even tried to use XCache v1.1.0 but the issue remains.
Enabled/Used? modules (in that order):
# add additional extensions below
# standard PHP extension
|#52||fixed||Problem with adodb when use pdo_mysql driver||moo||safari|
<? require_once(dirname(__FILE__).'/adodb/adodb-exceptions.inc.php'); require_once(dirname(__FILE__).'/adodb/adodb.inc.php'); echo "<BR>before"; $conn =& NewADOConnection("pdo_mysql://user:pwd@localhost/dbname?persist"); var_dump($conn); ?>
When not use xCache, will see "before" and the dump of $conn value.
I guess that xCache has problem when compiling/caching file adodb-pdo.inc.php or adodb-pdo_mysql.inc.php. When the error happened, the file adodb-pdo.inc.php was compiled/cached, but adodb-pdo_mysql.inc.php was not.
This bug also happened with eaccelerator, wonder why? (use the same code/idea???); but worked fine with APC.
|#53||worksforme||500 error with Wordpress||moo||johnleach|
Hi, I'm seeing a 500 error returned in Wordpress. It is fixed with either a restart of the php fastcgi processes, or clearing the xcache cache from the xcache admin page.
It is not with all Wordpress pages, so far I've seen it when posting a comment. Posting comments works fine for a few hours/days then consistently returns a 500 error.
This is with php5-cgi 5.1.2-1ubuntu3.4 package on Ubuntu Dapper running as a fastcgi process under lighttpd. It's with xcache 1.1.0 compiled from source (and observed from at least xcache trunk svn r262).
I get no error output from php (to the error_log or php stderr) when accessing the broken page (though I know php error logging to be working).
I think the php script causing the problem is wp-comments-post.php but I've got a couple of comment related plugins installed, such as Akismet and a threaded comments plugin.
I've got other Wordpress installations on the same box which *reportedly* had the same problem (but at different times), though I've not seen it myself.
I'm getting no coredump on the error.
root@mule:~# gcc -v Using built-in specs. Target: i486-linux-gnu Configured with: ../src/configure -v --enable-languages=c,c++,java,f95,objc,ada,treelang --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --program-suffix=-4.0 --enable-__cxa_atexit --enable-clocale=gnu --enable-libstdcxx-debug --enable-java-awt=gtk-default --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.4.2-gcj-4.0-188.8.131.52/jre --enable-mpfr --disable-werror --with-tune=pentium4 --enable-checking=release i486-linux-gnu Thread model: posix gcc version 4.0.3 (Ubuntu 4.0.3-1ubuntu5) root@mule:~# php-cgi -v PHP 5.1.2 (cgi-fcgi) (built: Nov 2 2006 12:24:48) Copyright (c) 1997-2006 The PHP Group Zend Engine v2.1.0, Copyright (c) 1998-2006 Zend Technologies with XCache v1.1.0, Copyright (c) 2005-2006, by mOo