[perfsonar-user] OSX error: Invalid data record (seq

Discussion:

[perfsonar-user] OSX error: Invalid data record (seq_no too large)

Brian Candler

2014-11-28 12:05:10 UTC

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.

Jason Zurawski

2014-12-01 12:46:59 UTC

Permalink

Hi Brian;

Another use reported this problem a couple of days ago, Aaron prepared a patch that is described in this thread:

https://lists.internet2.edu/sympa/arc/perfsonar-user/2014-11/msg00135.html

Let us know if this helps, if not we can debug further.

Thanks;

-jason

Post by Brian Candler
I have built owampd 3.3 on OSX Mavericks.
$ 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.

Brian Candler

2014-12-01 13:48:28 UTC

Permalink

Post by Jason Zurawski
https://lists.internet2.edu/sympa/arc/perfsonar-user/2014-11/msg00135.html

I already applied that patch and it didn't make a difference.

Aside: I built via homebrew, and I did the patch that way too (see
below). When I "brew reinstall owamp" I see a message saying the patch
is being applied, so I'm fairly confident it's being used.

Regards,

Brian.

$ git diff
diff --git a/Library/Formula/owamp.rb b/Library/Formula/owamp.rb
index eff3998..903e6cc 100644
--- a/Library/Formula/owamp.rb
+++ b/Library/Formula/owamp.rb
@@ -5,6 +5,12 @@ class Owamp < Formula
url 'http://software.internet2.edu/sources/owamp/owamp-3.3.tar.gz'
sha1 'ac3b77294ee30d41924b01fc009de0b2605a753c'

+ #
https://lists.internet2.edu/sympa/arc/perfsonar-user/2014-11/msg00131.html
+ patch :p1 do
+ url "http://ndb1.internet2.edu/~aaron/owamp_time_fix.patch"
+ sha1 "9e5588d57b357f438ae1a785a713f0deaea5a5ba"
+ end
+
def install
system "./configure", "--disable-debug",
"--disable-dependency-tracking",

Aaron Brown

2014-12-01 13:05:33 UTC

Permalink

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

Brian Candler

2014-12-01 13:46:36 UTC

Permalink

Post by Aaron Brown
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?

If I run "date" on both boxes they seem to be within a second of each other.

The VM is perfsonar running inside VirtualBox inside my laptop. The OSX
instance is my laptop itself.

On Perfsonar VM:

$ ntpq -p
remote refid st t when poll reach delay offset
jitter
==============================================================================
www.bhay.org 145.238.203.14 2 u 60 64 3 6.003 -1.878
0.492
*golem.canonical 131.188.3.220 2 u 26 64 1 6.554 0.065 1.296

On OSX:

$ ntpq -p
remote refid st t when poll reach delay offset
jitter
==============================================================================
time.euro.apple 17.72.133.55 2 u 253m 512 1 164.282 6.436 917.154

(hmm, no asterisk, is that in sync? If not, why not?)

Regards,

Brian.

Brian Candler

2014-12-01 14:53:55 UTC

Permalink

OK, I just tried again and it's working now. It's clear the clocks are
~440ms out of sync. Maybe the time difference was higher previously.

Regards,

Brian.

From OSX to Perfsonar:

$ date; time owping 192.168.56.6
Mon 1 Dec 2014 14:51:59 GMT
owping: FILE=time.c, LINE=124, NTP syscalls unavail: Status UNSYNC
(clock offset issues likely)
Approximately 12.9 seconds until results available

--- owping statistics from [Brians-MacBook-Air.local]:50754 to
[192.168.56.6]:8841 ---
SID: c0a83806d826ff0f7202009cc92f80b7
first: 2014-12-01T14:52:00.953
last: 2014-12-01T14:52:11.321
100 sent, 0 lost (0.000%), 0 duplicates
one-way delay min/median/max = -439/-438/-437 ms, (unsync)
one-way jitter = 0.4 ms (P95-P50)
TTL not reported
no reordering

--- owping statistics from [192.168.56.6]:9313 to
[Brians-MacBook-Air.local]:60233 ---
SID: c0a83801d826ff0fe328e92d9a7f8114
first: 2014-12-01T14:52:00.982
last: 2014-12-01T14:52:10.457
100 sent, 0 lost (0.000%), 0 duplicates
one-way delay min/median/max = 438/439/439 ms, (unsync)
one-way jitter = 0.5 ms (P95-P50)
TTL not reported
no reordering

real 0m14.197s
user 0m0.008s
sys 0m0.030s

From perfsonar to OSX:

$ owping 192.168.56.1
Approximately 13.2 seconds until results available

--- owping statistics from [perfsonar1.ws.nsrc.org]:8914 to
[192.168.56.1]:9819 ---
SID: c0a83801d826fe9c426bb55a9a4ee77e
first: 2014-12-01T14:50:05.004
last: 2014-12-01T14:50:15.106
100 sent, 0 lost (0.000%), 0 duplicates
one-way delay min/median/max = 436/436/437 ms, (unsync)
one-way jitter = 0.4 ms (P95-P50)
TTL not reported
no reordering

--- owping statistics from [192.168.56.1]:9043 to
[perfsonar1.ws.nsrc.org]:8770 ---
SID: c0a83806d826fe9bd4e052438f763817
first: 2014-12-01T14:50:05.055
last: 2014-12-01T14:50:15.805
100 sent, 0 lost (0.000%), 0 duplicates
one-way delay min/median/max = -436/-435/-434 ms, (unsync)
one-way jitter = 0.4 ms (P95-P50)
TTL not reported
no reordering