Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] perfsonar trouble with limits processor

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] perfsonar trouble with limits processor


Chronological Thread 
    < Chronological >      < Thread >
  • From: Mark Feit <>
  • To: Paul MEBALE-ASSAKO <>, "" <>
  • Subject: Re: [perfsonar-user] perfsonar trouble with limits processor
  • Date: Thu, 6 Mar 2025 21:17:54 +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=arcselector10001; 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=AmMyT1eCWb1fMnf0p3bHTrpH548CV71drpqeoX74M5Y=; b=RRyJ+jhR0J3and+syHSfE14MC4SxYeHu1ub6Tbs0lytzSdNXtchOpjXPeT4Fjthpw4Tg+EcINLMqHojZM3EPjDtjnTF8NsmYoRjF9H6U6fzhDH2T0udIu8kC1xQSdhgiMkVUeFFn5OZDUrunIFYGyUWloXARxQaXs4vYyh6vKSABcXXkhAi7it5YOt8AFVY8BREO6pKEiFNIVngBxvgX56kG2dTgKh4Xg6Ky+RzyKv4f50H9GKN0XPGR4x0cWv17Tlwb0czSExGvUGZTWaqtTaZ0lLvndXa0dCgtbHo0SS8RHRSI80dkktq2Dcl1Tiqy7eJUOmPo74LCsJ/uy75YLA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=tnpgbVSZ61Z4tMdOBvbmOzhoOQqOeqa6OYUsJKJCYbaNLRLPjhEtGdYFzpJcpWwoBtgh2ZhF/SfHHmqMVqDJLsoa6pSvu96w9VsCw+nzORqE3z5MF/yp/1Jq+P8mGflK03VE8jxLJHJWDbS3oMojiwQnXSKbS1X16GpwY6fAtSAoM3sIcT4pqNWRFuzJ2Dm3kQ4yX7SkQZFbxwbPmK2jUHI5o71bjUq6dZVHIzg64u0IU4kXdPMwREWwqkLS64UdDo0FAMjF7C4JE2D3ZGiwRCPEGbZaJwKUl6fzzazmwIn/MuOI0Kr8WZDkIP9yhGuI3zcs305HV2ZeN44H6SfFCw==

Paul MEBALE-ASSAKO writes:

 

We get this error message when we run ‘pscheduler troubleshoot’:

mebale-assako@lille-snd-021:~$ pscheduler troubleshoot

Performing basic troubleshooting of lille-snd-021.

...

  Checking limits... Failed.

 

Limit processor is not initialized: ‘ascii’ codec can't decode byte 0xc3 in position 11: ordinal not in range(128)

 

This is a bug in pScheduler.  There’s some old code in the JSON parser that tries to decode byte streams as ASCII when it shouldn’t be so picky.  The API and CLI validators read the file differently and probably shouldn’t.  I’ve opened the ticket listed below and should have it patched in 5.2, which we anticipate putting into beta shortly.

 

https://github.com/perfsonar/pscheduler/issues/1527

 

In the mean time, this can be worked around by removing non-ASCII characters from the limit configuration.

 

--Mark


Archive powered by MHonArc 2.6.24.

Top of Page