search

AICoE / prometheus-anomaly-detector

A newer more updated version of the prometheus anomaly detector (https://github.com/AICoE/prometheus-anomaly-detector-legacy)
GNU General Public License v3.0
597 stars 151 forks source link

IndexError: list index out of range #114

Closed DirkFries closed 3 years ago

DirkFries commented 4 years ago

Hi @all,

I run several PAD instances with different configuration on different tcp ports as a standalone process, started by systemd. Basically everything works fine. But from time to time a process gets this error:

2020-03-11T08:46:03.421065+01:00 host pad[1761]: HTTPServerRequest(protocol='http', host='192.168.1.2:8088', method='GET', uri='/metrics', version='HTTP/1.1', remote_ip='192.168.1.1') 2020-03-11T08:46:03.421204+01:00 host pad[1761]: Traceback (most recent call last): 2020-03-11T08:46:03.421327+01:00 host pad[1761]: File "/usr/lib64/python3.6/site-packages/tornado/web.py", line 1699, in _execute 2020-03-11T08:46:03.421459+01:00 host pad[1761]: result = await result 2020-03-11T08:46:03.421570+01:00 host pad[1761]: File "app.py", line 78, in get 2020-03-11T08:46:03.421684+01:00 host pad[1761]: )[0] 2020-03-11T08:46:03.421806+01:00 host pad[1761]: IndexError: list index out of range

In such a case this error message occurs in the log every minute and no new values are beeing predicted. The reoccuring messages and missing values go on until I notice the problem. If I restart the process everythin works fine again.

My firstg assumption was, that for some reason the Prometheus Server does not answer for some time, but in this case the problem should appear with all my PAD processes and the problem should vanish as soon as the Prometheus Server answers again.

So - unforunaly I have no idea where to start with a troubleshoot.

Has anyone experienced the same error or any idea what might cause this?

Thanks a lot !

Bye, Dirk

sesheta commented 3 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

sesheta commented 3 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

sesheta commented 3 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

sesheta commented 3 years ago

@sesheta: Closing this issue.

In response to [this](https://github.com/AICoE/prometheus-anomaly-detector/issues/114#issuecomment-968058604): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.