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: "Curtis, Bruce" <>, Pete Siemsen <>
  • Cc: "" <>
  • Subject: Re: [perfsonar-user] "Task forbidden by limits", maybe an IPV6 problem?
  • Date: Thu, 27 Sep 2018 16:02:52 +0000
  • Accept-language: en-US
  • Authentication-results: ndsu.edu; dkim=none (message not signed) header.d=none;ndsu.edu; dmarc=none action=none header.from=internet2.edu;
  • Ironport-phdr: 9a23:x0bYpx+Gtl4IBP9uRHKM819IXTAuvvDOBiVQ1KB+0+sVIJqq85mqBkHD//Il1AaPAd2Eraocw8Pt8InYEVQa5piAtH1QOLdtbDQizfssogo7HcSeAlf6JvO5JwYzHcBFSUM3tyrjaRsdF8nxfUDdrWOv5jAOBBr/KRB1JuPoEYLOksi7ze+/94HRbglSmDaxfa55IQmrownWqsQYm5ZpJLwryhvOrHtIeuBWyn1tKFmOgRvy5dq+8YB6/ShItP0v68BPUaPhf6QlVrNYFygpM3o05MLwqxbOSxaE62YGXWUXlhpIBBXF7A3/U5zsvCb2qvZx1S+HNsDtU7s6RSqt4LtqSB/wiScIKTg58H3MisdtiK5XuQ+tqwBjz4LRZoyeKfhwcb7Hfd4CRWRPQNtfVzBPDI2/YYsADesBMvpXoITmvVQCsR6+CBOwCO/zyDJFgGL9060g0+QmFAHLxAsuEMgUsHTXsd77NLkdUeGpzKLVyjjDav1W1in86IjUaR0hoPeMXa5ufsrLz0kgCR/FgkuKpYP7IjyVy/0Avm6G5ORuUuKvjnQoqwB3ojW3x8csjJXJiZwPylDC6yp53Jg5KcemR0FmfN6pFoZbuSKCN4ZuXM8tWX1ktDs/x7EbpJK3YS0HyJooyhLDd/CKdoqF7QzsWeuQJDp1gWxpdK68ihqq7ESs1u7xWtOq3FtJtCZJjMfAu38X2xDN98SLVuNx/km/1juMywze7+RJLlw0mKrVJZMsx6Q/m5oQvEnDGyL7mlj6gayIeUgh/uWk9/jrba7gq5SBLYF7kBv+Pb4rmsGnAeQ3LAwOX2+D9OqkyLDt+lH1TKtTgvArlKfVronWJcMAqaGnGQNV1Zsj6wqkADehzdQYm2QIIEhdeBKdiIjpJ0/BL+zkDfe+hFSsli1nx/fbPr39BpXNKX/DkLT7cblh7E5czRI/zdFZ551KFrEMOOz/VVXtuNDFCxI1LhG4z/viBdVz2Y4SRX6DD6qbPazMvlKF5+ciLuySaIMJuzvxM/0l6OTvjX89l18dZ66p3Z4PZXC9EPRpPUSZYWb3j9cAF2cKohQxTPbsiFKcTT5feWy+ULwh6TEmEI6mF5vMRpixgLyd2ye2BoVWaX5cClCCCnfocIOEVO0WaC6LP89hiSILVaK6Ro8l1BGurxP6y6F5IubO+y0Ys47j28Zv5+3Vix4y6SJ4A96D3G6QUmEn1l8PEnUdwbpjoFc5gn2ZzKN1ybQMH8ZO7P4PWRogKZ/H5+p2EM20Vw7cKJPBcFu6T52dADw0Vd83i4sVYkt4ANikpg3I1jDsDrMIwe+lHpsxp4fVxXu5Cct81z6S0acsjkUOQ81TOHegi7IlsQXfGtiawA2ii6+2ePFEj2b2/2CZwD/L5RkAClQiWLjZXX0ZekrdpMj44UWHVbK1FLA7KVIYl5yEJrBXLNDlkAYOSPTiPYHYZGS80ye1CA2Tz7yBJIztZy0G3SrbBURF9mJb/XuPOQUkQCv0pWXYAW9oGUnyJU7g7Lo2pHayVERhyQaMYgVo3Ka0/RhAg/uaRrsT07sItT1npS9zGQO82c7bEdyNu1AncalBMt4=
  • Spamdiagnosticoutput: 1:0

Curtis, Bruce writes:

 

Does your local machine limit throughput tests to 20 seconds?

If so would that explain why the task is forbidden?

 

There would be diagnostic information that would say what limits weren’t met.  See my last post for an example.

 

What’s going on here is even more fundamental than that.  Nothing during the identification phase, which is where the system figures out who’s asking for a measurement, is firing.  The configuration we ship with the toolkit includes an identifier called “everybody” that’s supposed to be tripped for every request no matter what.  That’s not happening, which leads me to think the limit configuration on Pete’s system has been modified in a way that makes it fall back on the default behavior of denying everything.  A copy of that file just arrived; I’ll look at it and follow up in a minute.

 

This is an opportune time to plug Know Your Limits, our upcoming tutorial on how to configure and diagnose pScheduler’s limit system.  The announcement is here:  https://lists.internet2.edu/sympa/arc/perfsonar-announce/2018-09/msg00000.html.

 

--Mark

 




Archive powered by MHonArc 2.6.19.

Top of Page