Bad Blog!
You may have had some trouble seeing this page within the last 48 hours or so - which was due to my host (Cedant.com) turning off my account due to “abuse of MySQL” apparently. When I told Cedant WTF?, they replied with the following (in the More section). So, acting on the advice of two trusted fellow bloggers, I’ve increased the severity of my SpamKarma 2 installation to see if the problem was caused by spammers gone wild. Cross your fingers - and if you have any insight into any other possible causes, please let me know!
This is the e-mail that I received from my host, in response to my question about why they turned off my account temporarily:
This is typically because you either need to optimize your queries and/or possibly move old comments out. Here’s a look from the server load and it looks like blogging software that isn’t running well. We’ve released the hold on your account now, but please have this fixed right away or the admins will likely re suspend the account.
last pid: 33041; load averages: 8.19, 9.20, 7.43 up 35+15:55:07 08:45:48
536 processes: 9 running, 525 sleeping, 2 zombie
CPU states: 52.1% user, 7.6% nice, 37.5% system, 2.7% interrupt, 0.0% idle
Mem: 1028M Active, 360M Inact, 348M Wired, 105M Cache, 199M Buf, 168M Free
Swap: 2048M Total, 118M Used, 1930M Free, 5% InusePID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND
49793 mysql 82 14 52952K 42048K RUN 0 9:02 9.52% 9.52% mysqld
39325 mysql 18 14 52952K 42048K pause 0 7:52 9.23% 9.23% mysqld
39324 mysql 18 14 52952K 42048K pause 1 7:57 8.98% 8.98% mysqld
39332 mysql 84 14 52952K 42048K RUN 1 7:24 8.98% 8.98% mysqld
39328 mysql 82 14 52952K 42048K RUN 0 7:42 8.89% 8.89% mysqld
50577 mysql 82 14 52952K 42048K RUN 0 8:30 7.81% 7.81% mysqld
51368 mysql 82 14 52952K 42048K RUN 0 7:30 7.71% 7.71% mysqld
39327 mysql 18 14 52952K 42048K pause 1 8:42 5.47% 5.47% mysqld
50578 mysql 18 14 52952K 42048K pause 1 9:19 4.88% 4.88% mysqld
49792 mysql 18 14 52952K 42048K pause 1 9:15 4.88% 4.88% mysqld
32991 davidmsc 2 0 17408K 15344K sbwait 1 0:01 16.94% 4.39% perl
32983 davidmsc 2 0 17412K 15344K sbwait 0 0:01 11.39% 3.76% perl
32843 davidmsc 2 0 21560K 19476K sbwait 1 0:02 4.72% 3.37% perl
32937 davidmsc 2 0 17408K 15340K sbwait 0 0:01 5.09% 2.69% perlMySQL on localhost (4.0.27-log) up 12+21:03:03 [08:45:51]
Queries: 35.9M qps: 34 Slow: 12.9k Se/In/Up/De(%): 86/01/02/01Cache Hits: 23.6M Hits/s: 22.2 Hits now: 0.0 Ratio: 76.4% Ratio now: 0.0%
Key Efficiency: 100.0% Bps in/out: 672.1/ 2.0kId User Host/IP DB Time Cmd Query or State
— —- ——- — —- — ———-
1508394 davidmsc localhost davidmsc_c 1 Query select distinct tempTable_id, tempTable_blog_id, tempTable_status, tempTabl
1508396 davidmsc localhost davidmsc_c 1 Query select distinct tempTable_id, tempTable_blog_id, tempTable_status, tempTabl
1508364 davidmsc localhost davidmsc_c 3 Query create temporary table tempTableselect entry_id as tempTable_id, entry_blog
1508381 davidmsc localhost davidmsc_c 12 Query select distinct tempTable_id, tempTable_blog_id, tempTable_status, tempTabl
August 26th, 2006 at 10:36 am
SpamKarma 2 can be pretty hard on servers if you get a lot of spam, I think. I wouldn’t think increasing the severity would help if that’s the problem. You might try switching to Akismet for a while and see if that appeases your host.
March 3rd, 2007 at 12:33 pm
I looked at this report they sent.
Bogus Beans.
Any server op’s management team wouldn’t so much as sniff at something like this. I say this, because according to what they sent you, your buffer overflow parameters were so way below the norm. We have clients that operate at GIG levels, and still, things move along smoothly.
Your server op’s folks, if they knew what they were doing in the first place, would have written refresh/dump cache configs in to take care of any potential problems. Cache can gum it all up pretty quick…..
As far as spam??… well, SpamKarma is an extremely dated and heavy script… Akismet though lighter, isn’t much better… SpamKarma rates in as a bandwidth hog on many of todays faster server technologies.
Most modern op centers usually install spam filtering at the server in order to keep their clients from having to resort to using 3rd party spam utilities in the first place.
I don’t even have Akismet configured or turned on on my blog…. no reason for me to, as I am quite confident that our mail server software can handle anything that comes down the pike……