perfsonar-user - Re: [perfsonar-user] PS 5.0.1 limits file issue
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Onno Zweers <>
- To: "MacBurney, James" <>, Mark Feit <>, "" <>
- Subject: Re: [perfsonar-user] PS 5.0.1 limits file issue
- Date: Fri, 21 Apr 2023 21:59:50 +0000
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=surf.nl; dmarc=pass action=none header.from=surf.nl; dkim=pass header.d=surf.nl; 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=J5Vp6TzlxC04kwRLYmmm7Zc2SHZCHHglTG3KSrzMp3o=; b=kf1qh0ZuHXFhY0Y7CfDfz/PbisyFKjqF0A+sUw1+AbMdqWcoc9RjAht2PYzz/MAw7cguZQtuuOb97pcdCXAWIKMDKHJ2w7jHyAdFxsXYrUZ98zHyWtaxfIx/MsXH4dxrHDcYgMScL/V9lkI6w2QhuOPt1bQCJ0ma5pDYhfvVSGrbxZcYnu6HkDhqXe0e/RrmZIBYPS9oipbL67fhiHvKjbkTtIXvbM2gzEamKu8saUrxwp10uqtJ8oQx/GdnLqah1Bwt1wGt36nHFJYCk+dya3ELkaLjCnC8l08thoWrizLcZNDw2LgfutmOEdHSFPapv//h6buyaqVp1STVOGG8AA==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Gf6mgHWRYQnbnZGL0ELY4dH/BpXoykDTmeBEBkmao/hQJy84BbCrp2RPzKCHaGCP9KC3lmccIMG53NXGzKDMQ1whqzqupNIIkPKYbf3ZF3Z/NNfRPREYau1dO+kK2fozZ9EH+2ig5GgFXU0IWbJedGR8nj5iOrBZ9C8vUn1C0tf8X/fq5VGWei/slzcsR6mhoNJGUC/7LohurflYLwHoz4IJw+ZukgL77KBk7gzz3GHGvumFtz6q+Mi/t20R2ofKzvLo1ZowKNlGxKRbQw3wJ5imR9WRwfFUzsyxQp5RlEVzcxsAcUiKLxjWGA1eKln9FlG4ojz6At/aPHCZvC+Bvg==
- Msip_labels:
Same here, the SHA checksum was 8d4d5142229804ccf26ec6969d0113539c5008988d2089e2f504befa1b134e34 and not the one Mark gave. I replaced it with the github version and now `pscheduler troubleshoot` is happy.
I’m not aware of ever having modified the file.
Cheers, Onno
Van:
<> namens MacBurney, James <> 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
Thanks for the fast response.
James From: Mark Feit <>
MacBurney, James writes:
Trying to run a simple pscheduler test and it complains:
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
|
- [perfsonar-user] PS 5.0.1 limits file issue, MacBurney, James, 04/20/2023
- Re: [perfsonar-user] PS 5.0.1 limits file issue, Mark Feit, 04/20/2023
- Re: [perfsonar-user] PS 5.0.1 limits file issue, MacBurney, James, 04/20/2023
- Re: [perfsonar-user] PS 5.0.1 limits file issue, Onno Zweers, 04/21/2023
- Re: [perfsonar-user] PS 5.0.1 limits file issue, MacBurney, James, 04/20/2023
- Re: [perfsonar-user] PS 5.0.1 limits file issue, Mark Feit, 04/20/2023
Archive powered by MHonArc 2.6.24.