perfSONAR User Q&A and Other Discussion

[Aaron Brown <>]

Hey Brian,

That error is usually caused by the clocks being too far offset. How far off 
are the two hosts from each other time-wise? Is the VM instance running NTP?

Cheers,
Aaron

On Nov 28, 2014, at 7:05 AM, Brian Candler 
<>
 wrote:

> I have built owampd 3.3 on OSX Mavericks.
> 
> When I try to connect to the OSX owampd using owping from a perfsonar-3.4.1 
> instance (VM), I get the following:
> 
> $ owping 192.168.56.1
> owping: FILE=time.c, LINE=112, NTP: Status UNSYNC (clock offset issues 
> likely)
> owping: FILE=time.c, LINE=118, NTP: STA_NANO should be set. Make sure ntpd 
> is running, and your NTP configuration is good.
> Approximately 13.2 seconds until results available
> owping: FILE=api.c, LINE=1097, _OWPCleanDataRecs: Invalid data record 
> (seq_no too large) sid(c0a83806d822e0c6d39b994e9e3c10f9)
> owping: FILE=api.c, LINE=1245, _OWPCleanDataRecs: Failed
> owping: FILE=protocol.c, LINE=2291, _OWPReadStopSessions: Unable to clean 
> data sid(c0a83806d822e0c6d39b994e9e3c10f9): Function not implemented
> owping: FILE=protocol.c, LINE=2453, _OWPReadStopSessions: Failed
> owping: FILE=owping.c, LINE=1777, Test session(s) Failed...
> 
> I applied the patch from 
> https://lists.internet2.edu/sympa/arc/perfsonar-user/2014-11/msg00131.html 
> and it didn't make any difference.
> 
> Using the OSX owping to talk to its own owampd is fine.
> 
> Any ideas?
> 
> Thanks,
> 
> Brian.
>