Hey, Sorry i think you should do "ps -ef | grep netperf" on both host, and see, if netperf server is starting and connecting to netperf client and vice-versa ..
Regards, DJ On Sat, Jun 14, 2014 at 2:54 AM, Bhupesh Purandare <[email protected]> wrote: > Hello, > > I did a ps -ef | grep autotest on both the machines while running netperf > and I found a bunch of autotest processes on both. > > ps -ef |grep autotest > root 5114 1 0 20:22 ? 00:00:00 /usr/bin/python > /ghostcache/autotest/autotestd /tmp/autoserv-4SQnjd -H autoserv --verbose > --hostname=10.15.23.62 --user=debug_user > /ghostcache/autotest/control.autoserv > root 5115 4975 0 20:22 ? 00:00:00 /usr/bin/python > /ghostcache/autotest/autotestd_monitor /tmp/autoserv-4SQnjd 0 0 > root 5116 5114 0 20:22 ? 00:00:00 /usr/bin/python -u > /ghostcache/autotest/autotest -H autoserv --verbose --hostname=10.15.23.62 > --user=debug_user /ghostcache/autotest/control.autoserv > root 5119 5116 0 20:22 ? 00:00:00 /usr/bin/python -u > /ghostcache/autotest/autotest -H autoserv --verbose --hostname=10.15.23.62 > --user=debug_user /ghostcache/autotest/control.autoserv > root 5120 5116 0 20:22 ? 00:00:00 /usr/bin/python -u > /ghostcache/autotest/autotest -H autoserv --verbose --hostname=10.15.23.62 > --user=debug_user /ghostcache/autotest/control.autoserv > root 5134 5116 0 20:22 ? 00:00:00 /usr/bin/python -u > /ghostcache/autotest/autotest -H autoserv --verbose --hostname=10.15.23.62 > --user=debug_user /ghostcache/autotest/control.autoserv > root 5161 5134 0 20:22 ? 00:00:00 /usr/bin/python -u > /ghostcache/autotest/autotest -H autoserv --verbose --hostname=10.15.23.62 > --user=debug_user /ghostcache/autotest/control.autoserv > root 5162 5134 0 20:22 ? 00:00:00 /usr/bin/python -u > /ghostcache/autotest/autotest -H autoserv --verbose --hostname=10.15.23.62 > --user=debug_user /ghostcache/autotest/control.autoserv > root 10405 5341 0 20:30 pts/0 00:00:00 grep autotest > > > ps -ef |grep autotest > root 7450 1 0 20:22 ? 00:00:00 /usr/bin/python > /ghostcache/autotest/autotestd /tmp/autoserv-RNgTgp -H autoserv --verbose > --hostname=10.15.23.82 --user=debug_user > /ghostcache/autotest/control.autoserv > root 7451 7362 0 20:22 ? 00:00:00 /usr/bin/python > /ghostcache/autotest/autotestd_monitor /tmp/autoserv-RNgTgp 0 0 > root 7452 7450 0 20:22 ? 00:00:00 /usr/bin/python -u > /ghostcache/autotest/autotest -H autoserv --verbose --hostname=10.15.23.82 > --user=debug_user /ghostcache/autotest/control.autoserv > root 7455 7452 0 20:22 ? 00:00:00 /usr/bin/python -u > /ghostcache/autotest/autotest -H autoserv --verbose --hostname=10.15.23.82 > --user=debug_user /ghostcache/autotest/control.autoserv > root 7456 7452 0 20:22 ? 00:00:00 /usr/bin/python -u > /ghostcache/autotest/autotest -H autoserv --verbose --hostname=10.15.23.82 > --user=debug_user /ghostcache/autotest/control.autoserv > root 7470 7452 0 20:22 ? 00:00:00 /usr/bin/python -u > /ghostcache/autotest/autotest -H autoserv --verbose --hostname=10.15.23.82 > --user=debug_user /ghostcache/autotest/control.autoserv > root 7499 7470 0 20:22 ? 00:00:00 /usr/bin/python -u > /ghostcache/autotest/autotest -H autoserv --verbose --hostname=10.15.23.82 > --user=debug_user /ghostcache/autotest/control.autoserv > root 7500 7470 0 20:22 ? 00:00:00 /usr/bin/python -u > /ghostcache/autotest/autotest -H autoserv --verbose --hostname=10.15.23.82 > --user=debug_user /ghostcache/autotest/control.autoserv > root 13027 9631 0 20:30 pts/0 00:00:00 grep autotest > > > In the netperf2.py, the run_once function has the following default > definition: > def run_once(self, server_ip, client_ip, role, test = 'TCP_STREAM', > test_time = 15, stream_list = [1], test_specific_args = > '', > cpu_affinity = '', dev = '', bidi = False, wait_time = 5): > > > Can someone suggest what command line/exe/script this is trying to run? I > wonder if there are any connectivity issues between the client and server > machines... > > Thanks, > Bhupesh > > -------------------------------------------- > On Fri, 13/6/14, Unix SA <[email protected]> wrote: > > Subject: Re: [Autotest] Autotest-kernel Digest, Vol 24, Issue 5 > To: [email protected] > Date: Friday, 13 June, 2014, 9:54 PM > > Hello, > > while running netperf can you check "ps -ef |grep > autotest" and monitor on client and server both, it > looks to me it starts server and it's waiting for client > to connect or it starts client and waits for server to > start.. dont remember exactly but i faced it and resolved it > before. > > > Regards, > DJ > > > On Fri, Jun 13, 2014 > at 9:45 PM, <[email protected]> > wrote: > > Send > Autotest-kernel mailing list submissions to > > [email protected] > > > > To subscribe or unsubscribe via the World Wide Web, visit > > https://www.redhat.com/mailman/listinfo/autotest-kernel > > or, via email, send a message with subject or body > 'help' to > > [email protected] > > > > You can reach the person managing the list at > > [email protected] > > > > When replying, please edit your Subject line so it is more > specific > > than "Re: Contents of Autotest-kernel digest..." > > > > > > Today's Topics: > > > > 1. Fwd: Netperf2 test failing with error: "timeout > waiting for > > barrier: start_1" in client.0./client.0.DEBUG > (Bhupesh Purandare) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Thu, 12 Jun 2014 17:32:06 -0400 > > From: Bhupesh Purandare <[email protected]> > > To: [email protected] > > Subject: [Autotest] Fwd: Netperf2 test failing with error: > "timeout > > waiting for barrier: start_1" in > client.0./client.0.DEBUG > > Message-ID: <[email protected]> > > Content-Type: text/plain; charset="iso-8859-1" > > > > > > > > > > -------- Original Message -------- > > Subject: Netperf2 test failing with error: > "timeout waiting for > > barrier: start_1" in client.0./client.0.DEBUG > > Date: Thu, 12 Jun 2014 16:13:40 -0400 > > From: Bhupesh Purandare <[email protected]> > > To: [email protected], > Josh Hunt <[email protected]> > > > > > > > > Hello Amos, > > I am trying to run the Netperf2(client) test in Autotest > 0.1.5.1. I saw > > your git commits for netperf in autotest. > > I am using two hosts as required for the test, setting the > IP address of > > one to 'client' and the other to 'server' in > the control.client file. > > > > The tests are failing and I see the following in the > client.0.DEBUG logs > > > > 06/12 18:43:16 DEBUG| parallel:0030| File > "/ghostcache/autotest/parallel.py", line 18, in > fork_start > > 06/12 18:43:16 DEBUG| parallel:0030| l() > > 06/12 18:43:16 DEBUG| parallel:0030| File > "/ghostcache/autotest/job.py", line 529, in > <lambda> > > 06/12 18:43:16 DEBUG| parallel:0030| l = lambda : > test.runtest(self, url, tag, args, dargs) > > 06/12 18:43:16 DEBUG| parallel:0030| File > "/ghostcache/autotest/test.py", line 115, in > runtest > > 06/12 18:43:16 DEBUG| parallel:0030| > job.sysinfo.log_after_each_iteration) > > 06/12 18:43:16 DEBUG| parallel:0030| File > "/ghostcache/autotest/shared/test.py", line 931, > in runtest > > 06/12 18:43:16 DEBUG| parallel:0030| > mytest._exec(args, dargs) > > 06/12 18:43:16 DEBUG| parallel:0030| File > "/ghostcache/autotest/shared/test.py", line 426, > in _exec > > 06/12 18:43:16 DEBUG| parallel:0030| > _call_test_function(self.execute, *p_args, **p_dargs) > > 06/12 18:43:16 DEBUG| parallel:0030| File > "/ghostcache/autotest/shared/test.py", line 841, > in _call_test_function > > 06/12 18:43:16 DEBUG| parallel:0030| return > func(*args, **dargs) > > 06/12 18:43:16 DEBUG| parallel:0030| File > "/ghostcache/autotest/shared/test.py", line 299, > in execute > > 06/12 18:43:16 DEBUG| parallel:0030| > postprocess_profiled_run, args, dargs) > > 06/12 18:43:16 DEBUG| parallel:0030| File > "/ghostcache/autotest/shared/test.py", line 219, > in _call_run_once > > 06/12 18:43:16 DEBUG| parallel:0030| > self.run_once(*args, **dargs) > > 06/12 18:43:16 DEBUG| parallel:0030| File > "/ghostcache/autotest/tmp/site_tests/netperf2/netperf2.py", > line 103, in run_once > > 06/12 18:43:16 DEBUG| parallel:0030| > 1200).rendezvous(*all) > > 06/12 18:43:16 DEBUG| parallel:0030| File > "/ghostcache/autotest/shared/base_barrier.py", > line 514, in rendezvous > > 06/12 18:43:16 DEBUG| parallel:0030| > self._run_client(is_master=False) > > 06/12 18:43:16 DEBUG| parallel:0030| File > "/ghostcache/autotest/shared/base_barrier.py", > line 391, in _run_client > > 06/12 18:43:16 DEBUG| parallel:0030| while > self._remaining() is None or self._remaining() > 0: > > 06/12 18:43:16 DEBUG| parallel:0030| File > "/ghostcache/autotest/shared/base_barrier.py", > line 184, in _remaining > > 06/12 18:43:16 DEBUG| parallel:0030| raise > error.BarrierError(errmsg) > > 06/12 18:43:16 DEBUG| parallel:0030| BarrierError: timeout > waiting for barrier: start_1 > > 06/12 18:43:16 INFO | job:0212| END ABORT > netperf2.client netperf2.client timestamp=1402598596 > localtime=Jun 12 18:43:16 > > 06/12 18:43:16 DEBUG| base_job:0348| Persistent state > client._record_indent now set to 1 > > 06/12 18:43:16 DEBUG| base_job:0375| Persistent state > client.unexpected_reboot deleted > > 06/12 18:43:16 ERROR| job:1341| JOB ERROR: timeout > waiting for barrier: start_1 > > 06/12 18:43:16 INFO | job:0212| END ABORT ---- > ---- timestamp=1402598596 localtime=Jun 12 > 18:43:16 timeout waiting for barrier: start_1 > > 06/12 18:43:16 DEBUG| base_job:0348| Persistent state > client._record_indent now set to 0 > > > > > > > > I tried tweaking the netperf2.py file to set higher values > for time parameters; e.g. I tried increasing the wait time > for server start from 10 minutes to 20 minutes. > > I also increased the wait time for the "server to reach > this point" from 5 minutes to 10 minutes. > > > > elif role == 'client': > > # Wait up to ten minutes for the server to start > > self.job.barrier(client_tag, 'start_%d' % > num_streams, > > *1200*).rendezvous(*all) > > self.client(server_ip, test, test_time, > num_streams, > > test_specific_args, cpu_affinity) > > # Wait up to 5 minutes for the server to also reach > this point > > self.job.barrier(client_tag, 'stop_%d' % > num_streams, > > > *600*).rendezvous(*all) > > > > > > > > Can you kindly guide as to what might be causing the test > timeout? Is there some documentation we should be using to > run this test correctly or are there any patches available > to be applied? > > Any help will be much appreciated. > > > > > > Thanks, > > Bhupesh > > > > > > > > > > -------------- next part -------------- > > An HTML attachment was scrubbed... > > URL: < > https://www.redhat.com/archives/autotest-kernel/attachments/20140612/854edf0a/attachment.html > > > > > > > ------------------------------ > > > > _______________________________________________ > > Autotest-kernel mailing list > > [email protected] > > https://www.redhat.com/mailman/listinfo/autotest-kernel > > > > End of Autotest-kernel Digest, Vol 24, Issue 5 > > ********************************************** > > > > > -----Inline Attachment Follows----- > > _______________________________________________ > Autotest-kernel mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/autotest-kernel >
_______________________________________________ Autotest-kernel mailing list [email protected] https://www.redhat.com/mailman/listinfo/autotest-kernel
