Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Bandwidth system failing to run some tests

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Bandwidth system failing to run some tests


Chronological Thread 
  • From: Sowmya Balasubramanian <>
  • To: Trey Dockendorf <>
  • Cc: perfsonar-user <>
  • Subject: Re: [perfsonar-user] Bandwidth system failing to run some tests
  • Date: Mon, 3 Aug 2015 13:32:13 -0700

Hi Trey,

Was the test working at some point? 

Can you try running a test from the command line from your host to the other host and send the results?

There is a possibility that the firewall rules or BWCTL limits on the other side is preventing your host from running the test.

Thanks,
Sowmya

On Mon, Aug 3, 2015 at 10:17 AM, Trey Dockendorf <> wrote:
I just discovered my bandwidth testing host is failing to run some of the configured tests.  I'm seeing errors like this in /var/log/perfsonar/regular_testing.log

2015/08/03 11:57:35 (21746) ERROR> MeasurementArchiveChild.pm:125 perfSONAR_PS::RegularTesting::Master::MeasurementArchiveChild::__ANON__ - Problem handling test results: Problem storing results: Error writing metadata: Error running test to psonar3.fnal.gov  with output bwctl: star
t_endpoint: 3634164453.980392

Attached is my regular_testing.log


The tests I was hoping to look at were against psonar3.fnal.gov.  I've noticed other tests are missing data too like tests to tx-learn.net hosts.  Tests to psnr-bw01.slac.stanford.edu is one that shows data but with lots of "red dots" at the top of the graphs.

I saw some mention of NTP problems in the logs so I forced NTP server updates via interface hoping to get closer NTP servers used.

# ntpq -p -c rv
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
-nms-rlat.chic.n 141.142.143.138  2 u   11   64  377   24.055   -3.209   0.407
*nms-rlat.hous.n .IRIG.           1 u    6   64  377   18.186    1.227   0.230
-nms-rlat.salt.n 128.138.140.44   2 u   65   64  377   33.024   -4.304   0.435
+time2.chpc.utah 198.60.22.240    2 u    8   64  377   34.591   -2.486   0.335
+time3.chpc.utah 198.60.22.240    2 u    2   64  377   34.534   -2.771   0.219
associd=0 status=0615 leap_none, sync_ntp, 1 event, clock_sync,
version="ntpd Mon Mar 16 14:53:03 UTC 2015 (1)",
processor="x86_64", system="Linux/2.6.32-504.30.3.el6.web100.x86_64",
leap=00, stratum=2, precision=-24, rootdelay=18.186, rootdisp=18.007,
refid=64.57.16.162,
reftime=d96a2001.60695f02  Mon, Aug  3 2015 12:14:41.376,
clock=d96a2090.760490a5  Mon, Aug  3 2015 12:17:04.461, peer=21380, tc=6,
mintc=3, offset=-0.105, frequency=41.314, sys_jitter=2.330,
clk_jitter=1.141, clk_wander=0.151

# ntpstat
synchronised to NTP server (64.57.16.162) at stratum 2
   time correct to within 27 ms
   polling server every 64 s

Let me know what other information would be useful to debug this.

Thanks,
- Trey

=============================

Trey Dockendorf 
Systems Analyst I 
Texas A&M University 
Academy for Advanced Telecommunications and Learning Technologies 
Phone: (979)458-2396 
Email:  
Jabber:




Archive powered by MHonArc 2.6.16.

Top of Page