Web errors #224
Comments
|
@gazzerman2 Dispatch's plugin manager is trying to find the plugin for metrics using a slug, but it can't because it's not defined and the default is |
|
Also, looks like you haven't set a value for |
|
Eventually yes, but with metrics specifically it shouldn't be an issue today: https://github.com/Netflix/dispatch/blob/develop/src/dispatch/metrics.py#L14 @gazzerman2 do you have anything in your config for |
|
Thanks guys, I didn't have |
|
Added in |
|
The Web is also throwing a 500 against this API
The second 500 as you can see is the metrics one we have an issue with. |
|
Ah, forecast metric won't work unless you have fbprophet dependency installed (we're working on removing it as its terrible to install). Regarding the first error, I wouldn't expect you to set anything for I would ask you add a print here: |
|
If I exec into the web container and run a |
|
@gazzerman2 I set the value to |
|
@gazzerman2 I would try to unset that envvar entirely, my guess is thatsince you have double quoting that the value is being set to |
|
Will try that and get back, thanks for the help @kevgliss |
|
OK these are now fixed, now onto my next web issue Incidents won't load due to a 401 auth issue
Data is present Do I need to have Authentication enabled just to look at incidents? @kevgliss |
|
@mvilanova have you any idea on the above? Thanks! |
|
@gazzerman2 you can disable auth by setting |
|
Same with
|
|
@gazzerman2 I think this should be fixed by #250 |
|
Unfortunately not |
|
@kevgliss and @mvilanova Steps done:
You get the picture, 401's everywhere still Any tips is much appreciated. Thanks! |
|
I think you are setting the wrong var in your env. You have: It should be: If you found the other string somewhere in the documentation let us know and we'll get that fixed. |
|
Thanks a lot, I got it from @mvilanova ;-)
|
|
OK so I modified the .env file today to fix
Having seen that I then said, OK it didn't like nothing set so I will set it to the default from here Line 32 in deadf86 So i set DISPATCH_AUTHENTICATION_PROVIDER_SLUG=dispatch-auth-provider-basic and rebuilt but I got
@kevgliss FYI. I am still blocked from doing anything on the webUI so I can test this out |
|
When is the last time you ran pip install on the project? It can't find the basic auth plugin:
I would make sure you re-install the application every time there is new code (which on the develop branch is daily). |
|
Hi @kevgliss I was under the impression the install.sh pulls and builds the latest docker images, I assumed the dockerfile would do any pip installs of packages it needed? Daily, I clear all containers, volumes and images, and run the I also git pull dispatch-docker when it changes. So are you saying I need to then update the python packages manually? OR Does the |
|
It will automatically pull from the master branch, but the master branch does not have the basic I'm a bit of a loss as to how you're getting code from the develop branch; if you do truly have the newest version of dispatch docker I would double-check this line: I just walked through a clean install (no prior containers, get pull on dispatch-docker |
|
Thanks @kevgliss I checked that line and I was set to It fails to manually create Also |
|
@gazzerman2 can you first create a document and then link it to the incident type when you create the incident type, and let us know if you still see the error? We may need to make some code changes, as it seems like things need to be created in a very specific order in order to work. I think the second error is related to the first one, because you're not providing an incident type when you create the incident. |
|
Thanks @mvilanova |
|
@gazzerman2 do you have documents with empty names and weblinks? If so, can you delete them? |
|
Nope it was a fresh install so no other documents. Thanks for all the help folks. |
|
Hmm, ok. I'll try to see if I can repro it locally and get back to you. |
|
@gazzerman2 I wasn't able to repro locally. Here's what I did:
Please, try again and let me know! |
|
@mvilanova thanks for coming back.
|
|
I'm not able to reproduce number 2 locally. The error means that both the weblink and name for one of the documents in the database are |
|
Pulled a new version, deleted everything and testing now. |
|
@mvilanova - So definitely looking better, thank you!
Env: New everything, docker-dispach also, no DB dump added this time.
In my .env I have |
|
@gazzerman2 nice, almost there! Can you try setting the env var without wrapping the value with |
|
Will do, Thanks a lot, yeah I just spotted it now with single and doubles. |
|
@mvilanova All above works as before but still create Incident fails on a 500
I wonder does it need to have auth enabled to create an incident? |
|
Dispatch uses the |
|
Thanks @mvilanova I have I followed the doc for Slack and have bot which I added in the info below for. |
|
Does the Slack app have the scopes listed here? Try setting the env vars without |
|
Yes, removing the quotes may help. |
|
@mvilanova I did run through that and set all the scopes but will double check it again tomorrow. |
|
I have some config work to do on Slack but given the web issues are now all resolved I will close this out and open a fresh one on Slack related issues as I find them. Thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Unable to submit an incident, web container is throwing this, any help much appreciated.
What's the keyerror?
The text was updated successfully, but these errors were encountered: