perfSONAR User Q&A and Other Discussion

[David Szydloski <>]

Andrew,

Thanks that did the trick.

David

On Tue, Jan 9, 2018 at 8:07 AM, Andrew Lake <> wrote:

Hi,

Do you have some tests that are being archived? If you do and you have others running tests against your host, its entirely possible its a test created by someone else that is misconfigured. If you follow the URL in the log message before /runs (e.g. https://localhost/pscheduler/tasks/e781f229-4e38-4c94-97b6-e917a07a950e) you should see a created-by section in the json returned which will tell you who created the task. 

If you have no results being archived, likely something is not right on your host. Try running "/usr/lib/perfsonar/scripts/system_environment/configure_esmond --force”. It should set the key in /etc/perfsonar/meshconfig-agent-tasks.conf. The key should match the one you see in /usr/share/pscheduler/psc-archiver-esmond.json.

Hope that helps,

Andy

On January 9, 2018 at 8:59:04 AM, David Szydloski () wrote:

Hello folks, has anyone seen this error before?

I have tests running that aren't being archived. Here's a snippet from /var/log/pscheduler/pscheduler.log:

Jan  8 20:16:12 netperf01-lon1 archiver WARNING  464: Failed to archive https://localhost/pscheduler/tasks/e781f229-4e38-4c94-97b6-e917a07a950e/runs/299f6061-83b5-47d6-8c9d-c22a22d40609 to esmond: 401: Invalid token.

Is the auth token in the contects of /usr/share/pscheduler/psc-archiver-esmond.json ? Can I regenerate that file / token?

Thanks in advance for your help,

--

David Szydloski

Core Deployment Engineer

VidScale, Inc.

--

David Szydloski

Core Deployment Engineer

VidScale, Inc.