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: "MacBurney, James" <>
  • To: Mark Feit <>, "" <>
  • Subject: Re: [perfsonar-user] PS 5.0.1 limits file issue
  • Date: Thu, 20 Apr 2023 22:23:37 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ipac.caltech.edu; dmarc=pass action=none header.from=ipac.caltech.edu; dkim=pass header.d=ipac.caltech.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=xM4vGeAmymhiH+2aFU8gYI4IN7TCk6y2XxuGL5Y34ZI=; b=e1fqHi3Uu6UiUONOt5mGy3sCF0T9MJ3rjlTwiCmHbtVORnStOdPZEhMBiTyFMebITCmzYg1s7ckxrwnpeYld9QBc8q9z21dbtJ2Zky98WLUauwOz3TKuxh1qlbQOl3iNKF1fPl5TEbXo1YUs3iyiPPTokYeKVMrEUGd8DgB6HEg90+eAGz7mzR8+7PiNzl6Va9TnxvPBaq9LlD+Uxq1QBpHxAnKCXvt/9l6o5O1uXasiyY+bbY0o3L31ZzFFgTBz/HdeAI7eneHFHR2QyDj+sSRCLtjxk57Fhnxaxo6s0CCT9WWqSsDvFAJr+kYekOqbEIRMeElguUiAXd5tZQOjvw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Z//qEHtJ3pxPUWVDxDGQYECORgqacxh1YTrs+QRHbW7syQcIJsCaI5mrcd0vmGLwnJw4S3FcEC6ZU/JvLyi4TvHIXo9/ho3X+bgg6EsDlaBMGMGB7stC/awxRpFC6n06Ztbm/ECNXyqITGHSUrfltEZh0IfcaOrUkXZgrO0u0U0AKjoESycwBx5PoJLbo6vGGXaAkJmwHeri2ZGQfAZH8a8RzPWJy1r8i8jffKpQk6Bj5hF0PGvutqjZnkzzqBRXFUITj/w+870NiMf1ccbd42C6Yj/a7mXjU6ZCquKPzOHNJvwfCf89wMhyqWtHZGtpzld0CRamDXLBMUAmCiV5/Q==
  • Msip_labels:
Mark,

the script output gave a code section to swapout, but that did not fix the problem.  Using the github link to the limits.conf file actually fixed our issue.

FYI, our limits.conf file still had an Aug 20,2019 timestamp. and SHA256sum did not match the one you provided.  So, it was not updated.

The link to get a working file is this: https://github.com/perfsonar/toolkit/blob/master/toolkit/perfsonar-toolkit/etc/default_service_configs/pscheduler_limits.conf
perfSONAR Toolkit distribution environment scripts and GUI - toolkit/pscheduler_limits.conf at master · perfsonar/toolkit
github.com
Thanks for the fast response.

James
From: Mark Feit <>
Sent: Thursday, April 20, 2023 2:28 PM
To: MacBurney, James <>; <>
Subject: Re: PS 5.0.1 limits file issue
 

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