Skip to Content.
Sympa Menu

perfsonar-user - [perfsonar-user] Two pscheduler-archiver questions

Subject: perfSONAR User Q&A and Other Discussion

List archive

[perfsonar-user] Two pscheduler-archiver questions


Chronological Thread 
  • From: David Szydloski <>
  • To:
  • Subject: [perfsonar-user] Two pscheduler-archiver questions
  • Date: Thu, 15 Mar 2018 11:59:03 -0500
  • Ironport-phdr: 9a23:yv96thTE4zwUl1bRvfSQa3+UrNpsv+yvbD5Q0YIujvd0So/mwa69bByN2/xhgRfzUJnB7Loc0qyK6/umATRIyK3CmUhKSIZLWR4BhJdetC0bK+nBN3fGKuX3ZTcxBsVIWQwt1Xi6NU9IBJS2PAWK8TW94jEIBxrwKxd+KPjrFY7OlcS30P2594HObwlSizexfb1/IA+qoQnNq8IbnZZsJqEtxxXTv3BGYf5WxWRmJVKSmxbz+MK994N9/ipTpvws6ddOXb31cKokQ7NYCi8mM30u683wqRbDVwqP6WACXWgQjxFFHhLK7BD+Xpf2ryv6qu9w0zSUMMHqUbw5Xymp4qF2QxHqlSgHLSY0/mHZhMJzkaxVvg6uqgdlzILIeoyYLuZycr/fcN4cWGFPXtxRVytEAo6kYYUAFfQBPedFoILgulUPrBu/ChSoBOPo0T9IhX721rA93us8CgHH3QwhEM8KsHTTt9X1N6YSXPurzKnJ0DrDdO9Z1i356IfWaBwuvfaMXbdpfMfX1EIhFBvFg02OpYP/Iz+ZyuEAv3WU4udgSe6ijmEqpx1trjezw8ojlpXFi4YQx13B6yl13po6KNulQ0Bhe9GkCoFftySCOot2XMwiR2ZotT4/yrIcuJ67eDEGyZoixxLDcvCGfJaE7gz/W+qLLjd4g3VleL27hxms60Sv1ur8Vsys3FZLqCpKjMXMu2gT2xPJ9sSLVv5w8lqu1DuPywze7+5JLVwomaXHLpMu3qI8m54WvEnGACP6hln5gLeTdko+++io7+rnYq/hpp+ZL4J7lxr+M6Uum8OiBeQ4NRMOX2ua+emnyr3j/FD2QK5WgfIslqnWrorWKtgcpq68GwNVyJos6w6jDze619QVhWEHI0xfeBKJlIjpPFfOL+riDfumnlSsiylkx+rdM73lA5XNNWTDkKz/cbpn6k5czhYzws5F55JSFL4BPOz/VlXvu9PFEx9qezCzlv7qEttm0YUXQyeSGaKDGKLUrVKS4O8zea+BaJJGliz6Lq0J7uDvgTcCi04Rea6y3ppfPHyjDOVqJ0KCYnvEnNYNCmwDugd4R+vv3g7RGQVPbmq/CvpvrgowD5irWN/O

1) Troubleshooting " 400: Invalid JSON returned " error:

One of the hosts in my mesh is running tests and getting results just fine however its not returning any results to the central management database. Looking at /var/log/pscheduler/pscheduler.log I see 

Mar 15 16:39:23 netperf01-fra1 archiver DEBUG    1349313: Returned JSON from archiver: {u'retry': u'PT60S', u'succeeded': False, u'error': u'400: Invalid JSON returned'}
Mar 15 16:39:23 netperf01-fra1 archiver WARNING  1349313: Failed to archive https://localhost/pscheduler/tasks/52ee426a-3b0d-41df-9b85-e6782633c65f/runs/3a6cb757-b446-4193-bc9e-54c9d321f9ff to esmond: 400: Invalid JSON returned
Mar 15 16:39:23 netperf01-fra1 archiver DEBUG    1349313: Rescheduling for 2018-03-15 16:40:23.310899+00:00
Mar 15 16:39:23 netperf01-fra1 archiver DEBUG    1349313: Thread finished

On the central management VM, is see the following in /var/log/apache2/access.log pertaining to the host having the issues:

dszydloski@sonar-poc:/var/log/apache2$ tail access.log


10.71.8.28 - - [15/Mar/2018:16:44:32 +0000] "POST /esmond/perfsonar/archive/ HTTP/1.1" 201 7103 "-" "python-requests/2.9.1"
10.71.8.28 - - [15/Mar/2018:16:44:32 +0000] "POST /esmond/perfsonar/archive/ HTTP/1.1" 201 7103 "-" "python-requests/2.9.1"

So its reaching the remote server but not making any PUT requests--likely due to the archiver error I guess?

I've been racking my brain isolating local differences between my mesh node setups but haven't been able to find anything pertaining to this issue. Any ideas on what else I can look at to fix this?

2) esmond "fast_mode"?

In the process of troubleshooting 1), I noticed some differences in my different mesh hosts. When I ran "cat /var/log/pscheduler/pscheduler.log | grep 'fast_mode is True'" across the hosts I had some hosts that showed 'fast_mode is True' in the logs but most didn't. It doesn't seem to matter in performance though i'm curious if I should spend time getting these all to report the same way or not.

Thanks!
--
David Szydloski
Core Deployment Engineer
VidScale, Inc.



Archive powered by MHonArc 2.6.19.

Top of Page