-
-
Notifications
You must be signed in to change notification settings - Fork 659
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
Missing required configuration "bootstrap.servers" which has no default value #230
Comments
Really strange !
Thanks |
It doesn't appear that your container has
I was able to curl from a separate pod in the same namespace. ================================================================== You talk about details of topic that timeout, so you can see the list of topic, not the details page ? Is any others topic working well ? Can you enable the debug mode and send me the full log please ? |
Yes curl is not on KafkaHQ image. |
A link like this one: https://kafkahq.prod.domain.com/kafka/topic, listing topics on the page seems to work. When I try clicking on a debezium topic in general, like this: https://kafkahq.prod.domain.com/kafka/topic/debezium.debezium.releases I get a 504 gateway timeout from nginx and the logs I sent are related. So the second link never works. The logs are from a single cluster and the single topic above. Really just the second link there generated all of the logs I pasted. |
We're facing this issue, too on version 0.15.0. For any curious reason you can click the error away, list topics again and you might be able to see all topics. Unfortunately this behaviour is very annoying. |
Same error here like @alwibrm mentioned. There seems to be error parsing configValue bootstrap.servers some times. |
Using the developer tool I see that API request refers to unidefined cluster and undefined topic (/api/undefined/topic/undefined/partitions). Clicking Consumer Groups and back to Partitions solve the issue. |
Sadly it's happening in an air-gapped environment so I can't capture and export an har file. It happens consistently. |
Hi @tchiotludo, Sorry for the late response. I rather think that this is not a bug in the UI, since the exception states an "500 - Internal Server Error". I was able to reproduce the error, here is the full error message:
|
It must be an ui bug.. look at this comment : #230 (comment) /api/undefined/ so the server look at undefined cluster (that will be not defined) so the ui is looking for an invalid cluster, why I need a full har files to understand where is the ui is doing a wrong request, only a stacktrace from the server will not help. |
@tchiotludo Here a slightly modified HAR file: akhq-har.txt |
Thanks @alwibrm , I see this first request : https://kafkahq.dev.somesystem.mycompany.local/ui/401/topic
|
@tchiotludo This appears immediately after a (successful) login. I don't enter the 401 manually. Is the 401 related to the HTTP status 401 (unauthorized) in any way? Yes, when I switch to a different cluster with way less topics in the same AKHQ instance it's working. When I go back to the first cluster sometimes it's working, sometimes I get this error and sometimes the error described in #137. |
don't know ... |
Okay, login included: akhq-with-login.har.txt |
i had the same issue on 0.16.0 so hopefully issue will gone with the next release |
I think this can be a duplicate of #498 (and #514), and I think it is fixed by #510 in the Any chance to get a new release soon, @tchiotludo? 🙏 We are currently running version |
Hi @tchiotludo, I can not intuitively see how #543 (ProtoBuf integration) fixes the above error? |
@alwibrm : it's not linked, just need that one to release. |
@tchiotludo: thanks for the (insanely fast) clarification. Can you please link the change in the upcoming release that you suspect should fix this issue? |
issue mention by @erikgb must do the trick, only a "undefined" vars pass from the ui |
Ah, now I got it. Thank you! |
Current dev build solves the issue. Thank you! |
I am seeing this error on the latest 0.21.0 release. |
can you provide the full stacktrace ? seems to be weird |
I get the same error when issueing a GET. It seems the api (in contrast to the ui) cannot connect at all |
I'am unable to reproduce the issue, can you create a fresh issue with all the details please? |
Damn...my mistake was that I had a typo in the cluster-name of the api path. Of course it looked for a configured cluster which was not configured. |
@lostiniceland you can create a new ticket yes 👍 |
I'm running a kubernetes Deployment of kafkahq. After I upgraded to kafka 2.4.0, it started timing out when I try accessing topic details of any topic that was created by our debezium plugin. I have the following set as my configuration:
I'm guessing it has to do with the difference in plugin versions, but I don't see anything wrong with the topics when I try accessing them outside of kafkahq.
The text was updated successfully, but these errors were encountered: