Analyzing Core Dump File

Yeah, I know core dump files may eat up user’s space quickly. But it is definitely a sign that something wrong with their scripts. So, keeping coredump files is sometimes useful so that we can analyze it properly. Here’s how to analyze core dump files :
strings /home/user/public_html/core.11051|head
You will find what scripts causing the coredump files.
or get a clear view with :
gdb /usr/bin/php /home/user/public_html/core.11051

Hope it can be useful for you!

Fixing File and Folder Permission on suPHP

Just for my own note
After installing suPHP on server, execute :
find /home/*/public_html -type d -exec chmod 755 {} \;
This command fix all folder permission

find /home/*/public_html -name '*.php' -o -name '*.php[345]' -o -name '*.phtml'| xargs chmod -v 644
This command fix all file permission

#!/bin/bash
cd /var/cpanel/users
for user in *
do
chown -R $user.$user /home/$user/public_html/*
done
This script fix all ownership issue

Joomla Logged Out when Uploading Image

I got a strange behaviour with Joomla after I apply suhosin and suphp on my cPanel hosting server. When I upload image through Media Manager, suddenly Joomla logged out.

On error_log I see that it has something crashed with flash.

I found a simple solution for this problem. Just disable flash upload on Global Config >> System >> Enable Flash Uploader

Disable CoreDump on Apache with suPHP

The idea of limiting user’s vhost resource usage on Apache brings me to give the suPHP a try. suPHP makes PHP process owned by the owner it self, not “nobody” or apache user, enabling us to limit resource per vhost.

After setting up suPHP with rlimit rule per vhosts, I see that Rlimit really works. Apache kills all PHP execution that hit the Rlimit. So, basically we can have a containers that lock user’s PHP execution, thus preventing user to overload the server with buggy or highload type of PHP script.
But a new problem arised. When PHP execution killed, it generate coredump files. Coredump files are very useful to traceback any crash issues that occur during PHP execution. But I got them all over user’s directory, especially  on user’s directory that have a highload type of PHP script. The size may vary from 1MB to 40MB (on my system). They eat up users space every time a greedy resource PHP execution killed.

Install Munin & RRDTool on cPanel Centos5

Installing Munin on a latest Centos 5 via WHM (cPanel) can be very painful (takes a long night googling for me.. lol). On my server (CENTOS Enterprise 5.2 x86_64) – under “Manage Plugin” menu on WHM, it shows : Can’t locate RRDs.pm.

First you have to install rrdtool, rrdtool-devel, and perl-rrdtool. Here’s how to install it (it works for me) :

wget http://dag.wieers.com/rpm/packages/rrdtool/perl-rrdtool-1.2.23-1.el5.rf.x86_64.rpm
wget http://dag.wieers.com/rpm/packages/rrdtool/rrdtool-devel-1.2.23-1.el5.rf.x86_64.rpm
wget http://dag.wieers.com/rpm/packages/rrdtool/rrdtool-1.2.23-1.el5.rf.x86_64.rpm
rpm -ivh rrdtool-1.2.23-1.el5.rf.x86_64.rpm rrdtool-devel-1.2.23-1.el5.rf.x86_64.rpm perl-rrdtool-1.2.23-1.el5.rf.x86_64.rpm


And now you’re ready to install Munin through WHM.

cPanelProxy No Longer Needed?

Recently I installed a new server with the latest cPanel release (cPanel 11.23.3-R25623) on Centos 5 64bit version. I notice that under “Tweak Setting” menu on WHM, there are new features that interesting :

Add proxy VirtualHost to httpd.conf to automatically redirect unconfigured cpanel, webmail, webdisk and whm subdomains to the correct port (requires mod_rewrite and mod_proxy)

Automatically create cpanel, webmail, webdisk and whm proxy subdomain DNS entries for new accounts. When this is initially enabled it will add appropriate proxy subdomain DNS entries to all existing accounts. (Use /scripts/proxydomains to reconfigure the DNS entries manually)

When I give a try on those feature, it did work. cPanel become accessible through common http port (80) (instead of port 2082) when we access http://cpanel.domainname.tld. It also work for webmail, WHM, and webdisk.

Meaning we probably dont need a cPanelProxy anymore.

Ganti Web Server dengan i-Phone

Trend yang terus menerus ada pada dunia IT terutama soal ergonomi dan form factor adalah pada pengecilan ukuran dan bentuk. Inget gak bentuk – bentuk server jadul yang pake pedestal casing? Bentuknya ajegile .. guedhe banget!

Tapi kalau yang satu ini sungguh ide ngawur : Mengganti Web Server dengan i-Phone

Centos 5 on Intel P35 based ASUS Motherboard

Few months ago I decide to buy a new computer for our hosting services that planned to be colocated at Jakarta (directly connected with IIX – Indonesian Internet eXchange). The specs was great (Q6600 – Intel QuadCore, with 4Gb of RAM, and P5KC Asus Motherboard). Sadly my favourite CentOS cannot be installed smoothly. But thank god now server is up and running with CentOS 5 and CPANEL installed – ready to roar!!!

Here’s some problem before :

1. DVD-ROM was detected, but no SATA Disk detected
   Solution : put acpi=off on /etc/grub.conf, but problem no. 2 comes up
2. Installation went through smoothly, but SATA disks are detected as IDE
   So I got a very poor disks performance. Usualy when I perform “hdparm -Tt /dev/sdX” on SATA disks, Timing buffered disk reads will hit 60 – 70MB/sec. But on my new machine, it shows only 4MB/sec. And it’s not detected as sdX, but hdX
3. Attansic onboard ethernet is not detected
   But it’s quite easy to solve this problem. Just put Centos compatible ethernet, or download attansic ethernet driver for linux. I do both of it (hey .. we need backup right?)

What I most concerned is problem No#2. Get real!! 4MB/sec?

7 Reason of Why I Use WordPress.com

These are the main reason even if I have my own hosting servers :

1. WordPress.com is free and keep up2date
2. No need for Agung’s help to install something on this blog
3. I dont want to carry hosting business for my personal need (naive … eh?)
4. No need to do deletion if I get bored with this blog someday
5. No server migration needed if server is in trouble. WordPress people would gladly do it for me for free
6. No software needed (no FTP, no SSH, no CPANEL stuff, nothing! Just a browser)
7. No domain needed, meaning I can reduce my annual personal expenses (LOL)