Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] PS 5.0.1 limits file issue

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] PS 5.0.1 limits file issue


Chronological Thread 
    < Chronological >      < Thread >
  • From: Mark Feit <>
  • To: "MacBurney, James" <>, "" <>
  • Subject: Re: [perfsonar-user] PS 5.0.1 limits file issue
  • Date: Thu, 20 Apr 2023 21:28:33 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=internet2.edu; dmarc=pass action=none header.from=internet2.edu; dkim=pass header.d=internet2.edu; 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-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=khFnLRftMMtbyWDpDPwbF6SopXl71ycSogLEJRVRBd8=; b=Lxhq8r8fQE24OABQqmyf5mmxsbG+zsqyPuGzSMJfozpOduHR04Fn4AXRpK1ZspBJH7QVWyguo/hzL4msy+rU7/CyxUsrtJG3Cq9XtGi1WPzGs4fGNanwcktWUZ3HNGcePUjHaGsOVMXV3yzQ3+Xy8PrTXi6CTnwMBN0YjiRhkdK80n1bcWEXR/c49ZHCg/m3JreKHvqAeuqIIBc9WcrtPhEBFQgIlu74NdfiYzive7pqPNqsotfiwOXL9q9OhSNlBpbjHqselU5xA/EZ6Iue9yAQ1tU11KCskiK6Z9e5p0PVDVUuoOk3BSqN2QwsvU6wIJjz6WAhhAD6CRasXXYfsQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=juSoc3gPK3NjaSSDJ0+Mfb8syZEmUfkHz1JPdC7kMP0kDHa+BQzzxWzi1CjNPLmodOTkHHTSux2FRbDXBHzLEezlk8gHcbzDwhJtKBBI6CjVyPg2WgwgpQ8DUwQFVJ+8+VUk1Qi5KYwMCoCE+x9FwX0EY5HI/DyWR5yK3XqVJanwoCtKiAs9qmNGgSw4aHSsymJ0mqY/R4kp/aWgjWMa5ST4xJfKiPwPEswkjnpOExffhhh1tx5iioYz1B/+wYOfh0orRqb2oqE3brxtsrqr+DgmNHpNXnLa1tgUl/cPUyFoz26Dw9zuFbRQ6fL3tuC8H9JpE18XjDtdveHLItnRGw==
  • Msip_labels:

MacBurney, James writes:

 

Trying to run a simple pscheduler test and it complains:

Failed to post task: Unable to complete request: Limit processor is not initialized: Limit processor is not initialized: Limit 'idleex-default' has unsupported type 'test'

 

There was a breaking change in the limit configuration format in 5.0 announced ahead of the release.

 

If your limit config  is the one shipped with 4.4.x (and has a SHA256 sum of 10bc4fb31ba4bb9fdbd1624668035d76d6d6d82e12ca42c6c8fbb98cb0ace831), it should have been replaced with a valid one during the upgrade.  If that did not happen, please let us know.

 

If yours has been customized, we have a helper script that you can download and run to recommend changes:  https://github.com/perfsonar/pscheduler-limit-checker-for-5.0

 

--Mark

 


Archive powered by MHonArc 2.6.24.

Top of Page