perfsonar-user - Re: [perfsonar-user] [EXTERNAL] perfSONAR 4.2.0 now available
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: "Uhl, George D. (GSFC-423.0)[SGT INC]" <>
- To: Andrew Lake <>, "" <>
- Subject: Re: [perfsonar-user] [EXTERNAL] perfSONAR 4.2.0 now available
- Date: Mon, 26 Aug 2019 16:51:46 +0000
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nasa.gov; dmarc=pass action=none header.from=nasa.gov; dkim=pass header.d=nasa.gov; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=bw68wJoJb/yl9ciKECshpOjOwESQ/cfdzVG76RC70W8=; b=BysjlgWtrRfCziJi8O9RYviJ5mxjdD3JZVsOMY83VHKGEU63NQucPJ1NCCqmFxjR6nxSUzv7f3tbYzXho/44lsJOHS4iSJTvtBAVSLUSqGWOhb14GmzKaKXnDWuftseKsz0eF0xKzyjC6CjlToSW+2TavcvrJicAL92nRz4XmbqCqvKVg6HhajhN4N5e5X75mFAyRG0+WiWc8xiWRPXDgb6BRqxWxAEWQyMeAuESI4oRcXd7S87CmXaN/B39WvLZvrqKNgKj4zp+Hly1IucfMQ+cDnoZdtMZPpkrg60M8C8xchxDocBSEpxy+mM0okC00NZLVs4UeGc42IIx8th+Dg==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=MvxDrJilgAovhf1W3zakRdCIeHxYUBONKSkeRGCnBtgVYKcxL2cjKAghmLhhqFALGjQQ0nLO3wbE9eYDxrY+vt433oAY5qmIwDbFaALdR6b179hD9U/W2HwNQaYFKv3iiJnZy6YVtjuh7JGmJNAvSwG87TUwTHAVjQ03BrXoJ1kEnjieYxhIZwHP11eU+95c9ly1cmIPVQFpvziibqdkp5FSkIgImTD6TXbf4tbT7u0yzLRFU0gaI5SObeP1ECR6CrS44+L5UYZGKzJo48Qxa/9bAhTcspRwabGMh1y3P92TN6eGdfTO/4yhUvojdxziu8zcOp4LiDLd+jZF5LfrEQ==
- Dkim-filter: OpenDKIM Filter v2.11.0 ndjsvnpf103.ndc.nasa.gov 4A4CB400FC7B
Hi Andy,
The host in question is a central MA and it’s not running pscheduler. When I go to https://localhost/pscheduler I get a response from a front-end javascipt app. The _javascript_ brings up an authentication page for users who want to access the MA’s maddash dashboard. It’s a way for us to enforce credentialed access. Since this outside the scope of perfsonar, I’ll just continue to ignore the error message.
Thanks, George
From: Andrew Lake <>
Hi George,
The command does more checking that it used to do. It will now reach out to pscheduler and validate the test specs, context specs and archiver specs. It looks to me like it got some funny results back when it reached out to pscheduler on the local machine. If the local machine does not have pscheduler it should be skipping that step - and confirmed it does just now for me even in cases with a web server but no pscheduler. Is pscheduler on the box where you are running the “psconfig validate" command? If not, is there a web server and does it return something other than a 404 when you try to go to “https://localhost/pscheduler”?
Thanks, Andy
On August 21, 2019 at 7:46:48 AM, Uhl, George D. (GSFC-423.0)[SGT INC] () wrote:
|
- [perfsonar-user] perfSONAR 4.2.0 now available, Andrew Lake, 08/19/2019
- Re: [perfsonar-user] perfSONAR 4.2.0 now available, Phil Reese, 08/20/2019
- Re: [perfsonar-user] perfSONAR 4.2.0 now available, Andrew Lake, 08/22/2019
- Re: [perfsonar-user] [EXTERNAL] perfSONAR 4.2.0 now available, Uhl, George D. (GSFC-423.0)[SGT INC], 08/21/2019
- Re: [perfsonar-user] [EXTERNAL] perfSONAR 4.2.0 now available, Andrew Lake, 08/22/2019
- Re: [perfsonar-user] [EXTERNAL] perfSONAR 4.2.0 now available, Uhl, George D. (GSFC-423.0)[SGT INC], 08/26/2019
- Re: [perfsonar-user] [EXTERNAL] perfSONAR 4.2.0 now available, Andrew Lake, 08/22/2019
- Re: [perfsonar-user] perfSONAR 4.2.0 now available, Phil Reese, 08/20/2019
Archive powered by MHonArc 2.6.19.