Closed anclrii closed 3 years ago
Looks like it's confirmed as a storagenode bug on the 1st day of the month with the latest version(s). The exporter should be robust enough to cope with this anyway in case the bug isn't fixed or is re-introduced in the future.
https://forum.storj.io/t/what-is-it-error-console-endpoint-failed-to-encod/11513/8
This is happening for me too:
Traceback (most recent call last):
File "./storj-exporter.py", line 235, in <module>
REGISTRY.register(StorjCollector())
File "/usr/local/lib/python3.7/site-packages/prometheus_client/registry.py", line 26, in register
names = self._get_names(collector)
File "/usr/local/lib/python3.7/site-packages/prometheus_client/registry.py", line 66, in _get_names
for metric in desc_func():
File "./storj-exporter.py", line 190, in collect
yield from self.add_payout_metrics()
File "./storj-exporter.py", line 109, in add_payout_metrics
data = self.node_data.get('payout', {}).get('currentMonth', None)
AttributeError: 'NoneType' object has no attribute 'get'
Deploying on Kubernetes this is causing the pod to go into a crash loop because the exporter never comes up.