perfsonar-user - Re: [perfsonar-user] Failed to archive to esmond: 400 Invalid JSON returned
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Andrew Lake <>
- To: ,
- Subject: Re: [perfsonar-user] Failed to archive to esmond: 400 Invalid JSON returned
- Date: Fri, 2 Feb 2018 09:30:23 -0500
- Ironport-phdr: 9a23:oMuVIB8CZm7tef9uRHKM819IXTAuvvDOBiVQ1KB41+4cTK2v8tzYMVDF4r011RmVBdyds6oMotGVmpioYXYH75eFvSJKW713fDhBt/8rmRc9CtWOE0zxIa2iRSU7GMNfSA0tpCnjYgBaF8nkelLdvGC54yIMFRXjLwp1Ifn+FpLPg8it2O2+54Dfbx9UiDahfLh/MAi4oQLNu8cMnIBsMLwxyhzHontJf+RZ22ZlLk+Nkhj/+8m94odt/zxftPw9+cFAV776f7kjQrxDEDsmKWE169b1uhTFUACC+2ETUmQSkhpPHgjF8BT3VYr/vyfmquZw3jSRMMvrRr42RDui9b9mRh/qhycJMDA2/2/ZhM9tgqxFvB2svAZwz5LObYyPLvdyYqHQcNUHTmRBRMZRUClBD5ugYosJEuUBJ/hXrofgrFUItxS+BhejD/7oxzBSgH/5wK073v8/HgHdxgAgGcwBsGjNodjzKawcX+e1zKzSwjXCafNbwTb96I7Uch8/u/GMW6x/cdbPxUU1CQzKk0iQpIr4ND2WzuQAq3WX4/RjWO61hWMrsQ58riW1ysotiYTFnpwZxkzA+Cljw4s4Jce0RFBlbdOqCpdcqiWXOohwT8g/WW9nojw6xacDuZOjfCgF1pAnxxnHZvyJbYeF7AjvVOKKLjd8nn5ld7W/hwiq/UihzO3zSNW03U5XoiZbkdTArH4A2wbc58SaUPdw/0Ss1S6K1w/J6+FEJU40lbDcK54k2rM/jJwTvlnDHyLthkr2l7WadkM69ei08+jneKnppoeAN49ojQHzKrwuldKlAeQ2KQgOWG6b9v6m1LH64E35W6tFjuctn6ndsZDaPtgbprWnDwNP04Yj7Qq/ACm80NQeg3YHMExJdAiZgIf0JlGdaMz/WO+ymVq3lzFi3bXbJbD7KpTLMnXZlrr9J/Bw51MYgBAvwNJY/LpQA6sKZu/oQgn7ro/2FBg8ZiWyz/zqF51Z34ATETaGBKOIGK7J91mF+rR8cKG3eIYJtWOleLAe7Pn0gCphlA==
Hi, In general if you are not seeing anything in the archive logs that likely means the test in question is not reaching your archive for some reason or your archive is down. A couple things to check: 1. Are you actually missing any tests/data when you look at your dashboard or toolkit test listing (not sure which displays are applicable for your setup)? It’s quite possible the error is not caused by a test you have created. If someone else created a test where your host is the source, but misconfigured the archive, then you could see this error. There should be a URL in the log error message that if followed will take you to some JSON with all the details of the test, including where it’s trying to archive. 2. Double-check the URL of the archive to make sure its configured correctly for the test. 3. On the archive host, make sure you have looked in both /var/log/esmond/esmond.log and /var/log/esmond/django.log. 4. Also try visiting the archive in question to make sure its reachable something like “curl -k https://YOURHOST/esmond/perfsonar/archive/?limit=1” from the host giving you the errors should give you an indication. Hope that helps, Andy On February 2, 2018 at 7:31:02 AM, () wrote:
|
- [perfsonar-user] Failed to archive to esmond: 400 Invalid JSON returned, rtejos, 02/02/2018
- Re: [perfsonar-user] Failed to archive to esmond: 400 Invalid JSON returned, Andrew Lake, 02/02/2018
Archive powered by MHonArc 2.6.19.