Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Omni not passing token? #4

Open
spanko opened this issue Oct 13, 2021 · 2 comments
Open

Omni not passing token? #4

spanko opened this issue Oct 13, 2021 · 2 comments

Comments

@spanko
Copy link

spanko commented Oct 13, 2021

this is great - I did EXACTLY what you did and setup Prometheus and Grafana and nearly killed my 4-node Rpi cluster. When I set everything up, I ended up seeing in the omni pod logs this error:

                omni
                return self.request("POST", url,
                omni
                File "/usr/local/lib/python3.8/site-packages/influxdb_client/rest.py", line 250, in request
                omni
                raise ApiException(http_resp=r)
                omni
                influxdb_client.rest.ApiException: (401)
                omni
                Reason: Unauthorized

There is a corresponding error in influxdb:

              influxdb
              ts=2021-10-13T17:10:18.772914Z lvl=info msg=Unauthorized log_id=0XAaFye0000 error="token required"

I've triple-checked, and tried a couple of different kinds of tokens. Have you seen any common reasons for this? Thanks in advance for any help, if I can end up helping here I'll do so but I'm pretty rusty.

@spanko spanko closed this as completed Oct 13, 2021
@spanko spanko reopened this Oct 13, 2021
@spanko
Copy link
Author

spanko commented Oct 13, 2021

I thought I had this fixed but using the service name instead of the URL to influxdb was just failing silently (eventually the omni log caught up.) I'll keep playing with it, but any pointers would be welcome!

@mattogodoy
Copy link
Owner

Hi!
Something like this happened to me also after an electricity brownout that restarted my servers. The problem was the InfluxDB token. I just deleted and created it again (following the steps in the README file) and it came back to life again. I don't know if it was a bug in InfluxDB or what.

Another important piece of information: When you change the token, you have to update the ConfigMap with the new value, but bear in mind that changing the ConfigMap does not update the existing pods. The easiest way is to manually delete the omni pods so they will be automatically re-created using the new config data.

Hope you can find the problem! 🤞🏻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants