Skip to Content.
Sympa Menu

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

Subject: perfSONAR User Q&A and Other Discussion

List archive

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


Chronological Thread 
  • From: Pete Siemsen <>
  • To:
  • Subject: [perfsonar-user] "Task forbidden by limits", maybe an IPV6 problem?
  • Date: Wed, 26 Sep 2018 17:06:35 -0600
  • Ironport-phdr: 9a23:AEjNJR1f6lwcJpizsmDT+DRfVm0co7zxezQtwd8Zse0SKPad9pjvdHbS+e9qxAeQG9mDtLQc06L/iOPJYSQ4+5GPsXQPItRndiQuroEopTEmG9OPEkbhLfTnPGQQFcVGU0J5rTngaRAGUMnxaEfPrXKs8DUcBgvwNRZvJuTyB4Xek9m72/q99pHPYQhEniaxba9vJxiqsAvdsdUbj5F/Iagr0BvJpXVIe+VSxWx2IF+Yggjx6MSt8pN96ipco/0u+dJOXqX8ZKQ4UKdXDC86PGAv5c3krgfMQA2S7XYBSGoWkx5IAw/Y7BHmW5r6ryX3uvZh1CScIMb7S60/Vza/4KdxUBLnhycJOTA6/m/KlMJ/kLlWrwi9qxFl2YPYfJ2ZOfh4c6jAfd0aX21BXsNJWiJbHIy8c5UABPccM+ZZsYb9okAOogW4BQKxA+7v0T5IiWHz3a0hzeshFxrL3BE8EN0UqnTYtsv6O7oPUe2syqTD0DbNb+tO1Dvj8ofEbgwtrPSRUb9/ccfd1UwiGgzGg1iRpoHoOi2Z2vgIvmWe4edsS/mghmg6oA9ruDev3N0jiozRi4IV1F/E8SJ5zZ4wJdKiSU57ZceoEZVVty2HLod3Tc0vT39ztyogxb0Gvpm7fCcOyJs53RLQd/uHc42Q7hLiUuaePyt4iWp7dL2lmxq+7U2txvDzW8S0zFpHqyVIn9rNu30C0hHf9NSLR/5480qvxzqAzBjf6uReLkA1karbJYQhwrk1lpcLqkTDHzH5mEDtjKCIcEUp4fWo5Pj9bbX8vJOTKZJ7ihzmPqQ0hsO/Gfg4MhQJX2WD4eSzyqfj/UPiQLVNiP05iLPZvInHJcQAuKG5GRRY0oIi6xakEzemy8oUkWMGLFJDZBKIkZLpO1fQL/DkE/uzmUqjnyp2x6OOArq0GpjXIGPElr77OKtm5lR0yQwvwMpZ6o4OTLwNPaHdQEj04eTVEhJxCA25xv3qDp0pzYITXHmCBIeEO6rI91KE+7R8cKG3eIYJtWOleLAe7Pn0gCphlA==
What might explain the following:

perfsonar-1850$  pscheduler task throughput -t 30 -d 158.142.6.250
Submitting task...
Unable to post task: Task forbidden by limits:
Hints:
  requester: ::1
  server: ::1
Made no identifications.
The 'pscheduler troubleshoot' command may be of use in problem
diagnosis. 'pscheduler troubleshoot --help' for more information.

I think the above "pscheduler" command means "Do a 30-second throughput test to 158.142.6.250". I can execute that command successfully on another perfSONAR machine at my site. The working machine is running 4.0.2 on CentOS 6.10. The failing machine is running 4.1.2 on CentOS 7.5. The failing machine is a fresh install - it has net yet had a working test configured.

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.

-- Pete


Archive powered by MHonArc 2.6.19.

Top of Page