Red Hat Bugzilla – Bug 146826
ab command used in NETWORK test timed out in fast network
Last modified: 2007-04-18 13:19:04 EDT
Description of problem:
In NETWORK test, 'ab -c 128 -k -n 256 $ipaddress/httptest.file' was
used to exercise httpd on test machine. However, it will get time
out and terminate NETWORK test in fast network. Tried test machine
and server with such network condition. ie. above ab command got
timeout. If during the execution of ab command, a ping flood command
such as 'ping -c15000 -f -s65507' from test machine to server machine
to increase network load caused the ab command finished normally
without timeout. That proved the ab command used in NETWORK test was
sensitive to network load, and probably was not suitable for
Version-Release number of selected component (if applicable):
Need network between test machine and test server lost no packet at
least for 'ping -c1000 -f -s65507' to get above ab command timed out.
Steps to Reproduce:
1.'dd if=/dev/zero of=/var/www/html/httptest.file bs=1M count=12' on
the test machine
2. start httpd on test machine
3. on test server machine do
'ab -c 128 -k -n 256 $ipaddr/httptest.file'
4. above ab command will get timed out
5. repeat 3, and do 'ping -c15000 -f -s65507' from test machine to
test server, ab command will finished normally without timeout
Both 4 and 5 should all be finished without timeout.
thanks. note that we've updated the ab parameters in the latest errata to avoid
timeouts -- you can update over rhn.
Thanks. Couldn't fine related errata in rhn yet with serach of rhr2 and
redhat-ready. Please advise.
It's on the hardware certification (final) subchannel of RHEL 4 RC.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.