Skip to Content.
Sympa Menu

perfsonar-user - [perfsonar-user] meshconfig problems

Subject: perfSONAR User Q&A and Other Discussion

List archive

[perfsonar-user] meshconfig problems


Chronological Thread 
  • From: Pete Siemsen <>
  • To:
  • Subject: [perfsonar-user] meshconfig problems
  • Date: Mon, 13 Aug 2018 18:20:50 -0600
  • Ironport-phdr: 9a23:at2lFRbH2gFDg3hjGCuqiNX/LSx+4OfEezUN459isYplN5qZrsS+bnLW6fgltlLVR4KTs6sC17KI9fi4EUU7or+5+EgYd5JNUxJXwe43pCcHRPC/NEvgMfTxZDY7FskRHHVs/nW8LFQHUJ2mPw6arXK99yMdFQviPgRpOOv1BpTSj8Oq3Oyu5pHfeQpFiCa8bL9oMBm6sRjau9ULj4dlNqs/0AbCrGFSe+RRy2NoJFaTkAj568yt4pNt8Dletuw4+cJYXqr0Y6o3TbpDDDQ7KG81/9HktQPCTQSU+HQRVHgdnwdSDAjE6BH6WYrxsjf/u+Fg1iSWIdH6QLYpUjmk8qxlSgLniD0fOjE28G/ZhM9+gr9Frh29vBFw2ZLYbZuPOfZiYq/Qf9UXTndBUMZLUCxBB5uxYZERAOodI+lTspTzp1oQohu7HgmjGuXvwSJPi3/t3K01zeEhERrY0wwmBN8OrWjbo8/vNKsIT++60bTIwCzFYvhL1zn9743IfQogofGKRb9xf8vRyVIzGAPDkFqQtZbpPzWL2eQRq2Sb6u1gVfixhGI9rQF+vCSvyt8xionPgoIZ0E7L+jhkwIotIt24TlB0Ydi6H5tMrS2aMZV5Qt86T2F2pCY20KMJtoOmfCQS0JQnwRDeZ+WIc4iJ7RLsTv6RITBghH5/frKwmQqy/VC8xeLiUMm00UpFojBDktbSqnABzxrT5dadSvt65Euh3yiA1xzL5uFHO080k7DbJIAnwrIqkJocr1jDEjf4mEXsg6+Wbl8o+u625OT7ernmo56cOJN0ig3kNKQhhNC/DOIlOQYNR2iW4fqw26f/8UHlRbhGk/I7n6nFvJ3fKskXurK1DBNQ34k/9xqyCzKr3dEGkXQJI19Ifg+MgZLzNFHUOv/4CO+yg1SynzdvwPDLJrjhDY/MLnjHibvgc7N951JFxAs809xS6Z1ZBqsOIPL0XU/xu9jYAQEjPwOoxObnDc1x1oIYWW2RHq+UKL3evkWU6u4zJuSAeYAYtTbhJ/Ug6PPikWM1lkMYcKa1wZcabHW1E/F4L0iXbnfgmtIBHn0Lvgo6QuzqklqCUTtLanapXqIz+DQ7CJm4AofFXY2tnaCO0z2hHpFMeG9JF02MHW/yd4qYQ/cMdD6SIsh5nzwcS7ehUYEh1QqptA/80bVnNPPY+jADtZ39zth4/OnTlRAp9TxoFMSRzXuBT2BynmMUWTA2xqZ/rlJhyludy6R3neFXFcEAr89OBx83L5DHyOpzEZXvQQ/bVtaPVFu8RNi6W3c8Qs9i7cUJZhNFFsmvxivC0i+xDrldw6eKCZkv/6T0wnP4PYBwx2uQh/pptEUvXsYabT7uvaV47QWGX4M=
