Bug 480890 - Network test failed with "tcp latency test failed" error (rhel4 x86_64)
Network test failed with "tcp latency test failed" error (rhel4 x86_64)
Status: CLOSED NOTABUG
Product: Red Hat Hardware Certification Program
Classification: Red Hat
Component: Test Suite (tests) (Show other bugs)
5.3
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Greg Nichols
Lawrence Lim
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-01-21 01:13 EST by Yan Tian
Modified: 2014-03-25 20:56 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-01-21 03:59:33 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
network/output.log (1.93 KB, text/x-log)
2009-01-21 01:13 EST, Yan Tian
no flags Details
/var/hts/results.xml (789.52 KB, text/xml)
2009-01-21 01:14 EST, Yan Tian
no flags Details
network/output.log (2.12 KB, text/x-log)
2009-01-21 03:10 EST, Yan Tian
no flags Details

  None (edit)
Description Yan Tian 2009-01-21 01:13:40 EST
Created attachment 329548 [details]
network/output.log

Description of problem:
Network test failed with following errors:
tcp test:
/bin/sh: lat_tcp: command not found
test cycle 1 of 5
testing latency...
Error: tcp latency test failed
Error: "lat_tcp 10.66.70.105" has output on stderr
Restoring all interfaces...
Network test on device eth0 failed
...finished running ./network.py, exit code=1

Version-Release number of selected component (if applicable):
hts-5.3-14.el4

How reproducible:
always

Steps to Reproduce:
1.start hts server on 10.66.70.105
2.hts run -t network -n 10.66.70.105
3.
  
Actual results:
Network test failed

Expected results:
Network test passed

Additional info:
Attached the network/output.log and /var/hts/result.xml file
Comment 1 Yan Tian 2009-01-21 01:14:41 EST
Created attachment 329550 [details]
/var/hts/results.xml
Comment 2 YangKun 2009-01-21 01:41:20 EST
have you installed the lmbench package ?
Comment 3 Yan Tian 2009-01-21 01:45:07 EST
(In reply to comment #2)
> have you installed the lmbench package ?

Yes.
# rpm -q dt lmbench stress hts
dt-15.14-2.EL4
lmbench-2.0.4-2.EL4
stress-0.18.8-1.3.EL4
hts-5.3-14.el4
Comment 4 YangKun 2009-01-21 02:19:00 EST
the lmbench package you're using is obsolete, which installs the binaries into "/usr/lib/lmbench/bin/i686-pc-linux-gnu/":

    <15:10:32 kun@yk>$ rpm -qpl lmbench-2.0.4-2.EL5.i386.rpm | grep lat_tcp
    /usr/lib/lmbench/bin/i686-pc-linux-gnu/lat_tcp
    /usr/share/doc/lmbench-2.0.4/doc/lat_tcp.8


we have upgraded lmbench to version 3.0a7 long time ago, which installs the binaries into the standard "/usr/bin/":

    <15:08:12 kun@yk>$ rpm -qpl lmbench-3.0a7-6.EL5.i386.rpm | grep lat_tcp
    /usr/bin/lat_tcp
    /usr/share/doc/lmbench-3.0a7/doc/lat_tcp.8
    /usr/share/doc/lmbench-3.0a7/doc/lat_tcp.tbl


please switch to lmbench-3.0a7 and see if this issue still exists, the latest lmbench package on RHN should be lmbench-3.0a7-6

Thanks
-YK
Comment 5 Yan Tian 2009-01-21 03:10:58 EST
Created attachment 329565 [details]
network/output.log

Updated lmbench to 3.0a7-6.EL4, then network test failed with "tcp bandwidth test failed" error.
Comment 6 YangKun 2009-01-21 03:25:55 EST
error is "bw_tcp errors: socket connection: Connection refused"

plesae make sure the firewall is turned off on both machines and the "hts server status" shows all the proper services are running on the network server.
Comment 7 Yan Tian 2009-01-21 03:59:33 EST
The firewall was turned off on both machines. I updated lmbench to 3.0a7-6.EL4 on hts server machine, then re-run network test passed. Closed this bug.

Note You need to log in before you can comment on or make changes to this bug.