perfSONAR User Q&A and Other Discussion

[Pete Siemsen <>]

Problem solved. The new limits file seems to work.

Thanks Mark!

-- Pete

On Thu, Sep 27, 2018 at 10:28 AM Mark Feit <> wrote:

Pete Siemsen writes:

 

Mark: attached is my limits file. I don't think it's been modified from the default.

 

That’s not the file we ship.  It’s one of the samples we provide in /usr/share/doc/pscheduler/limit-examples that illustrates how to identify hosts using a downloaded list of CIDR blocks, in this case a list of R&E blocks provided by ESNet.  It’s not intended to be a full configuration that can be dropped in and used.  Because the example is the sole identifier in the configuration and ::1 isn’t in ESNet’s list (see the URL in the configuration), it doesn’t identify as R&E, isn’t classified as “trusted-requesters” and doesn’t activate any of the applications that would allow a task to run.

 

Someone may have put that configuration in place at some point, and because we treat that file as configuration, it won’t be replaced during upgrades.  You can either remove /etc/pscheduler/limits.conf entirely (in which case pScheduler will allow all tests with no restrictions) or you can download a copy of what we ship from GitHub at https://raw.githubusercontent.com/perfsonar/toolkit/master/etc/default_service_configs/pscheduler_limits.conf and replace /etc/pscheduler/limits.conf with it.

 

HTH.

 

--Mark