perfSONAR User Q&A and Other Discussion

[Zhi-Wei Lu <>]

Thank you, Jason!

 

It turns out that the /etc/perfsonar/meshconfig-agent-tasks.conf

Is no longer used in the new perfsonar 4.1.1, and it has been converted to somewhere else.

It appears the the password part has been moved to /etc/perfsonar/psconfig/archives.d/esmond_local.json

 

I also tried to use the OLD /usr/share/pscheduler/psc-archive-esmond.json file from my backup (CentOS 6), but I am still getting archival errors.

 

I am still looking at a solution.

 

Thanks again.

 

Zhi-Wei Lu

IET-CR-Network Operations Center

University of California, Davis

(530) 752-0155

 

From: Jason Watt <>
Sent: Wednesday, September 05, 2018 10:52 AM
To: Zhi-Wei Lu <>
Subject: Re: [perfsonar-user] Archiving to esmond failed after CentOS6 -> CentOS7 migration

 

See if your token (password) is the same in these two files:

 

/etc/perfsonar/meshconfig-agent-tasks.conf

/usr/share/pscheduler/psc-archiver-esmond.json

 

I had a similar problem recently with the "invalid token" error. 

 

 

 

 

On Wed, Sep 5, 2018 at 11:46 AM, Zhi-Wei Lu <> wrote:

Hi all,

 

I have just upgraded and migrated a few of my CentOS 6 perfsonar servers to CentOS 7.  I don’t see any new tests recorded.  I then noticed error messages in /var/log/ pscheduler/pscheduler.log

 

Sep  5 10:28:37 mammoth-owamp-v4 journal: runner INFO     1575513: With ping: rtt --count 10 --dest grx-v4.noc.ucdavis.edu --interval PT1S --source mammoth-owamp-v4.noc.ucdavis.edu --length 1000

Sep  5 10:28:46 mammoth-owamp-v4 journal: runner INFO     1575513: Run succeeded.

Sep  5 10:28:47 mammoth-owamp-v4 journal: archiver WARNING  1473429: Failed to archive https://localhost/pscheduler/tasks/44d685eb-40c6-48eb-90c9-fc5dd427e3cc/runs/79c06354-dd20-48c1-afe4-e6bf4fdd0ae2 to esmond: 401: Invalid token.

Sep  5 10:29:02 mammoth-owamp-v4 journal: archiver WARNING  1472536: Failed to archive https://localhost/pscheduler/tasks/c2a13eb2-b022-443d-95b9-42fa62c1859c/runs/44381ff1-71c4-4875-922f-c9cc9b253c29 to esmond: 401: Invalid token.

Sep  5 10:29:47 mammoth-owamp-v4 journal: archiver WARNING  1473429: Failed to archive https://localhost/pscheduler/tasks/44d685eb-40c6-48eb-90c9-fc5dd427e3cc/runs/79c06354-dd20-48c1-afe4-e6bf4fdd0ae2 to esmond: 401: Invalid token.

Sep  5 10:34:47 mammoth-owamp-v4 journal: archiver WARNING  1473429: Failed to archive https://localhost/pscheduler/tasks/44d685eb-40c6-48eb-90c9-fc5dd427e3cc/runs/79c06354-dd20-48c1-afe4-e6bf4fdd0ae2 to esmond: Archiver permanently abandoned registering test after 3 attempt(s): 401: Invalid token.

Sep  5 10:34:47 mammoth-owamp-v4 journal: archiver WARNING  1473429: Gave up archiving https://localhost/pscheduler/tasks/44d685eb-40c6-48eb-90c9-fc5dd427e3cc/runs/79c06354-dd20-48c1-afe4-e6bf4fdd0ae2 to esmond

 

I guess that “localhost” probably should be the real host name, is that right? As I have a few hostnames for the server, which one I should use?  How do I configure perfsonar to use that name?

 

Thank you!

 

Zhi-Wei Lu

IET-CR-Network Operations Center

University of California, Davis

(530) 752-0155

 

--
To unsubscribe from this list: https://lists.internet2.edu/sympa/signoff/perfsonar-user