Skip to Content.
Sympa Menu

perfsonar-user - [perfsonar-user] bwctl throughput - JSON parsing error

Subject: perfSONAR User Q&A and Other Discussion

List archive

[perfsonar-user] bwctl throughput - JSON parsing error


Chronological Thread 
  • From: Brian Candler <>
  • To: "" <>
  • Subject: [perfsonar-user] bwctl throughput - JSON parsing error
  • Date: Mon, 30 Nov 2015 11:35:04 +0000
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=pobox.com; h=to:from:subject :message-id:date:mime-version:content-type; q=dns; s=sasl; b=K4/ ex9BnBqPWUrRhJAQP1IduqyI8kP8nQ2VkCxqRGEIGz9emPbPngJb2v9aYlAPc3MY MLdgfTKnYNUYOIiTxwLkNryOi3Q1+sKb71JQPkXwZQdykUEgrHLDPBak0/AfjB3t w7vPNOjMjGzCscVm6jDcTuJ9qgN1rfAVFu0LHSnk=

I am trying to interoperate between a perfsonar 3.5 node and an Ubuntu VM running owamp (3.4.10) / bwctl (1.5.2)

owamp is working fine, but regular throughput testing is giving the following error:

" 01:27:21 11/30/2015
Error from bwctl/iperf3:
Problem parsing output: malformed JSON string, neither array, object, number, string or atom, at character offset 0 (before "(end of string)") at /opt/perfsonar_ps/regular_testing/bin/../lib/perfSONAR_PS/RegularTesting/Parsers/Iperf3.pm line 54. "

This log appears with a big red dot in the graphs. It doesn't appear in /var/log/perfsonar/regular_testing.log (*)

From the command line (using bwctl) I am able to do throughput tests in both directions.

Now, this error talks about parsing JSON, but I don't know where this JSON would come from. The bwctl manpage says there is a -y <format> option, but not what the options are. It seems to take only a single-character argument.

If I give "-y J" then it tells me that iperf doesn't like this flag, but iperf3 does, and I get JSON in response. Running these on the perfsonar node, both work correctly and give valid JSON:

bwctl -s <remotehost> -y J
bwctl -c <remotehost> -y J

Any more ideas where to look? How can I find out what bwctl command perfsonar is actually issuing?

Thanks,

Brian Candler.

(*) However, regular_testing.log does have a number of errors as shown below. They don't seem to correlate with the error times of the red dots though.

2015/11/30 07:56:23 (21637) ERROR> CmdRunner.pm:114 perfSONAR_PS::RegularTesting::Utils::CmdRunner::run - Problem with results callback: Attribute (tool) does not pass the type constraint because: Validation failed for 'Str' with value undef at /opt/perfsonar_ps/regular_testing/bin/../lib/perfSONAR_PS/RegularTesting/Tests/Bwctl.pm line 119
    perfSONAR_PS::RegularTesting::Tests::Bwctl::__ANON__('perfSONAR_PS::RegularTesting::Tests::Bwctl=HASH(0x4561ee8)', 'HASH(0x45efe28)') called at /usr/lib64/perl5/vendor_perl/Moose/Meta/Method/Overridden.pm line 36
    perfSONAR_PS::RegularTesting::Tests::Bwctl::build_results('perfSONAR_PS::RegularTesting::Tests::Bwctl=HASH(0x4561ee8)', 'HASH(0x45efe28)') called at /opt/perfsonar_ps/regular_testing/bin/../lib/perfSONAR_PS/RegularTesting/Tests/BwctlBase.pm line 237
    perfSONAR_PS::RegularTesting::Tests::BwctlBase::handle_output('perfSONAR_PS::RegularTesting::Tests::Bwctl=HASH(0x4561ee8)', 'HASH(0x45c3378)') called at /opt/perfsonar_ps/regular_testing/bin/../lib/perfSONAR_PS/RegularTesting/Tests/BwctlBase.pm line 180
    perfSONAR_PS::RegularTesting::Tests::BwctlBase::__ANON__('perfSONAR_PS::RegularTesting::Utils::CmdRunner::Cmd=HASH(0x45...', 'HASH(0x45c70d0)') called at /opt/perfsonar_ps/regular_testing/bin/../lib/perfSONAR_PS/RegularTesting/Utils/CmdRunner.pm line 112
    eval {...} called at /opt/perfsonar_ps/regular_testing/bin/../lib/perfSONAR_PS/RegularTesting/Utils/CmdRunner.pm line 111
    perfSONAR_PS::RegularTesting::Utils::CmdRunner::run('perfSONAR_PS::RegularTesting::Utils::CmdRunner=HASH(0x45784d8)') called at /opt/perfsonar_ps/regular_testing/bin/../lib/perfSONAR_PS/RegularTesting/Tests/BwctlBase.pm line 188
    perfSONAR_PS::RegularTesting::Tests::BwctlBase::__ANON__('perfSONAR_PS::RegularTesting::Tests::Bwctl=HASH(0x4561ee8)', 'HASH(0x4572cc0)') called at /usr/lib64/perl5/vendor_perl/Moose/Meta/Method/Overridden.pm line 36
    perfSONAR_PS::RegularTesting::Tests::BwctlBase::run_test('perfSONAR_PS::RegularTesting::Tests::Bwctl=HASH(0x4561ee8)', 'HASH(0x4572cc0)') called at /opt/perfsonar_ps/regular_testing/bin/../lib/perfSONAR_PS/RegularTesting/Test.pm line 75
    perfSONAR_PS::RegularTesting::Test::run_test('perfSONAR_PS::RegularTesting::Test=HASH(0x4554e28)', 'handle_results', 'CODE(0x1274958)') called at /opt/perfsonar_ps/regular_testing/bin/../lib/perfSONAR_PS/RegularTesting/Master/SelfScheduledTestChild.pm line 50
    eval {...} called at /opt/perfsonar_ps/regular_testing/bin/../lib/perfSONAR_PS/RegularTesting/Master/SelfScheduledTestChild.pm line 40
    perfSONAR_PS::RegularTesting::Master::SelfScheduledTestChild::__ANON__('perfSONAR_PS::RegularTesting::Master::SelfScheduledTestChild=...') called at /usr/lib64/perl5/vendor_perl/Moose/Meta/Method/Overridden.pm line 36
    perfSONAR_PS::RegularTesting::Master::SelfScheduledTestChild::child_main_loop('perfSONAR_PS::RegularTesting::Master::SelfScheduledTestChild=...') called at /opt/perfsonar_ps/regular_testing/bin/../lib/perfSONAR_PS/RegularTesting/Master/BaseChild.pm line 32
    perfSONAR_PS::RegularTesting::Master::BaseChild::run('perfSONAR_PS::RegularTesting::Master::SelfScheduledTestChild=...') called at /opt/perfsonar_ps/regular_testing/bin/../lib/perfSONAR_PS/RegularTesting/Master.pm line 182
    perfSONAR_PS::RegularTesting::Master::run('perfSONAR_PS::RegularTesting::Master=HASH(0x453fb00)') called at /opt/perfsonar_ps/regular_testing/bin/daemon line 122




Archive powered by MHonArc 2.6.16.

Top of Page