Ever since I upgraded to 4.0.2, my (the FRGP's) participation in the Quilt mesh at http://quiltmesh.onenet.net/maddash-webui/ has been problematic. My whole row is orange. Embarrassing. I've appended the last 25 lines from /var/log/perfsonar/meshconfig-agent.log file. These messages mystify me because I can ping and/or traceroute to most of the hosts that appear in these error messages, like these

ps-grand-bw.perfsonar.kanren.net
kc-core-psr.mo.more.net

perfsonar-1850$ tail --lines=25 meshconfig-agent.log
2018/08/13 18:06:47 (26630) WARN> perfsonar_meshconfig_agent:430 main:: - Problem adding test trace(ps-svl-10g.cenic.net->perfsonar-1850.frgp.net), continuing with rest of config: 403 FORBIDDEN: Task forbidden by limits:
Hints:
  requester: 129.19.165.2
  server: 137.164.28.121
Identified as everybody
Classified as default
Application: Defaults applied to non-friendly hosts
  Group 1: Limit 'innocuous-tests' failed: Test type not in list
  Group 1: Want any, 0/1 passed, 1/1 failed: FAIL
  Group 1: Failed; stopping here.
  Application FAILS
Proposal does not meet limits
2018/08/13 18:06:47 (26630) WARN> perfsonar_meshconfig_agent:430 main:: - Problem adding test trace(ps-grand-bw.perfsonar.kanren.net->perfsonar-1850.frgp.net), continuing with rest of config: 500 timeout: timeout
2018/08/13 18:06:47 (26630) WARN> perfsonar_meshconfig_agent:430 main:: - Problem adding test trace(ps-grand-lt.perfsonar.kanren.net->perfsonar-1850.frgp.net), continuing with rest of config: 500 timeout: timeout
2018/08/13 18:06:47 (26630) WARN> perfsonar_meshconfig_agent:430 main:: - Problem adding test trace(nmon-aa.mich.net->perfsonar-1850.frgp.net), continuing with rest of config: 500 timeout: timeout
2018/08/13 18:06:47 (26630) WARN> perfsonar_meshconfig_agent:430 main:: - Problem adding test trace(kc-core-psr.mo.more.net->perfsonar-1850.frgp.net), continuing with rest of config: 500 timeout: timeout
2018/08/13 18:06:47 (26630) WARN> perfsonar_meshconfig_agent:430 main:: - Problem adding test trace(latency.eugn-perfsonar.nero.net->perfsonar-1850.frgp.net), continuing with rest of config: 500 timeout: timeout
2018/08/13 18:06:47 (26630) WARN> perfsonar_meshconfig_agent:430 main:: - Problem adding test trace(bandwidth.eugn-perfsonar.nero.net->perfsonar-1850.frgp.net), continuing with rest of config: 500 timeout: timeout
2018/08/13 18:06:47 (26630) WARN> perfsonar_meshconfig_agent:430 main:: - Problem adding test trace(perfsonar-1850.frgp.net->web100.pnw-gigapop.net), continuing with rest of config: 500 INTERNAL SERVER ERROR: Unable to determine participants: Process took too long to run.
2018/08/13 18:06:47 (26630) WARN> perfsonar_meshconfig_agent:430 main:: - Problem adding test trace(web100.pnw-gigapop.net->perfsonar-1850.frgp.net), continuing with rest of config: 500 INTERNAL SERVER ERROR: Unable to determine participants: Process took too long to run.
2018/08/13 18:06:47 (26630) WARN> perfsonar_meshconfig_agent:430 main:: - Problem adding test trace(perfsonar.unl.edu->perfsonar-1850.frgp.net), continuing with rest of config: 500 timeout: timeout
2018/08/13 18:06:47 (26630) WARN> perfsonar_meshconfig_agent:430 main:: - Problem adding test trace(perfsonar-msn.wiscnet.net->perfsonar-1850.frgp.net), continuing with rest of config: 500 timeout: timeout
2018/08/13 18:06:47 (26630) WARN> perfsonar_meshconfig_agent:430 main:: - Problem adding test trace(perfsonar-1850.frgp.net->noctuidae.cns.vt.edu), continuing with rest of config: 500 INTERNAL SERVER ERROR: Unable to determine participants: Process took too long to run.
2018/08/13 18:06:47 (26630) WARN> perfsonar_meshconfig_agent:430 main:: - Problem adding test trace(noctuidae.cns.vt.edu->perfsonar-1850.frgp.net), continuing with rest of config: 500 INTERNAL SERVER ERROR: Unable to determine participants: Process took too long to run.
2018/08/13 18:06:47 (26630) WARN> perfsonar_meshconfig_agent:430 main:: - Problem adding test trace(psonar.arc.vt.edu->perfsonar-1850.frgp.net), continuing with rest of config: 500 timeout: timeout

Any clue appreciated :-)

-- Pete


Archive powered by MHonArc 2.6.19.

Top of Page