LAMP setup ( For Odroid U2 users using Debian wheezy )

Getting rid of bothersome kernel "Booted secondary processor" and "shutdown" notice messages from kern.log

My Odroid servers "kern.log" is basically swamped with these messages "Booted secondary processor" and "shutdown" that occur at every minute. Tried tweaking the "/etc/sysctl.conf" specifically the kernel.printk line to say "kernel.printk = 3 3 1 3". 3 is supposed to be error level but still these notice messages seemed to get printed some how.

Finally this is what got rid of them by drastic measures.

Performance Impact of Drupal's Boost module

So my website has been running on Boost for more than a month now. Things should seem quicker, or atleast the content from my site should feel faster and the facebook and google plus and all those widgets load a bit later on.

Suspicious ipv6 activity when only Shorewall ipv4 as firewall active

So I have shorewall, the ipv4 version as the only running firewall on my server. For ipv6, there was a seperate package from shorewall to install and configure. What was worrying me was the activity on ipv6 that I was seeing in monitorix below.


Enabling Alternative Php Cache monitoring for Monitorix securely

To see the apc graph in monitorix securely, just add the following apc.conf file to "/etc/apache2/sites-availiable". Add the following contents to it:

Apache mod_cache and mod_file_cache

Here is another performance tip for your website. Take my blog for example. Examine all the static resources for it, that are possibly present for all of your webpage. In my case I could list them as below:

Analyzing io bottlenecks on linux for my drupal blog

So at this point my setup on the odroid u2 is humming along with memcached and php apc cache. The performance boost from this I described in this article here. At best I was getting 2 request/sec.

Disabling .htaccess lookups and merging to sites conf file for Drupal 7

So I managed to get my server to server almost 2 request/sec with my last incremental configuration tweaks using memcached described here. After memcached I had to analyze my server for bottle necks and io as expected was top of the list with mysql process at the top of io bottle-neck list. This finding I shared in this article here.

My custom rules for mod_security

This article will be place holder for the custom rules I keep adding for my blog based on my access logs. I'll try to keep it upto date as possible. Since I run a drupal 7 install, they should be viewed from that perspective.


Performance Impact of Memcache on Drupal

So in my previous article here, I did a stress test with php's APC enabled and drupals 2 performance modules "adv_agg" and minify. This was test #4 in that article. In this article I will carry over that test and see what new numbers are with memcache now configured for my drupal blog. How to confgure memcached you can read about it in my previous article here.

1-2-3 guide to quickly set up Memcache for Drupal

So this is how you can setup memcache for drupal. This guide is for a single server where memcache and drupal are all co-located. So at drupal's end, execute the following commands :

drush dl memcache -y
drush dl entitycache -y --dev


Next the apt-get command can be used to install the following packages:


apt-get install memcached libmemcached10 libmemcachedutil2 libmemcached-tools php5-memcache

Next hop to your drupal "sites/default/settings.php"


Subscribe to LAMP setup ( For Odroid U2 users using Debian wheezy )