Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] "Task forbidden by limits", maybe an IPV6 problem?

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] "Task forbidden by limits", maybe an IPV6 problem?


Chronological Thread 
  • From: Mark Feit <>
  • To: Pete Siemsen <>, "" <>
  • Cc: "" <>
  • Subject: Re: [perfsonar-user] "Task forbidden by limits", maybe an IPV6 problem?
  • Date: Thu, 27 Sep 2018 16:28:29 +0000
  • Accept-language: en-US
  • Authentication-results: ucar.edu; dkim=none (message not signed) header.d=none;ucar.edu; dmarc=none action=none header.from=internet2.edu;
  • Ironport-phdr: 9a23:3U8n2RStEJfcA8Tq0ymgvf6A5tpsv+yvbD5Q0YIujvd0So/mwa67ZBSGt8tkgFKBZ4jH8fUM07OQ7/i/HzRYqb+681k6OKRWUBEEjchE1ycBO+WiTXPBEfjxciYhF95DXlI2t1uyMExSBdqsLwaK+i764jEdAAjwOhRoLerpBIHSk9631+ev8JHPfglEnjWwba9wIRmssQndqtQdjJd/JKo21hbHuGZDdf5MxWNvK1KTnhL86dm18ZV+7SleuO8v+tBZX6nicKs2UbJXDDI9M2Ao/8LrrgXMTRGO5nQHTGoblAdDDhXf4xH7WpfxtTb6tvZ41SKHM8D6Uaw4VDK/5KpwVhTmlDkIOCI48GHPi8x/kqRboA66pxdix4LYeZyZOOZicq/Ye94RWGhPUdtLVyFZAo2ycZYBD/YPM+hboYnypVoOogexCgS3Huzj1jpIi2Xq0aEm0eksFxzN0gw6H9IJtXTZtNL7O70IUeC20aLGzSvMb/JK2Tzg74XIdx4hru+NXbJsasfRyE8vFx/bgVWKr4zqIS+V2voXv2eF8uVgSPuihmg6oA9/pTivw90jiojPho8NxVDE9Dl5wIYoJdKjVU57esCrEIFMuCGdMYt2Xt0tQ2d0uCog1rIGvpu7cS4Xw5ok3x7Sc+KLf5WJ7x75WuudPy10iG9mdb6inRq+70etx+LkWsWpzFpHrTBJnsfPu3wXyRDf9MeKRuFj8ku8xTqDzw7T5f9HLEwokKfWLoIuz74+lpcdtEnMBC/7lUb2gaKTdEgo5+ul5Prib7jiupOQK5R7hwfjOao0gMO/G/43Mg0WUmib5+u80Lrj8FXhTrhWifM6jqnUvInHKMsZuKK1GghV3Z095BqlCDemzcgYkmIALFJYfhKIkpLlO0nUIPD/EfewnUijkCtqx/DBOL3tGJLNLmXfkLflerZ97E1cxBAvwtBY4pJYErABIPTtVU/trNHUEAI1Pg2uz+vpFtlxzJ4SVGGSDqODLq/fvlCF6voqI+aWZY8VvDj9K+Ii5/7rlXI5nFEdcreo3ZsLc324H/JmI1mHbnr2hNcOD3sKshQkQOP0lVKCTCZfZ2yuUKIk+jE7FIWmAJ/bRo+zmryB0jy7HppQZm9cEFCACGrod56aVPcWcy+SJs5hkicYVbi6VYMtzxCutAnmy7V5NOrU/DMXtY792NRv+eLciAwypnRICJGl3n2AB1p1k2YTSjl+iLt+rElmx1GrzKNxmbpVGcEFo7sDWB0nPpOaxPFgF9HpcgTNZcrPRVq7CJ3yCyssRd93yMIUf0dmM9OulQ2F0ia3Vew7jbuOUbk96KGU8XXwO44pznjL1bUJjl86T9FJOHH8wKNz6l6AVMbyj0yFmvPyJuwn1ynX+TLGlDLW5hsKWRNsUajDQXEUb1fXqtK8/E7ZUruyEu1+bFlcwseYbKZGd46hgVZHQaLlP9LTKyK0lnyrDBmFjrWLcMLxemob0SmcbSpMkw0a8XuccwRrACCnrjHDBzV0U1/jfhCk/ex3snjuSEgywkmDZFFg0Lzg/BkTiLScRvof06hCtj0mrmB1GkqwxdTbF4DGqgZ8L6g=
  • Spamdiagnosticoutput: 1:0

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

 




Archive powered by MHonArc 2.6.19.

Top of Page