perfsonar-user - [perfsonar-user] meshconfig-agent.log 400 bad request error on toolkit hosts
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: matt fetting <>
- To:
- Subject: [perfsonar-user] meshconfig-agent.log 400 bad request error on toolkit hosts
- Date: Thu, 25 Jan 2018 11:37:09 -0500
- Ironport-phdr: 9a23:hTmrMRYyMOsHEzhzmZ17bvD/LSx+4OfEezUN459isYplN5qZoMu+bnLW6fgltlLVR4KTs6sC17KP9fi4EUU7or+5+EgYd5JNUxJXwe43pCcHRPC/NEvgMfTxZDY7FskRHHVs/nW8LFQHUJ2mPw6arXK99yMdFQviPgRpOOv1BpTSj8Oq3Oyu5pHfeQpFiCagbb9oMBm6sRjau9ULj4dlNqs/0AbCrGFSe+RRy2NoJFaTkAj568yt4pNt8Dletuw4+cJYXqr0Y6o3TbpDDDQ7KG81/9HktQPCTQSU+HQRVHgdnwdSDAjE6BH6WYrxsjf/u+Fg1iSWIdH6QLYpUjmk8qxlSgLniD0fOjA5/m/ZidF+grxHrx+6vRNz35TZbZuJOPZifK7Qe84RS2pbXsZWUixMGoa8YJETD+odIO1YoZfyp0cSrRu/AwmsC/7kxzhNhnDswa06z/4tEQ/Y0ww8A9IOsXLUrNruOacdVOC61qjIzTHZY/xK3jf97ZHFfxY8qv+PRbJ9adTdxlMzGw/Zi1ictIPoMjOJ2ukIvGWX8/dsWf6qhmE7tw18oD2iy8IyhoXXmo0YzE3P+z9jz4YvP9K4TVZ2Yd66H5tUsCGXL452TdkjQ2FsoSo6zrMGtYKicCkF1pgr2QLQZ+aIc4iP5RLjW+KRLiliiH15f7K/gg6+8UmmyuLiSsm5yEhGoTBZntXQs30ByhPe58ibRvZ48UqtxSuD2xzW5+5YPUw5l6/WJps/zrIuipUfqUHDETX3mEXygq+WbEIk+u2w5uTieLrmuoOcO5V6ig7gLqQuhs2/AeI3MgUVUGib/P6z1Lzn/UHjXLpKifg2nrHDsJ/GPcQburK5AwhN34Y79Rm/FTmm0M8fnXkBNl1FYguLj5XyO17QOvD1FvO/g1W3kDd33PDKIKftApTLLnjfjrjhZ7B95FBAyAYt19xQ+Y9bCqxSaM70D1f8rtLDCRkwKUmp2Ov9INR7yo4EX2+TWOmUPL6Bn0WP47cqKvWQLIEYpCr8Lfdts/vnkWN/l1IBYaiv0rMYbXm5GrJtJEDPMimkucsIDWpf5ll2d+ftklDXCTM=
I have 3 centos7 toolkit hosts deployed from the netinstall iso, two of which are intended to run tests and one of which is intended to be a measurement archive. Starting very simple with just owamp, traceroute, and iperf tests between these two testing hosts. My understanding about perfSonar is partial, so please excuse any ignorance here.
My MaDDash dashboard has some errors around not being able to find data for some tests, and it's been up/running for over 24 hours now without changes. The scheduled tests are frequent and should be showing data by now. pScheduler is running on both hosts, and there is no firewall in between them. I can confirm that with certainty because I am the operator. Since these are internal, I've actually stopped firewalld to make sure there isn't any unintended filtering there. selinux is disabled. There are variations of this error message in the meshconfig-agent.log:
2018/01/24 10:18:12 (3859) WARN> perfsonar_meshconfig_agent:430 main:: - Problem determining which pscheduler to submit test to for creation, skipping test throughput(host1->host2): 400 BAD REQUEST: Can't find pScheduler or BWCTL on host2
Can someone help get me started on where to look for resolving this? Past research into the list/google didn't prove fruitful.
Thanks
mdf
- [perfsonar-user] meshconfig-agent.log 400 bad request error on toolkit hosts, matt fetting, 01/25/2018
- Re: [perfsonar-user] meshconfig-agent.log 400 bad request error on toolkit hosts, David Szydloski, 01/25/2018
- Re: [perfsonar-user] meshconfig-agent.log 400 bad request error on toolkit hosts, matt fetting, 01/25/2018
- Re: [perfsonar-user] meshconfig-agent.log 400 bad request error on toolkit hosts, David Szydloski, 01/25/2018
- Re: [perfsonar-user] meshconfig-agent.log 400 bad request error on toolkit hosts, matt fetting, 01/25/2018
- Re: [perfsonar-user] meshconfig-agent.log 400 bad request error on toolkit hosts, Szymon Trocha, 01/26/2018
- Re: [perfsonar-user] meshconfig-agent.log 400 bad request error on toolkit hosts, matt fetting, 01/26/2018
- Re: [perfsonar-user] meshconfig-agent.log 400 bad request error on toolkit hosts, Szymon Trocha, 01/26/2018
- Re: [perfsonar-user] meshconfig-agent.log 400 bad request error on toolkit hosts, matt fetting, 01/25/2018
- Re: [perfsonar-user] meshconfig-agent.log 400 bad request error on toolkit hosts, David Szydloski, 01/25/2018
- Re: [perfsonar-user] meshconfig-agent.log 400 bad request error on toolkit hosts, matt fetting, 01/25/2018
- Re: [perfsonar-user] meshconfig-agent.log 400 bad request error on toolkit hosts, David Szydloski, 01/25/2018
Archive powered by MHonArc 2.6.19.