Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] tests don't produce graph

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] tests don't produce graph


Chronological Thread 
  • From: Pete Siemsen <>
  • To:
  • Cc:
  • Subject: Re: [perfsonar-user] tests don't produce graph
  • Date: Mon, 22 Oct 2018 14:10:57 -0600
  • Ironport-phdr: 9a23:rz7jJxIXjGyv5Mgr/dmcpTZWNBhigK39O0sv0rFitYgeL/jxwZ3uMQTl6Ol3ixeRBMOHs60C07KempujcFRI2YyGvnEGfc4EfD4+ouJSoTYdBtWYA1bwNv/gYn9yNs1DUFh44yPzahANS47xaFLIv3K98yMZFAnhOgppPOT1HZPZg9iq2+yo9JDffwdFiCChbb9uMR67sRjfus4KjIV4N60/0AHJonxGe+RXwWNnO1eelAvi68mz4ZBu7T1et+ou+MBcX6r6eb84TaFDAzQ9L281/szrugLdQgaJ+3ART38ZkhtMAwjC8RH6QpL8uTb0u+ZhxCWXO9D9QLYpUjqg8qhrUgflhygJNzE78G/ZhM9+gr9Frh29vBFw2ZLYbZuPOfZiYq/Qf9UXTndBUMZLUCxBB5uxYZERAOodI+lTspTzp1oQohu7HgmjGuXvwSJPi3/t3K01zeEhERrY0wwmBN8OrWjbo8/vNKsIT++60bTIwCzFYvhL1zn9743IfQogofGKRb9wcMzRyVUxGAPfiFWft5DlMy2P2usTrmeb8uxtXv+shW4/swx9vCKgytswhoTMm44YxVDJ+Tl8zYs6JtC1SUF2bNu6HJdMsiyXMoV7T80sTmxupS000KcJuYShcygP0JknxwDQa/iAc4WQ5xLsTueRITNhiHNrfbKzmg++8Eeux+DyWMS4yllKri1CktnDsnACyQbf5dSASvt45kuh2DCP2B7P6uxcP0w7j7bXJ4Ikz7ItmZcesVjPEyr5lUj1jaKbeUAp9va05+niZ7jrqJGROoFshgH7KKsum8i/AeoiMggJWmiW4f+81Lz98k38W7VFkPs2n7LEsJ/GP8sbvLS1DBFI3YY+8xq/FSup0MwEnXkbK1JIYAqHgJbzO1HAO/D4CvG/jE62kDty2vDGJaPuAo/WI3jHkbfhZqp961VCxAYpzNBf4Y5UBa8bIPL1REDxqMLUAgUnPAOp3ua0QOh7zZ4UDGKTHreCYuSVtV6T+vlpIu+QaZUTtSqnbfUp+rn1nHohkBgGfKav2pUZL2i1BPp9JEOQez/xmdobQlsN6wM4UOvrjlDEXTNXeX+vT4o57zd9EIW0C47FAJip05Kb2yLuJpBKayh9C12JCnruP9GfWvoJcy+UCtJqmyZCWLS8HdxynSqyvRP3nuI0ZtHf/TcV4Mru

Thank you!

When I run "pscheduler schedule" I see this, among many others:

2018-10-14T21:16:53Z - 2018-10-15T21:16:53Z  (Running)
latencybg --data-ports 8760-9960 --source-node 158.142.6.250 --dest 129.19.165.2
  --flip --dest-node 129.19.165.2 --source 158.142.6.250 --ip-version 4 (Run with tool 'powstream')

When I run "pscheduler monitor" I see this line among others:

2018-10-14T21:16:53Z  Running      latencybg --data-ports 8760-9960 --source-node 158.142.6.250 --dest 129.19.165.2 --flip --dest-node 129.19.165.2 --source 158.142.6.250 --ip-version 4

So it looks the the first thing you mentioned is good.

I found lots of these in  /var/log/pscheduler/pscheduler.log:

Oct 22 14:08:27 perfsonar-1850 journal: archiver WARNING  7029379: Failed to archive https://localhost/pscheduler/tasks/e2e5651e-1c8f-419a-a6d1-d41903914786/runs/80485939-a892-41f4-a20c-aa3947fa594e to esmond: Archiver permanently abandoned registering test after 1 attempt(s): 401: Authentication credentials were not provided.

I'm running perfsonar 4.0.2 on Centos 7.

-- Pete



On Sat, Oct 13, 2018 at 6:40 AM Antoine Delvaux <> wrote:
Hello Pete,

The first thing to do is to double check the test is actually part of the pscheduler schedule.  You can run `pscheduler schedule` or `pscheduler monitor` to be sure and you should see latencybg tests running. You should also have some powstream processes running on your machine. 

Next you should check if the results of the tests are posted to the local archive.  There are different ways to do that:
  • looking at one of the run URL of a past test (check `pscheduler schedule -PT1H` or similar)
  • looking at the httpd/apache logs to see if you see PUT requests coming in 
  • checking the /esmond/perfsonar/archive URL on your toolkit deployment
It can also be worth checking the /var/log/esmond/django.log esmond.log and /var/log/pscheduler/pscheduler.log file for any errors. 

Also, which version of perfSONAR are you running and on which platform?

Cheers,

Antoine. 

Le 12 oct. 2018 à 23:21, Pete Siemsen <> a écrit :

This is so basic I'm embarrassed to ask. I defined a test a few days ago. I expect to see a graph on the perfsonar home page, but I don't have one. I've attached a screenshot of the test. I can ping the target. How do I troubleshoot this? Perhaps looking in log files?

-- Pete

<Screen Shot 2018-10-12 at 5.19.50 PM.png>--
To unsubscribe from this list: https://lists.internet2.edu/sympa/signoff/perfsonar-user




Archive powered by MHonArc 2.6.19.

Top of Page