perfSONAR User Q&A and Other Discussion

[Jason Zurawski <>]

Hi Amjad;

I looked at the owmesh you sent to the list on Nov. 20th, and it appears you 
have a test configured for a single host:

> <NODE=SDN_12_10G_DSCR_DUKE_LOCAL-0>
> BW4ADDR sdn-12-10g.dscr.duke.local:4823
> CONTACTADDR     sdn-12-10g.dscr.duke.local
> LONGNAME        1
> NOAGENT 1
> </NODE>

If we look at the name specified in the 'CONTACTADDR' field, it doesn't 
resolve for me personally, does it resolve for you?  What do you see if you 
do something like this:

> [zurawski@poteen
>  ~]$ nslookup sdn-12-10g.dscr.duke.local
> Server:               192.168.1.1
> Address:      192.168.1.1#53
> 
> ** server can't find sdn-12-10g.dscr.duke.local: NXDOMAIN

If you can can't use IP connectivity to reach this host (or other hosts that 
can't be resolved), you won't see tests succeed.  I would recommend trying to 
set up tests to other hosts that do have a public facing address to help you 
verify that your node is functioning properly.  

Thanks;

-jason

On Nov 27, 2013, at 3:30 PM, Md. Amjad Hossain 
<>
 wrote:

> Hi 
> 
> still I am not getting any data for bwctl test. Last time I waited to let 
> bwctld to run automatically.  I have checked bwctl database. There is only 
> one table DATES but no data.
> 
> please help me to solve the problem.
> 
> Regards,
> Amjad
> 
> 
> On Tue, Nov 26, 2013 at 10:35 AM, Md. Amjad Hossain 
> <>
>  wrote:
> Hello Andy,
> 
> Good Morning.
> 
> After 8 hours still no data. I ran bwctld by command. Should I let it run 
> automatically?
> 
> Please find the log file in the attachment. 
> 
> Thanks
> Amjad
> 
> 
> On Tue, Nov 26, 2013 at 9:18 AM, Andy Lake 
> <>
>  wrote:
> Hi,
> 
> You may just need to wait some time. After you reboot BWCTL may not start 
> right away as it waits for NTP to converge. This is expected behavior. 
> Within an hour or so bwctld should start on its own. After that it may take 
> several hours for your tests to collect its first data. If you still don't 
> have any data this morning, can you share 
> /var/log/perfsonar/owamp_bwctl.log?
> 
> Thanks,
> Andy
> 
> 
> On Nov 25, 2013, at 11:10 PM, Md. Amjad Hossain 
> <>
>  wrote:
> 
>> Thanks Andy,
>> 
>> I have setup the Perfsonar toolkit again. May be there were some problem 
>> in previous installation. Now both of the testing tools running. I have 
>> test OWAMP, its working. But I am facing problem with BWCTL test.  I have 
>> scheduled for BWCTL test but it is not showing any data in "Service Graphs 
>> -> Throughput" page. Could please help me with this problem.
>> 
>> 
>> For your understanding,
>> 
>> I have observed that after rebooting the system " Bandwidth Test 
>> Controller (BWCTL)" is not running. I refreshed the browser several times 
>> but still was not running. Then I ran it using the command:  /etc/init.d/ 
>> service bwctld start . After running this command its shows followings: 
>> 
>> 
>> [root@dhcp39-88
>>  init.d]# service bwctld start
>> /usr/bin/bwctld -c /etc/bwctld -R /var/run
>> bwctld[2671]: FILE=tools.c, LINE=319, Compiled-in tools: iperf nuttcp 
>> iperf3
>> bwctld[2671]: FILE=iperf.c, LINE=80, IperfAvailable(): iperf_cmd unset, 
>> using "iperf"
>> bwctld[2671]: FILE=nuttcp.c, LINE=81, NuttcpAvailable(): nuttcp_cmd unset, 
>> using "nuttcp"
>> bwctld[2671]: FILE=tools.c, LINE=339, Available tools: iperf nuttcp iperf3
>> /etc/init.d/bwctld start: bwctld started
>> [root@dhcp39-88
>>  init.d]#
>> 
>> 
>> Do you see any problem in the above output? 
>> 
>> Please help me to solve this problem.
>> 
>> Thanks
>> Amjad
>> 
>> 
>> 
>> 
>> 
>> 
>> On Mon, Nov 25, 2013 at 9:44 AM, Andy Lake 
>> <>
>>  wrote:
>> Hi,
>> 
>> Thank you. I am not sure how your owmesh file got in the state where its 
>> missing parameters like the DataDir. Can you try running the following to 
>> reset your owmesh file?
>>      rm /opt/perfsonar_ps/perfsonarbuoy_ma/etc/owmesh.conf
>>      yum reinstall perl-perfSONAR_PS-perfSONARBUOY-config
>>         
>> /opt/perfsonar_ps/toolkit/scripts/upgrade/upgrade_owmesh_traceroute.sh
>>         chmod o+r /opt/perfsonar_ps/perfsonarbuoy_ma/etc/owmesh.conf
>>         reboot
>> 
>> After the host reboots add back your tests via the GUI. That should 
>> hopefully get things back to a normal state. 
>> 
>> Thanks,
>> Andy
>> 
>> On Nov 22, 2013, at 5:03 PM, Md. Amjad Hossain 
>> <>
>>  wrote:
>> 
>>> 
>>> Yes, I am scheduling tests using GUI on toolkit ( 
>>> https://.../toolkit/admin/regular_testing/). I have also run bwctl by 
>>> hand as follows,
>>> 
>>> 
>>> [root@dhcp39-88
>>>  ~]# bwctl -s nrel-pt1.es.net
>>> bwctl: Using tool: iperf
>>> bwctl: 26 seconds until test results available
>>> 
>>> RECEIVER START
>>> bwctl: exec_line: iperf -B kahuku.medianet.cs.kent.edu -s -f b -m -p 5548 
>>> -t 10
>>> bwctl: start_tool: 3594146020.046475
>>> ------------------------------------------------------------
>>> Server listening on TCP port 5548
>>> Binding to local address kahuku.medianet.cs.kent.edu
>>> TCP window size: 87380 Byte (default)
>>> ------------------------------------------------------------
>>> [ 15] local 131.123.39.85 port 5548 connected with 198.129.254.162 port 
>>> 5548
>>> [ ID] Interval       Transfer     Bandwidth
>>> [ 15]  0.0-12.4 sec  94896128 Bytes  61462940 bits/sec
>>> [ 15] MSS size 8948 bytes (MTU 8988 bytes, unknown interface)
>>> bwctl: stop_exec: 3594146044.332582
>>> 
>>> RECEIVER END
>>> 
>>> 
>>> [root@dhcp39-88
>>>  ~]# bwctl -c nrel-pt1.es.net
>>> bwctl: Using tool: iperf
>>> bwctl: 26 seconds until test results available
>>> 
>>> RECEIVER START
>>> bwctl: exec_line: /usr/bin/iperf -B 198.129.254.162 -s -f b -m -p 5001 -t 
>>> 10
>>> bwctl: start_tool: 3594146063.374125
>>> ------------------------------------------------------------
>>> Server listening on TCP port 5001
>>> Binding to local address 198.129.254.162
>>> TCP window size: 87380 Byte (default)
>>> ------------------------------------------------------------
>>> [ 15] local 198.129.254.162 port 5001 connected with 131.123.39.85 port 
>>> 5001
>>> [ ID] Interval       Transfer     Bandwidth
>>> [ 15]  0.0-11.0 sec  92930048 Bytes  67816732 bits/sec
>>> [ 15] MSS size 1448 bytes (MTU 1500 bytes, ethernet)
>>> bwctl: stop_exec: 3594146087.580142
>>> 
>>> RECEIVER END
>>> 
>>> 
>>> As I have mentioned one version of owmesh.conf file is after scheduling 
>>> bwctl test and another one before scheduling the test.
>>> 
>>> 
>>> Thanks
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On Fri, Nov 22, 2013 at 4:04 PM, Andy Lake 
>>> <>
>>>  wrote:
>>> Hi,
>>> 
>>> How are you configuring your tests? Are you using the regular testing GUI 
>>> on the toolkit or are you doing things by hand?  Also, why are there two 
>>> versions of your owmesh file?
>>> 
>>> Thanks,
>>> Andy
>>> 
>>> 
>>> On Nov 22, 2013, at 3:42 PM, Md. Amjad Hossain 
>>> <>
>>>  wrote:
>>> 
>>>> Hi,
>>>> 
>>>> My perfsonar still is not running perfSONAR-BUOY Regular Testing 
>>>> (Throughput and One-way Latency).
>>>> 
>>>>  Please help me to solve the problem.
>>>> 
>>>> Regards
>>>> Amjad
>>>> 
>>>> 
>>>> 
>>>> 
>>>> On Wed, Nov 20, 2013 at 10:02 AM, Md. Amjad Hossain 
>>>> <>
>>>>  wrote:
>>>> Hello,
>>>> 
>>>> Here is the two version of my owmesh.conf file
>>>> 
>>>> 
>>>> Thanks
>>>> Amjad
>>>> 
>>>> 
>>>> On Wed, Nov 20, 2013 at 8:36 AM, Andy Lake 
>>>> <>
>>>>  wrote:
>>>> Hi,
>>>> 
>>>> Can you send /opt/perfsonar_ps/perfsonarbuoy_ma/etc/owmesh.conf?
>>>> 
>>>> Thanks,
>>>> Andy
>>>> 
>>>> 
>>>> On Nov 19, 2013, at 10:50 PM, 
>>>> 
>>>>  wrote:
>>>> 
>>>> > HI,
>>>> >
>>>> > My perfsonar is experiencing problems in starting the perfSONAR-BUOY
>>>> > Regular Testing Throughput and One-Way Latency services.
>>>> > I tried the following, receiving errors:
>>>> >
>>>> > cd /etc/init.d/
>>>> > $> service perfsonarbuoy_bw_master start
>>>> > Conf::must_get_val(ATTR=>DataDir, TYPE=>BW, ) undefined, called
>>>> > from /opt/perfsonar_ps/perfsonarbuoy_ma/bin/bwmaster.pl:165
>>>> > Couldn't start perfSONAR-BUOY BWCTL Measurement Service
>>>> >
>>>> > $> service perfsonarbuoy_owp_master start
>>>> > Conf::must_get_val(ATTR=>DataDir, TYPE=>OWP, ) undefined, called
>>>> > from /opt/perfsonar_ps/perfsonarbuoy_ma/bin/powmaster.pl:158
>>>> > Couldn't start perfSONAR-BUOY OWAMP Measurement Service
>>>> >
>>>> > Also, sometimes Traceroute Reqular Testing is not running.
>>>> >
>>>> > Any solution please?
>>>> >
>>>> >
>>>> > - Amjad