• We have a server that we lease from Rackspace, a linux box running Red Hat Enterprise Linux 3. Yesterday we tried to get some e-commerce software going and we realized our build of PHP didn’t have mhash installed. So we called Rackspace and asked them to rebuild our copy of PHP, this time including mhash. Rackspace did so. And then all of our WordPress died.

    If you go here, you’ll see that our WordPress blog is dead:

    http://www.monkeyclaus.org/

    All you’ll see is what I’m echoing to the screen.

    It turns out WordPress is now dying on this line:

    $this->col_info[$i] = mysql_fetch_field($this->result);

    That line is in wp-db.php (which is in the wp-includes folder).

    Other sites on our server, including PHP/MySql sites, are having no problem:

    http://www.accumulist.com/

    So why would WordPress die on this one line? I’m not getting any PHP errors, though in the Apache error log there is a notice that talks about a segmentation fault. I’ve no idea what that means.

    We’re currently running version 4.3.2 of PHP.

    The configure command for the new build of PHP was this:

    ‘./configure’ ‘–host=i686-redhat-linux-gnu’ ‘–build=i686-redhat-linux-gnu’ ‘–target=i386-redhat-linux-gnu’ ‘–program-prefix=’ ‘–prefix=/usr’ ‘–exec-prefix=/usr’ ‘–bindir=/usr/bin’ ‘–sbindir=/usr/sbin’ ‘–sysconfdir=/etc’ ‘–datadir=/usr/share’ ‘–includedir=/usr/include’ ‘–libdir=/usr/lib’ ‘–libexecdir=/usr/libexec’ ‘–localstatedir=/var’ ‘–sharedstatedir=/usr/com’ ‘–mandir=/usr/share/man’ ‘–infodir=/usr/share/info’ ‘–cache-file=../config.cache’ ‘–with-config-file-path=/etc’ ‘–with-config-file-scan-dir=/etc/php.d’ ‘–enable-force-cgi-redirect’ ‘–disable-debug’ ‘–enable-pic’ ‘–disable-rpath’ ‘–enable-inline-optimization’ ‘–with-bz2’ ‘–with-db4=/usr’ ‘–with-curl’ ‘–with-dom=/usr’ ‘–with-exec-dir=/usr/bin’ ‘–with-freetype-dir=/usr’ ‘–with-png-dir=/usr’ ‘–with-gd’ ‘–enable-gd-native-ttf’ ‘–with-ttf’ ‘–with-gettext’ ‘–with-ncurses’ ‘–with-gmp’ ‘–with-iconv’ ‘–with-mhash=/usr/lib’ ‘–with-jpeg-dir=/usr’ ‘–with-openssl’ ‘–with-png’ ‘–with-pspell’ ‘–with-regex=system’ ‘–with-xml’ ‘–with-expat-dir=/usr’ ‘–with-pcre-regex=/usr’ ‘–with-zlib’ ‘–with-layout=GNU’ ‘–enable-bcmath’ ‘–enable-exif’ ‘–enable-ftp’ ‘–enable-magic-quotes’ ‘–enable-safe-mode’ ‘–enable-sockets’ ‘–enable-sysvsem’ ‘–enable-sysvshm’ ‘–enable-discard-path’ ‘–enable-track-vars’ ‘–enable-trans-sid’ ‘–enable-yp’ ‘–enable-wddx’ ‘–enable-mbstring’ ‘–enable-mbstr-enc-trans’ ‘–enable-mbregex’ ‘–with-pear=/usr/share/pear’ ‘–with-imap=shared’ ‘–with-imap-ssl’ ‘–with-kerberos=/usr/kerberos’ ‘–with-ldap=shared’ ‘–with-mysql=shared,/usr’ ‘–with-pgsql=shared’ ‘–with-unixODBC=shared’ ‘–enable-memory-limit’ ‘–enable-bcmath’ ‘–enable-shmop’ ‘–enable-versioning’ ‘–enable-calendar’ ‘–enable-dbx’ ‘–enable-dio’ ‘–enable-mcal’ ‘–with-apxs2filter=/usr/sbin/apxs’

    Does anyone see anything missing? I assume that ‘–with-mysql=shared,/usr’ covers all the MySql stuff.

    Any ideas?

Viewing 1 replies (of 1 total)
  • Only that perhaps you might have better luck with this on the wp-hackers list: http://lists.automattic.com/ – the people who frequent that list are the ones with programming backgrounds as well as knowledge of wp’s innards and workings.

Viewing 1 replies (of 1 total)
  • The topic ‘we upgraded our PHP on the server and now WordPress is dead’ is closed to new replies.