perfSONAR User Q&A and Other Discussion

["Garnizov, Ivan (RRZE)" <>]

Hi Orion,

 

With regards to yellowstone.ucar.edu:

Please grep your pscheduler logs at /var/log/pscheduler/pscheduler.log for records with yellowstone.ucar.edu.

Also make sure your pscheduler archiver does not report warnings again. Same location check the "archiver" keyword.

 

With regards to owamp.boulder.noaa.gov:

It seems to be a firewall issue. Purely by FQDN I would not expect to be able to run throughput tests with this host.

You have to make sure you have https and/or TCP 4823 connectivity to the remote host.

Once this error is resolved, your test request will be considered by your local scheduling service. You could try forcing a manual test on the CLI of course. http://docs.perfsonar.net/pscheduler_client_tasks.html

 

Regards,

Ivan Garnizov

 

GEANT SA1T2: pS deployments GN Operations

GEANT SA2T3: pS development team

GEANT SA3T5: eduPERT team

 

 

 

-----Original Message-----
From: Orion Poplawski [mailto:]
Sent: Freitag, 30. Juni 2017 18:31
To: Garnizov, Ivan (RRZE); Andrew Lake;
Subject: Re: [perfsonar-user] Trouble after upgrade

 

Not all issues.  The invalid token messages have gone away, but on the web page there is nothing under "Test Results", but I have at least two hosts configured for ping tests.

 

I added a new host, and that showed up.

 

I deleted and re-added yellowstone.ucar.edu for a ping test, but still nothing shows up for that.

 

Also, I would have thought I could do a throughput test with owamp.boulder.noaa.gov, but I get:

 

2017/06/30 10:16:48 (2306) WARN> perfsonar_meshconfig_agent:430 main:: - Problem determining which pscheduler to submit test to for creation, skipping

test: 400 BAD REQUEST: Can't find pScheduler or BWCTL on owamp.boulder.noaa.gov

 

 

 

On 06/30/2017 01:51 AM, Garnizov, Ivan (RRZE) wrote:

> Hi Orion,

>

> 

>

> I guess your issues have been cleared by now. The problem that you

> observe is that scheduled tasks already on the pipeline do not get

> updated with the new token. It is only the new tasks, that are being negotiated get the new token.

> Hence you see reports for new failures for archiving for some time

> after the update.

 

 

 

--

Orion Poplawski

Technical Manager                          720-772-5637

NWRA, Boulder/CoRA Office             FAX: 303-415-9702

3380 Mitchell Lane                      

Boulder, CO 80301                   http://www.nwra.com