perfSONAR User Q&A and Other Discussion

[Gaetano Vocca <>]

Hi,

thank you, I was able to install iperf on the Raspberry by means pf apt-get.

Coming to Aaron’s question below, I was able to run iperf3

 

iperf3 -u -c <always the same receiver>

 

from the Raspberry and it worked, so it seems more a bwctl issue, correct?

 

Have a nice day

Gaetano

 

Da: [mailto:] Per conto di Alan Whinery
Inviato: giovedì 18 dicembre 2014 23:51
A:
Oggetto: Re: [perfsonar-user] BWCTLD segmantation fault on Raspberry Pi

 

I usually get iperf by doing "apt-get install iperf" on a standard Raspbian install...

On 12/18/2014 12:34 PM, Gaetano Vocca wrote:

Thank you but I am actually looking for Iperf in order to follow Aaron 's suggestion. 

 

Thanks

Il giorno 18/dic/2014, alle ore 23:30, Brian Tierney <> ha scritto:

 

iperf3 is here: https://github.com/esnet/iperf

 

 

On Thu, Dec 18, 2014 at 2:22 PM, Gaetano Vocca <> wrote:

Hi Aaron,
Thank you for your kind answer.
I will surely try but would you please point me to the repository for Iperf?

Thank you
Gaetano



> Il giorno 18/dic/2014, alle ore 22:13, Aaron Brown <> ha scritto:

>
> Hi Geatano,
>
> Could you try running it with iperf or nuttcp instead of iperf3, to see if it’s a bwctl issue or an iperf3 issue.
>
> Cheers,
> Aaron
>
>> On Dec 18, 2014, at 2:11 PM, wrote:
>>
>> Hello,
>> this is my first post and I would like to say hi to the list members and thank
>> you for all the nice work about the bwctl suite.
>>
>> It is indeed about bwctld that I am writing here because I am trying to run it
>> on a Raspberry Pi with latest Raspbian (Sept 2014).
>> I downloaded the latest (at time) sources (1.5.2) and I went through the whole
>> building flow without any problem. I am able to run tests in almost any way
>> except for the case in which the Raspberry is the "sending" machine (e. g.
>> bwctl -T iperf3 -u -c <receiver ip>) of UDP traffic.
>> In fact, in such case, I find in the logs
>>
>> raspberrypi bwctld[2589]: FILE=endpoint.c, LINE=1455, _BWLEndpointStatus:
>> Child #2590 exited from signal #11
>>
>> This is deterministic, it happens all the times but only when running the test
>> from the Raspberry with -u and -c. I tested the same code on a regular PC and
>> it worked fine.
>>
>> Do you have an idea of what could be the issue?
>>
>> Thank you in advance
>> Gaetano
>

 

--

Brian Tierney, http://www.es.net/tierney
Energy Sciences Network (ESnet), Berkeley National Lab
http://fasterdata.es.net