Today I was cutting one of our client’s development wordpress sites over to production and ran into a couple of tweaks that were needed.
Mainly, I wanted to get Munin hooked up to the new server so we could monitor system load, disk activity, mysql activity, and the apache statistics. However, when I went to set up the Apache and Mysql plugins there were a few issues that needed to be tweaked.
First, the .htaccess file for WordPress was causing the /server-status/ url to get hijacked by WP prior to getting processed by the Apache Status Module. Based on this post I needed to adjust the .htaccess file to ignore the status requests, and wound up with:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_URI} !=/server-status/?auto
RewriteCond %{REQUEST_URI} !=/server-status
RewriteCond %{REQUEST_URI} !=/server-status/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
Next, when the munin apache modules where run an error like the following would occur:
Can’t locate object method “new” via package “LWP::UserAgent”
the solution based on this post was to install the libwww-perl package, which provides those methods. This was able to get the Munin Apache Plugins working.
As for Mysql – based on this post I had to install the libcache-cache-perl and libipc-sharelite-perl packages to meet the missing dependencies.
Now it’s just a matter of waiting for the hits to come in and stare at the graphs for a while.

