Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] BWCTLD segmantation fault on Raspberry Pi

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] BWCTLD segmantation fault on Raspberry Pi


Chronological Thread 
  • From: Aaron Brown <>
  • To: "" <>
  • Cc: "" <>
  • Subject: Re: [perfsonar-user] BWCTLD segmantation fault on Raspberry Pi
  • Date: Thu, 18 Dec 2014 21:13:54 +0000
  • Accept-language: en-US
  • Authentication-results: sesanv.com; dkim=none (message not signed) header.d=none;

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




Archive powered by MHonArc 2.6.16.

Top of Page