Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Errors after auto update

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Errors after auto update


Chronological Thread 
  • From: Luke Whitworth <>
  • To: Steve O'Brien <>, Mark Feit <>
  • Cc: "" <>
  • Subject: Re: [perfsonar-user] Errors after auto update
  • Date: Fri, 28 Apr 2023 10:35:17 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cranfield.ac.uk; dmarc=pass action=none header.from=cranfield.ac.uk; dkim=pass header.d=cranfield.ac.uk; 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=jw/S/eul76e2gY9l0ThC/A7/c5WwuWwqcw+f1vy4OPk=; b=Dtc7WWnZdLN9CheYmIawJ0ph9SZ+j3vV5/YcWEp5y1nVI50uFuy20/JFOf8rY4hL8NFeuu7ZymLWIGD7d3/T7NU3u2l2eBAEV1QOi60b+gxfg/L+KOmcHHwh4Yr3w23zrASvKt3yrSgE60KXLca4koOsaAGq4G992Y7QeXD7U1izTyc4nJCsfSKhe/B8Hkz7FcT3Uej6nqIGIGzLyHhC55Gv4i97mcs3j2phDrcZhXviWT4dsJUgK1lDdjuCUzkaw0URvhsjNlLSWAF6WjHBAz8589rGMGA7LOuX8DCGwJdJe7eQMxGsav3U6FWTBhPf3x5FwK9c5JTfGuRRII6aKA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ZbTX0u38u5H8crxjte6QOIunFejt7Xx1lUncI+k5FLdcDhkrjPvuPavbB4A+O+kB/DV/8SPWfefoXxc/hkJS1mhFNft0M7bez1RF+LTnfMoVwcdv5o4jAeAJbmINduDv23oVCK5kVIaGpcf1j6GIgttGEY5on0zjE7Eyb8bql9vmNOecsVqYisF8YW/87xqVaCgoY+rZkMh7y44vlR4jBMsPEVirTGZ9pBY/x1VefgbVKT9BBZYeRFq/D5QFcwQhoEGwRYgVGbOsLSjtS22Ge93BAEz0eogqpTWqDHkpSUsnNYj+UU9TnrowDuQX1g5ZEuFwNTJBU45X+x3LGiqgqg==

Just ran into this myself after an upgrade on a raspberry pi (from .deb).  Turns out that /etc/perfsonar/toolkit/default_service_configs/pscheduler_limits.conf was as  https://github.com/perfsonar/toolkit/blob/master/toolkit/perfsonar-toolkit/etc/default_service_configs/pscheduler_limits.conf but I still had /etc/pscheduler/limits.conf too.  A quick “mv /etc/pscheduler/limits.conf ~/limits.bak” and a reboot seems to have done the trick.

 

Of course, ymmv!

 

Luke

 

From: <> on behalf of Steve O'Brien <>
Date: Thursday, 27 April 2023 at 19:53
To: Mark Feit <>
Cc: <>
Subject: Re: [perfsonar-user] Errors after auto update

Unfortunately that is not very helpful.  I downloaded the check script and it outputs:

Examining limit configuration at /etc/pscheduler/limits.nso

NO ACTION REQUIRED.

This limit configuration appears to be the one that shipped with perfSONAR
4.x.  It will be replaced automatically with a new one upon upgrade to 5.0.
(END)

 

I have removed the /etc/pscheduler/limits.conf file and reinstalled all pscheduler rpms and it does not give me a new limits.conf file.

 

Steve O'Brien Senior Network Administrator

National Solar Observatory

Daniel K. Inouye Solar Telescope Project

22 Ohi’a Ku Street, Pukalani, HI 96768

 

 

On Thu, Apr 27, 2023 at 1:53 AM Mark Feit <> wrote:

Steve O'Brien writes:

 

I am experiencing a limit error relating to idleex-default after an auto upgrade:

Any help would be appreciated!

The section on changes to the pScheduler limits file in our announcement should get you back into business:  https://lists.internet2.edu/sympa/arc/perfsonar-announce/2023-03/msg00002.html

--Mark

 

.




Archive powered by MHonArc 2.6.24.

Top of Page