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: Wed, 26 Sep 2018 23:35:49 +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:mqwvDxwfN6onXozXCy+O+j09IxM/srCxBDY+r6Qd2uMVIJqq85mqBkHD//Il1AaPAd2Eraocw8Pt8InYEVQa5piAtH1QOLdtbDQizfssogo7HcSeAlf6JvO5JwYzHcBFSUM3tyrjaRsdF8nxfUDdrWOv5jAOBBr/KRB1JuPoEYLOksi7ze+/94HRbglSmDaxfa55IQmrownWqsQYm5ZpJLwryhvOrHtIeuBWyn1tKFmOgRvy5dq+8YB6/ShItP0v68BPUaPhf6QlVrNYFygpM3o05MLwqxbOSxaE62YGXWUXlhpIBBXF7A3/U5zsvCb2qvZx1S+HNsDtU7s6RSqt4LtqSB/wiScIKTg58H3MisdtiK5XuQ+tqwBjz4LRZoyeKfhwcb7Hfd4CRWRPQNtfVzBPDI2/YYsADesBMvpXoITmvVQCsR6+CBOwCO/zyDJFgGL9060g0+QmFAHLxAsuEMgUsHTXsd77NLkdUeGpzKLVyjjDav1W1in86IjUaR0hoPeMXa5ufsrLz0kgCR/FgkuKpYP7IjyVy/0Avm6G5ORuUuKvjnQoqwB3ojW3yccsi5XJhoIIyl/f7yl23IE1Jdi+RUVmYtCkCINduz+HO4Z3WM8vTX9ktDwnxrAFpJK3ZjUGxZYnyhLHdvCLb4uF7gj9WOuSOzt0mmxpdb2lixqs7ESs1vXwVseq31tJsiZIl9zBuWwN2hzd5MWKT+Fy80ei1DuP0g3e6PxILEMqmqfeL5Mt3qI8mYEVvE/eBCH5gl/2g7WTdkg8+uin9eDnYrL+q5GEK4J6jR3yPrk3lsGiA+s0LBECX2+A9uuizrHj+lD5QKlRgf0xj6nZto3VKd4Dpq6jBA9Vzpgs5AqjDzen19QYm2MLLFVYeBKbi4jpPFbOIPPiAfijhFSslS9nx/HAPrL/HpXANmbPnKrgcLpn5UNQ1hA/wc1c6p5JEL0NPfD+V0/puNzdFBA5Mgi0w+j9CNV604MTQWePAqGHP6PTrV+F/eMvI++QZIALojb9LeYq5+LwgXMjh1ASYLSp0YMNaH+kBvRmP1mZYX30j9cZD2gKpAQ+TPftiF2ESzFTfW++X78n5j4lEoKrFoPDRoG2gLydxye3AIdaZmFAClCQD3jobYOEVOkQaC6MOMNujCELVaXyA7MmgCmjqAKy8LtqK/HZ/GVMrpPu0cN44cXOnhgoszF4EpLZmyuVQnt6hWQOTiVzwbtyu2R8zEuOy651n6YeGNBOrbsdSgogO4XbyeVgTs3pVxjpf9GVRUygT8n8Rzw9U4Ri7cUJZhNYEs+hxj7O3jbiV7obmr2XLJ0y7q/G2XXtfYBwx2uQh/pptEUvXsYabT7uvaV47QWGQteRyx/Dxa+3aaQR2jLM/26fzG2I+VtVSxN0Tb6cBC5Ne0Dft5L06l6RB7OtCLFyNAxHxIbCL6ZRcdTmgB1AQ+urI9XRZW+92gLSTRaFz7+BdszmLmMa2iiOFUMNiUYe8WvVfQQ7Dz2q9mTZCjEmHFnzYkTqpO95rn7zTkI9wwyQKUN70L/g+xgJiOaaRu9JmL8IpXQs
  • Spamdiagnosticoutput: 1:0

Pete Siemsen writes:

 

What might explain the following:

…

Hints:

  requester: ::1

  server: ::1

Made no identifications.

…

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.  It’s possible that something outside of perfSONAR has changed recently; CentOS does spring one on us from time to time.  I did verify that Apache is logging the correct source IP address, so it has to be something between that and pScheduler.  I’ve opened a ticket on this (https://github.com/perfsonar/pscheduler/issues/682) and will look into it promptly because this will adversely affect the functioning of the limit system.

 

The “Made no identifications” message is inconsistent with the way the stock limit configuration (/etc/pscheduler/limits.conf) shipped with the toolkit should behave.  Has yours been modified?

 

--Mark

 


Archive powered by MHonArc 2.6.19.

Top of Page