perfSONAR User Q&A and Other Discussion

["Roderick Mooi" <>]

Hi Chris

I haven't had more feedback from Aaron or others yet. I also don't know what 
the problem is. We aren't even using the mesh config on this node but you 
might be onto something. In any case, we've scheduled this node for a 
re-install - I hope I don't get the same results as you this time (I'll pay 
attention when installing and see if/when it goes wrong to hopefully identify 
the cause)...

Cheers,

Roderick

>>> On 2013-09-16 at 15:38, "Christopher J. Walker" 
>>> <>
>>>  wrote:
> On 01/08/13 11:52, Roderick Mooi wrote:
>> Hi Aaron
>> 
>> I started having the same problem on one of my other 3.3. hosts. When I 
> scheduled a new test and saved, the bwctl processes for the other tests 
> didn't come back. Then I changed the test frequency on the old tests and 
> the 
> new one and saved again. This time no bwctl processes appeared. Rebooting 
> the 
> host made no difference.
>> 
>> I then deleted all throughput tests, saved and re-created them 
>> individually. 
> Then saved. Now the bwctl processes are back...
>> 
>> The owmesh.conf file on the other, non working, host looks different to 
>> the 
> version on my other hosts which is what is causing the problems I think - 
> e.g. 
> missing: BWDataDir. (It doesn't start with "16Jul2009 SayWhatAgainIDareYou" 
> like the files on the working hosts do). What is the best way to 
> reset/restore it?
>> 
> 
> I also have this problem having just installed perfsonar 3.3.1.
> 
> Was there a solution?
> 
> 
> It looks like the problem is that the mesh config
> 
>       sudo -u perfsonar /opt/perfsonar_ps/mesh_config
>       /bin/generate_configuration
> 
> generates
>         /opt/perfsonar_ps/perfsonarbuoy_ma/etc/owmesh.conf and this
> doesn't contain a variable BWDataDir
> 
> The host was completely reinstalled from scratch using the 3.3.1 netinst
> iso
> 
> Chris
> 
>> Thanks!
>> 
>> Regards,
>> 
>> Roderick
>> 
>>>>> On 2013-07-30 at 08:29, "Roderick Mooi" 
>>>>> <>
>>>>>  wrote:
>>> Hi Aaron
>>>
>>> [root@perfsonar8
>>>  ~]# /etc/init.d/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
>>>
>>> [root@perfsonar8
>>>  ~]# /etc/init.d/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
>>>
>>> Clearly there is a problem above - if you can tell me where to look or 
>>> how to 
> 
>>> fix it I'd appreciate it.
>>>
>>> The output of "ps auxw" is attached. Note that this node currently has 
>>> Throughput tests scheduled. Also, I didn't set up this node so perhaps 
>>> something went wrong during installation that I'm not aware of... 
>>>
>>> Thanks!
>>>
>>> Roderick
>>>
>>>>>> On 2013-07-29 at 14:54, Aaron Brown 
>>>>>> <>
>>>>>>  wrote:
>>>> Hey Roderick,
>>>>
>>>> When you run "/etc/init.d/perfsonarbuoy_owp_master start", what's the 
>>>> output? Same deal with "/etc/init.d/perfsonarbuoy_bw_master start". 
>>>> Also, 
>>>> could you send the output of "ps auxw"?
>>>>
>>>> Cheers,
>>>> Aaron
>>>>
>>>> On Jul 25, 2013, at 10:18 AM, Roderick Mooi 
>>>> <>
>>>>  wrote:
>>>>
>>>>> Good day
>>>>>
>>>>> I am scheduling tests on a 3.3. host but not getting any results (my 
>>>>> other 
>>>> 3.3. hosts are working fine including testing to this host :-/ & manual 
>>>> tests 
>>>> work on this host without issues). When I looked closer I saw that no 
>>>> powstream processes are being started (for one-way delay tests) and when 
>>>> adding throughput tests no bwctl processes are started. Ping and 
>>>> traceroute 
>>>> tests appear to work. I don't see any clear errors in the logs (just 
>>>> bwctl 
>>>> extracts - trying to get that working first):
>>>>>
>>>>> ...
>>>>> Jul 25 13:55:27 perfsonar8 bwctld[5258]: FILE=sapi.c, LINE=353, 
>>>>> Connection 
>>>> to (<my IP>:4823) from (<my IP>:39254)
>>>>> Jul 25 13:55:27 perfsonar8 bwctld[5258]: FILE=sapi.c, LINE=391, 
>>>> BWLControlAccept(): Unable to read ClientGreeting message
>>>>> Jul 25 14:03:50 perfsonar8 bwctld[2726]: FILE=bwctld.c, LINE=2336, 
>>>>> bwctld: 
>>>> exiting...
>>>>> Jul 25 14:03:50 perfsonar8 bwctld[2726]: FILE=bwctld.c, LINE=2390, 
>>>>> bwctld: 
>>>> exited.
>>>>> Jul 25 14:04:00 perfsonar8 bwctld[5570]: FILE=tools.c, LINE=301, 
>>>>> Compiled-in 
>>>> tools: iperf nuttcp 
>>>>> Jul 25 14:04:00 perfsonar8 bwctld[5570]: FILE=iperf.c, LINE=80, 
>>>> IperfAvailable(): iperf_cmd unset, using "iperf"
>>>>> Jul 25 14:04:00 perfsonar8 bwctld[5570]: FILE=nuttcp.c, LINE=81, 
>>>> NuttcpAvailable(): nuttcp_cmd unset, using "nuttcp"
>>>>> Jul 25 14:04:00 perfsonar8 bwctld[5570]: FILE=tools.c, LINE=321, 
>>>>> Available 
>>>> tools: iperf nuttcp 
>>>>> Jul 25 14:55:33 perfsonar8 bwctld[6047]: FILE=sapi.c, LINE=353, 
>>>>> Connection 
>>>> to (<my IP>:4823) from (<my IP>:40587)
>>>>> Jul 25 14:55:33 perfsonar8 bwctld[6047]: FILE=sapi.c, LINE=391, 
>>>> BWLControlAccept(): Unable to read ClientGreeting message
>>>>> ...
>>>>>
>>>>> Any help is appreciated? Thanks!
>>>>>
>>>>> Roderick
>>>>>
>>>>>
>>>>>
>>>>> -- 
>>>>> This message is subject to the CSIR's copyright terms and conditions, 
>>>>> e-mail 
>>>> legal notice, and implemented Open Document Format (ODF) standard. 
>>>>> The full disclaimer details can be found at 
>>>> http://www.csir.co.za/disclaimer.html.
>>>>>
>>>>> This message has been scanned for viruses and dangerous content by 
>>>> MailScanner, 
>>>>> and is believed to be clean.
>>>>>
>>>>> Please consider the environment before printing this email.
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> -- 
>>>> This message is subject to the CSIR's copyright terms and conditions, 
>>>> e-mail 
>>>> legal notice, and implemented Open Document Format (ODF) standard. 
>>>> The full disclaimer details can be found at 
>>>> http://www.csir.co.za/disclaimer.html.
>>>>
>>>> This message has been scanned for viruses and dangerous content by 
>>>> MailScanner, 
>>>> and is believed to be clean.
>>>>
>>>> Please consider the environment before printing this email.
>>>
>>>
>>> -- 
>>> This message is subject to the CSIR's copyright terms and conditions, 
>>> e-mail 
>>> legal notice, and implemented Open Document Format (ODF) standard. 
>>> The full disclaimer details can be found at 
>>> http://www.csir.co.za/disclaimer.html.
>>>
>>> This message has been scanned for viruses and dangerous content by 
>>> MailScanner, 
>>> and is believed to be clean.
>>>
>>> Please consider the environment before printing this email.
>> 
> 
> 
> -- 
> This message is subject to the CSIR's copyright terms and conditions, 
> e-mail 
> legal notice, and implemented Open Document Format (ODF) standard. 
> The full disclaimer details can be found at 
> http://www.csir.co.za/disclaimer.html.
> 
> This message has been scanned for viruses and dangerous content by 
> MailScanner, 
> and is believed to be clean.
> 
> Please consider the environment before printing this email.

-- 
This message is subject to the CSIR's copyright terms and conditions, e-mail 
legal notice, and implemented Open Document Format (ODF) standard. 
The full disclaimer details can be found at 
http://www.csir.co.za/disclaimer.html.

This message has been scanned for viruses and dangerous content by 
MailScanner, 
and is believed to be clean.

Please consider the environment before printing this email.