Closed ghost closed 9 years ago
If you have the latest cyanite, this is most likely this: https://github.com/pyr/cyanite/issues/130
There's a patch proposed for graphite-cyanite. Can you have a look? It could be used as a temporary solution -- there will be a proper fix in pyr/cyanite later.
Hey @brutasse,
thanks for the fast response. Actually the replies belong to me :) What patch are you talking about?
Cheers, Szop
Ah sorry, wrong issue! Patch is here: https://github.com/pyr/cyanite/issues/119#issuecomment-143243827
By the way. After my Apache Graphite-API started to report me 500, I'm still able to query the Cyanite API port on 8080
Cheers, Szop
Yeah, basically the return format for cyanite's /paths
endpoint changed and graphite-cyanite crashes on the new return format. Ideally the cyanite api should be updated to use the old format again but it's easier to have a workaround in graphite-cyanite.
Thanks @brutasse ! I guess this issue can be closed now.
Cheers, Szop
Cool, thanks!
Hello guys,
I have to be honest: I don't know what is causing this problem, so I'm starting here and hope to get a hint or wink into the right direction. My setup look's as following:
Cassandra 2.2 Graphite-API 1.0.1 Cyanite 0.4.5 (pip install cyanite) and also pyr/cynite
Collectd 5.5 Grafana 2.2
netstat is showing all ports that I need:
My tests look as following:
I'm curling the Graphite-API port on 8013, to get all metrics. Of course the Cassandra DB is empty at the beginning:
I'm just getting an [] back. After starting the collector (collectd), my curl's are producing a 500 in the apache access logs and I'm not able to query for data:
Any ideas on that?
Cheers, Szop