# Sabotaging an apache server

Bit of an odd one this. We have a very political management situation brewing and as the developer looking after the interaction with the hosting company, I have been asked to perform a bit of sabotage to test out our infrastructure providers monitoring and response times to failure in the hosting environment.

Essentially we want one of our Apache nodes to fail and stop responding to requests. I know the load balancer will take it out of the pool very quickly so no worries about that.

So, what are your favourite ways to bork an apache server without it looking like you are intentionally breaking it? Any way of locking up the entire box would be preferable.

Environment is Apache running on RHEL 5.

-
Hire a consultant? –  t1nt1n May 25 '12 at 10:52
Red Hat 5 was released in 1998. –  adaptr May 25 '12 at 10:55
I think he probably means RHEL 5... –  ℝaphink May 25 '12 at 11:11
Indeed RHEL 5.7 –  Nick Downton May 25 '12 at 11:19
In the end, I talked management in to something less severe, simply shutting down the box, but with the proviso they take responsibility for it. Ideally I would have run Tim Brigham's idea but with these servers being virtual and not having seen a working test of vmotion yet, I didn't feel like risking affecting other servers on the hardware. –  Nick Downton May 28 '12 at 17:07

Do a sudo su apache and execute a fork bomb with

 :(){ :|:& };:


This kind of behavior is common enough in programming mistakes to not raise many eyebrows. Plus it locks up.the whole server.

EDIT - As pointed out there may be legal limitations for executing this on hosted hardware. Also depending on your configuration this may only work running under the root account.

-
I should be wary of doing anything that might break contracts, acceptable use policies, or even the law in some countries, especially as there is "a very political management situation brewing". –  ramruma May 25 '12 at 12:57
@ramruma That's the point of this whole question... –  TheLQ May 25 '12 at 13:37
On RHEL (and most properly configured distros) the Apache user doesn't have a shell so you can't execute a command in this manner. Command works nicely though :) –  James Yale May 25 '12 at 15:09

If you are interested in monitoring and response times, then just stop Apache. That should be enough to trigger an alert and a response.

-
Indeed. This emulates the, "Apache hit a SEGFAULT and crashed out" failure, which you do want to know about. –  sysadmin1138 May 25 '12 at 11:15

Any way of locking up the entire box would be preferable.

Kind of dramatic but you can force a crash/panic on the system with:

echo c > /proc/sysrq-trigger


Provided that:

cat /proc/sys/kernel/sysrq


has a value greater than 0.

-

http://httpd.apache.org/docs/2.0/programs/ab.html

and you can perform a lot of requests

-
Under "a very political management situation brewing" I would not DoS a web server. –  Janne Pikkarainen May 25 '12 at 13:35
@JannePikkarainen That's the point of this whole question... However I do wonder if a DoS attack will trigger a response at all –  TheLQ May 25 '12 at 13:47
Yes, but using ab is so blatantly obvious anyone can catch you from using it. I can use bazooka, but it sure ain't a silent way to get someone's attention. –  Janne Pikkarainen May 25 '12 at 14:19
@TheLQ, I see nothing in the question to suggest that there is a desire to aggravate an already bad relationship. The question is about testing of the monitoring system and subsequent response, not pissing people off. –  John Gardeniers May 26 '12 at 13:25

Depending on the situation you want to try, I would just use a mod_rewrite directive to redirect all request to an non existing page, generating a 404 error. Not sure it complies with your definition of "stop responding to requests".

If you want to push it to a machine error, you could just down the network adapter. Apache can't get request, nor can you ssh the machine. This would simulate a network failure (broken cable or other). Downside, you'll need to access the physical server to bring it up (or reboot it).

-
A 404 is still a response. It would also break the web site and from my reading of the question that's not what is intended at all. You will note that the OP has mentioned that the load balancer will ensure users won't really notice the targeted server going down. –  John Gardeniers May 26 '12 at 13:27