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 <>, "" <>
  • Subject: Re: [perfsonar-user] "Task forbidden by limits", maybe an IPV6 problem?
  • Date: Thu, 27 Sep 2018 14:50:13 +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:cX//ihZQThwTlKmtcbLZdJv/LSx+4OfEezUN459isYplN5qZrsW7bnLW6fgltlLVR4KTs6sC17KJ9fi4EUU7or+5+EgYd5JNUxJXwe43pCcHRPC/NEvgMfTxZDY7FskRHHVs/nW8LFQHUJ2mPw6arXK99yMdFQviPgRpOOv1BpTSj8Oq3Oyu5pHfeQpFiCa/bL9oMBm6sRjau9ULj4dlNqs/0AbCrGFSe+RRy2NoJFaTkAj568yt4pNt8Dletuw4+cJYXqr0Y6o3TbpDDDQ7KG81/9HktQPCTQSU+HQRVHgdnwdSDAjE6BH6WYrxsjf/u+Fg1iSWIdH6QLYpUjm58axlVAHnhzsGNz4h8WHYlMpwjL5AoBm8oxBz2pPYbJ2JOPZ7eK7WYNEUSndbXstJVyJPHJ6yb5cBAeQCM+ZXrYj9qEcBohalHwagGObvxyVUinPq36A31fkqHwHc3AwnGtIDqHPao8/vNKcRTOu7zLfHzTTfb/hL3jr97YbIfQ4gofGQRr9wcMzRyVUxGAPfiFWft5DlMy2P2usTrmeb8vNtWOSygGAkswF8uiajyd0whoXUg48Z103I+Th8zYY7KtC0VFJ3bNumHZROuCyVKY57T8Y8T210uis20qAKtYK4cSQQ1pgqxATTZ+KZf4WH+B7vSvudLStgiHJrZr2yhAq+/E2lx+LgVsS03lhHoy9fndTMtX0A1xne58qaRvZ+4Eis3DKC2xzP5u5fJ00/iLDVJIQ7wrEqk5oeqUTDETHymEXxlKKYblkp9O+05+noe7nru4eSOoFthgH5KashhNazAeMlMggSRGeb/vm81Lv+8kHjWLVKlPo2krXHv5/GOcQbp6m5AwlP3oYk9ha/EzOm0NMfnXkENl5KZBWHj43xN1HPJvD3E+u/jkyynDhx2/zKI7jsDojQInTelbrhc7lw51JAxAc2z91Q+Z1ZBa8ELf/2REP9qN7VAgc8MwOuwubnDNt91pkZWWKKGqKZNa3SvkGJ5uIzOOSMZYkVuCrjJPg/4f7hk2M5lUEHcaa3wJQXdWi0Hu56LEWBfXrsntABHH8SvgUgVuzqhkaCUTlVZ3moRaIw/yw7CJm4AofZXY2thL2B3DynHp1NeGxKEFGMEXH0d4qaQfcMbjydItN/njAeS7euVpIhhlmSs1rCxqZqZtHV9ygDuJSrgMN06ujImBca6Dd9FYKQ33zbCyk+hm4SSSQx2qll5FFmx02r0K5kjuZeGMAJof5FT01yYYbR1eJhDNb7QEfcZdqTYFegXti8BzwtFJQ8z8JYMGhnHND3qxnZ3GKEDr4J3+iOCpE17ord2WT8PcBw1yyA2aU82Qp1CvBTPHGr0/YsvzPYAJTExgDAz/7wL/YVwTLN+WGfzGGHoEBfVktqXL7YWWwEPxKI/8ny71mEQrOzWvwrMQpEnMiFLKYCKtjklk5PS/qrPtPCK3mwlGG9CVftpPuMYYPmdn9b0HDbD04JwB0Y9GzAOAQjVW+tpmvEB2loElTiK0rn7eh5ria9SUk5hwGHZkFszfy74BkQ0P2aV/4J2L8Y4mEspygnEQ==
  • Spamdiagnosticoutput: 1:0

I wrote:

 

Pete Siemsen writes:

 

I'm suspicious of the "::1" in the above output. Looks like the requester and server are both the IPv6 localhost? Huh? Any clue appreciated.

 

I am, too, and I’m seeing the same on my development machines and a couple in our test bed.

 

After some additional testing, my dev and testbed systems are behaving as expected, as is 158.142.6.250.  I overlooked something fundamental last night, which is what I get for reading my email after hours.  :-)

 

The task you submitted was for throughput between perfsonar-1850 (your machine) and 158.142.6.250 (at Colorado State University Pueblo).  The diagnostic you’re seeing is correct: the “task” command submitted the task to your machine which, being the same host, saw the submitter and server interface as being the local host (::1).  The task was rejected there, and I’d have to see your limit configuration to know why there were no identifications made.  If you want to send it to me off-list, I’ll look it over and follow up here.

 

Had pScheduler on your machine approved of the task, it would have connected to pScheduler at CSUP and run the same thing by it in the process of setting it up there.  (Throughput is a two-participant test and requires consent of the systems at both ends.)  The system at CSUP seems to be running at least the stock limit configuration, which makes it balk at UDP throughput at more than 50 Mbps when I try to run a task between one of my machines and there:

 

% pscheduler task throughput --udp --bandwidth 1G --dest 158.142.6.250

Submitting task...

Unable to post task: Error while tasking 158.142.6.250: Unable to post task to 158.142.6.250: Task forbidden by limits:

Hints:

  requester: xxx.xxx.xxx.xxx  (My IP)

  server: 158.142.6.250

Identified as everybody

Classified as default

Application: Defaults applied to non-friendly hosts

  Group 1: Limit 'innocuous-tests' failed: Passed but inverted

  Group 1: Limit 'throughput-default-tcp' failed: UDP testing not allowed

  Group 1: Limit 'throughput-default-udp' failed: Bandwidth not in 1..50M

  Group 1: Limit 'idleex-default' failed: Test is not 'idleex'

  Group 1: Want any, 0/4 passed, 4/4 failed: FAIL

  Group 1: Failed; stopping here.

  Application FAILS

Proposal does not meet limits

 

Your plain-Jane throughput task would have been approved there, as were the ones I ran from my own systems.

 

--Mark

 




Archive powered by MHonArc 2.6.19.

Top of Page