perfSONAR User Q&A and Other Discussion

["Uhl, George D. (GSFC-423.0)[SGT INC]" <>]

The dashboard is returning.  It was a matter of waiting for maddash to run the checks.  This is working with the downgraded mojolicious package.  Autoupdate is turned on so I’ll see how things turn out tomorrow.

From: <> on behalf of George Uhl <>
Date: Tuesday, November 27, 2018 at 1:16 PM
To: Andrew Lake <>, "" <>
Subject: [non-nasa source] Re: [perfsonar-user] Fix for perl client connection issue

Quick update.  Cells are orange but clicking on a cell displays graphed performance data.

From: <> on behalf of Andrew Lake <>
Date: Tuesday, November 27, 2018 at 1:05 PM
To: George Uhl <>, "" <>
Subject: Re: [perfsonar-user] Fix for perl client connection issue

Yes, it affects the checks that call out to your archives using https to populate the maddash cells. A "yum update” on the maddash host should fix.

Thanks,

Andy

 

On November 27, 2018 at 1:01:40 PM, Uhl, George D. (GSFC-423.0)[SGT INC] () wrote:

Andy,

Does this impact the Maddash dashboards too?  My dashboard is all orange and I get HTTP 404 Not Found on cell mouse overs.

Thanks,

George

From: <> on behalf of Andrew Lake <>
Date: Monday, November 26, 2018 at 8:52 PM
To: "" <>
Subject: [perfsonar-user] Fix for perl client connection issue

All,

RPMs have been uploaded that address an issue where HTTPS connections made by various perfSONAR perl clients were failing due to an updated third-party library. This includes the Toolkit test listing not displaying as well as pSConfig agents failing to create any new tasks.

The issue arose in the past day when the EPEL yum repo added a new perl-Mojolicious package (the package perfSONAR uses many places for http clients). This update required a version of perl-IO-Socket-SSL newer than what is in the main CentOS repos as well as some other small changes in its use. If you had auto-updates enabled, you may have gotten this package and it caused some of the issues described above. The new perfSONAR 4.1.4 packages that have been uploaded should fix these issues.  

Originally we had planned to do a 4.1.4 release in a few weeks but due to the critical nature of this issue we have pushed out 4.1.4 now and will do a 4.1.5 in the timeframe we planned to do 4.1.4 with the remainder of the changes we had hoped to include. We will send out official release notes and new ISO images tomorrow for 4.1.4, but wanted to let everyone know the RPMs are available for those encountering issues. 

Thanks,

Andy