Thanks for the fix, investigation and writeup.

On Feb 8, 2013 10:54 PM, "Damien Regad" <> wrote:
I rebooted the server this morning at 07:16 CET (it went down at 06:35).

After a quick analysis, the crash was caused by the server running out of
memory, apparently due to spawning a huge number of apache2 processes (239); at
that point (06:16 CET), kernel killed mysqld.

I don't have time to go into details now, but a quick look in apache error log,
shows a very large number of errors, originating from several 180.76.x.x ip's
requesting non-existent files. This resolves to

Details on IP address

% [ node-2]
% Whois data copyright terms

inetnum: -
netname:        Baidu
descr:          Beijing Baidu Netcom Science and Technology Co., Ltd.
descr:          Baidu Plaza, No.10, Shangdi 10th street,Haidian District
country:        CN
admin-c:        WN141-AP
tech-c:         JC2179-AP
mnt-by:         MAINT-CNNIC-AP
mnt-lower:      MAINT-CNNIC-AP
mnt-routes:     MAINT-CNNIC-AP
status:         ALLOCATED PORTABLE
changed: 20090715
source:         APNIC

Not sure if that's the root cause or not.


Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
mantisbt-dev mailing list