Kent Nasveschuk

resolved

I have found the underlying problem with the plugins. A similar problem exists with uploading images. They are uploaded with no permissions and the thumbnails are not created.

In my case my 3 web servers are 32-bit systems. The NFS file system they are mounting that contains the WordPress installation is 64-bit. The little amount that I have read says that 32-bit client using a 64-bit file system may break some applications. This is indeed what happened. Since I am using GlusterFS 3.4.2, I exported the entire volume with this extra option: “gluster volume set web-data nfs.enable-ino32 on”. After remounting the volumes all problems disappeared, plugins no longer deactivate, images upload, thumbnails get created.

Hope this helps someone with similar problems.

I don’t know what in the WP code caused this problem BUT I found the solution. First, the entire WordPress installation is on NFS. When I moved just the “plugins” directory to hosts file system “/usr/local/plugins” symlinked “wp-content/plugins” from the real plugins directory all worked, plus fixed other things like image uploads.

I also tested placing the WordPress installation on a Gluster 3.4.2 volume, the plugin problem was the same.

Hope this helps someone else having NFS issues.

db.php goes in wp-content/

This is what I used to get HyperDB running with HAProxy. HAProxy listens on 6306 (MySQL master) 3306 (MySQL slaves):

db-config.php
….
$wpdb->add_database(array(
‘host’ => ‘haproxy:6306’, // If port is other than 3306, use host:port.
‘user’ => ‘user’,
‘password’ => ‘password’,
‘write’ => 1,
‘read’ => 0,
‘name’ => ‘wp_mu’,
‘dataset’ => ‘global’,
‘timeout’ => 0.2,
));

$wpdb->add_database(array(
‘host’ => ‘haproxy:3306’, // If port is other than 3306, use host:port.
‘user’ => ‘user’,
‘password’ => ‘password’,
‘write’ => 0,
‘read’ => 1,
‘name’ => ‘wp_mu’,
‘dataset’ => ‘global’,
‘timeout’ => 0.2,
));
….

wp-config.php
….
/*
define(‘DB_NAME’, ‘wp_mu’);
define(‘DB_USER’, ‘user’);
define(‘DB_PASSWORD’, ‘password’);
define(‘DB_HOST’, ‘haproxy’);
*/
….

Thats about it.

Update, latest hyperDB is working with WP3.8.1. The problem I had was not related to WP installation.

Testing wordpress 3.8.1 with HA Proxy. 3 backend web apache servers. Unfortunately, HyperDB latest (2014-03-04) has problems on WP 3.8.1. I have MySQL master and 2 slaves (connections also proxied via same HA Proxy).

On HA Proxy:
3306 -> read-only -> 2 slaves answering
6306 -> write-only -> 1 master answering
80 -> 3 apache web servers answering

I use an alternate DNS (bind on CentOS) for the above test environment for name resolution so URLs are not a problem, identical to production web site. Client uses same DNS.

Any suggestions on how to get HyperDB to work on 3.8.1?

I havent gotten latest hyperdb to work on 3.8.1.