perfsonar-user - Re: [perfsonar-user] local tool did not complete in allocated time frame and was killed
Subject: perfSONAR User Q&A and Other Discussion
List archive
Re: [perfsonar-user] local tool did not complete in allocated time frame and was killed
Chronological Thread
- From: Brian Tierney <>
- To: Gaetano Vocca <>
- Cc: "" <>
- Subject: Re: [perfsonar-user] local tool did not complete in allocated time frame and was killed
- Date: Wed, 28 Jan 2015 12:06:23 -0800
That will will also cause the test to time out. You need to make sure the full range of owamp and bwctl ports is open.
Dear all,
While performing some test campaign I receive this kind of output quite often, both when using owamp and iperf3 as tool.
Though I know there is some slowness in our network I wonder if there is any parameter that I can use with bwping or bwctl to make this frequency decrease, even at the cost of slowing down a bit the test execution speed.
Thank you
Gaetano
<TEST_CONFIG>;
tool: owamp;
user: ;
limit_class: root;
start_time: 1422458470;
is_host_sender: NO;
tos: 0;
client: 192.168.12.103;
sender: 192.168.12.17;
receiver: 192.168.12.103;
duration: 10;
use_udp: NO;
bandwidth: 0;
window: 0;
len_buffer: 0;
report_interval: 0;
parallel_streams: 0;
units:
output_format:
use_dynamic_window_sizing: NO;
</TEST_CONFIG>;
<RECV_OUTPUT>;
owampd[1120]: WARNING: No limits specified.;
owampd[1121]: Connection to ([192.168.12.103]:5495) from ([192.168.12.17]:56318);
owampd[1121]: ControlSession([192.168.12.103]:5495) accepted from userid(nil):([192.168.12.17]:56318);
owampd[1120]: ResReq ALLOWED: default:request:bandwidth = 672 (result = 0, limit = 0);
owampd[1120]: ResReq ALLOWED: default:request:disk = 450 (result = 0, limit = 0);
owampd[1120]: owampd: exiting...;
owampd[1121]: OWPDQuery: Unable to contact parent;
owampd[1121]: OWPDQuery: Unable to contact parent;
owampd[1120]: owampd: exited.;
;
bwctl: local tool did not complete in allocated time frame and was killed;
</RECV_OUTPUT>;
<SEND_OUTPUT>;
owping: FILE=protocol.c, LINE=2703, _OWPReadFetchAck: Unable to read from socket.;
owping: FILE=owping.c, LINE=1838, Unable to fetch data for sid(c0a80c67d8737ceb7450c8fdc8f1a4fa);
Approximately 8.1 seconds until results available;
</SEND_OUTPUT>;
Energy Sciences Network (ESnet), Berkeley National Lab
http://fasterdata.es.net
- [perfsonar-user] local tool did not complete in allocated time frame and was killed, Gaetano Vocca, 01/28/2015
- Re: [perfsonar-user] local tool did not complete in allocated time frame and was killed, Brian Tierney, 01/28/2015
- Re: [perfsonar-user] local tool did not complete in allocated time frame and was killed, Gaetano Vocca, 01/28/2015
- Re: [perfsonar-user] local tool did not complete in allocated time frame and was killed, Brian Tierney, 01/28/2015
Archive powered by MHonArc 2.6.16.