Skip to Content.
Sympa Menu

perfsonar-user - [perfsonar-user] Test results on test host web, but not on Maddash dashboard

Subject: perfSONAR User Q&A and Other Discussion

List archive

[perfsonar-user] Test results on test host web, but not on Maddash dashboard


Chronological Thread 
  • From: Johann Hugo <>
  • To:
  • Subject: [perfsonar-user] Test results on test host web, but not on Maddash dashboard
  • Date: Tue, 8 Oct 2019 12:20:50 +0200

Hi all

After rebuilding both cassandra + postgresql databases, I only get test results on the test host, but not on our central Maddash dashboard any more.

On the test node, psconfig is reading the remote configuration, "pscheduler monitor" shows all the tests that are running. Test results are showing on the web interface on the node itself.

From ssl_access_log on my CM server I can see the results coming from the test node.
(esmond)[root@perf-cm esmond]# tail -F /var/log/httpd/ssl_access_log | grep 155.232.40.215
155.232.40.215 - - [08/Oct/2019:12:05:39 +0200] "PUT /esmond/perfsonar/archive/7f51686d74d147689ad29f7c9ab43822/? HTTP/1.1" 201 2
155.232.40.215 - - [08/Oct/2019:12:05:45 +0200] "PUT /esmond/perfsonar/archive/318a362cb64342e6a182eb964ad77e8b/? HTTP/1.1" 201 2

From time to time I see this WARNING message in pscheduler.log on the test node:
[root@ps-19-cpt-teraco ~]# tail -F /var/log/pscheduler/pscheduler.log
Oct  8 12:14:07 ps-19-cpt-teraco journal: runner INFO     286650: Posted result to https://ps-19-cpt-teraco-1g.perfsonar.ac.za/pscheduler/tasks/5de48f93-077b-4408-840a-3782d7208649/runs/f7df3b89-3f65-44b6-8fa7-a8db8d72944c
Oct  8 12:14:09 ps-19-cpt-teraco journal: archiver WARNING  500449: Failed to archive https://ps-19-cpt-teraco-1g.perfsonar.ac.za/pscheduler/tasks/5e76c9f7-df28-451a-a152-bc0038e59053/runs/6f5ce2f0-8c76-4f7b-af19-1fde20bfe82c to esmond: Archiver permanently abandoned registering test after 3 attempt(s): 401: Authentication credentials were not provided.
Oct  8 12:14:09 ps-19-cpt-teraco journal: archiver WARNING  500449: Gave up archiving https://ps-19-cpt-teraco-1g.perfsonar.ac.za/pscheduler/tasks/5e76c9f7-df28-451a-a152-bc0038e59053/runs/6f5ce2f0-8c76-4f7b-af19-1fde20bfe82c to esmond
Oct  8 12:14:09 ps-19-cpt-teraco journal: runner INFO     287093: Posted result to https://ps-19-cpt-teraco-10g.perfsonar.ac.za/pscheduler/tasks/b1a2d5a5-3302-477b-9961-cf0ec8832928/runs/50dd3fe3-31a3-4973-a225-3261b8e48d37
Oct  8 12:14:09 ps-19-cpt-teraco journal: runner INFO     287072: Posted result to https://ps-19-cpt-teraco-10g.perfsonar.ac.za/pscheduler/tasks/d3f4f8cb-1702-468a-8c6e-298eccaf683a/runs/51423c80-2403-4562-9812-de73d7a17024
Oct  8 12:14:12 ps-19-cpt-teraco journal: runner INFO     291704: Running https://ps-19-cpt-teraco-1g.perfsonar.ac.za/pscheduler/tasks/eac31773-e167-46e7-b95d-13daf0a55f47/runs/cdca37ae-bccf-4e3d-939e-365102ce2723
Oct  8 12:14:12 ps-19-cpt-teraco journal: runner INFO     291704: With traceroute: trace --dest web100.pnw-gigapop.net --length 40 --probe-type udp --source ps-19-cpt-teraco-1g.perfsonar.ac.za --source-node ps-19-cpt-teraco-1g.perfsonar.ac.za --hops 64 --wait PT30S

Any ideas on how to fix this ?

Regards
Johann



Archive powered by MHonArc 2.6.19.

Top of Page