perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi,

The host archives test results to esmond using an API key and looks like maybe that API key is out of sync. Try running the following which should set it correctly:

/usr/lib/perfsonar/scripts/system_environment/configure_esmond —force

It’ll take some time for the changes to get picked-up. What it does is set the “password” fields in /etc/perfsonar/meshconfig-agent-tasks.conf to the value of the API key esmond expects. If you look at that file before and after you should see those fields change.

Thanks,

Andy

On September 13, 2017 at 1:08:14 PM, McDade, Michael () wrote:

I hope this is the correct place to post this question. We recently migrated some perfsonar machines for internal testing from version 3.5 32-bit to 3.5 64-bit, then upgraded to 4.0 64-bit using the migration document found here:

http://docs.perfsonar.net/install_migrate_centos7.html

Initally, all seemed to be working fine. Now we are no longer getting test results via the web interface, and the logs show entries like this:

ps-bsc archiver WARNING  41120: Failed to archive https://localhost/pscheduler/tasks/146face1-6412-4d92-9e39-74df6fe81b5d/runs/d111dfdd-26de-4624-b1f9-e533aebfa451 to esmond: Archiver permanently abandoned registering test after 3 attempt(s): 401: Invalid token.​

Can anyone point me to a document that might assist me in troubleshooting this issue, or perhaps might have an idea what the problem is?

Michael McDade

Systems Programmer Sr.

Marshall University Information Technology

Drinko Library 428K, 1 John Marshall Dr., Huntington, WV 25755

Phone: 304.696.6127