-
-
Notifications
You must be signed in to change notification settings - Fork 652
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 #193
Comments
I need a configuration files to help you ! |
sure , image: configuration: | secrets: | extraVolumes: [] extraVolumeMounts: [] service: ingress: paths: [] resources: {} nodeSelector: {} tolerations: [] affinity: {} |
any other configs are needed except the values.yaml ? |
can you send it with formatting, understand yaml without indentation is "impossible" 😄 |
|
As i can see, you must provide the cluster only in Change with this and it must work : configuration: |
kafkahq:
connections:
my-cluster-plain-text:
properties:
bootstrap.servers: "kafkacluster01:9092,kafkacluster02:9092,kafkacluster03:9092"
|
Hi , |
can you connect inside the pods and look at |
|
/app/application-secrets.yml is not exist as per your request to have only one method |
Ok all seems good ... Can you look at this one : #184 Especially adding this to your configuration :
And go to your pods with : |
from Host
|
Inside the POD
|
|
|
you have added this to your configuration files ? endpoints:
env:
enabled: true
sensitive: true if yes, your configuration is not take by micronaut that will be really weird ... Maybe remove in the bootstrap server the list and put only 1 to see if it's better ? |
Yes , i have added above section to configuration. |
Is there a default username and pass ? |
no it's not ok ... |
I am getting this same error, trying to spin up the dev-compose, and even though I have kafka->properties->bootstrap.servers set, kafka client throws exception when accessing kafkahq.
|
@unixunion : you are just trying with the docker-compose-dev.yml ? right ? |
Correct, and I have put a application.yml in the mounted root, and I had to add MICRONAUT_CONFIG_FILES to the compose too. I tried latest tag, master and dev branches. same issue. added this to env for kafkahq service in compose.
I cant seem to get the entire yaml formated into here. pastbin: https://pastebin.com/cgKL85ep
|
in the docker-compose-dev.yml , I commented out the kafkahq and the webpack and then started kafkahq via IntelliJ. I put a debugger on line 97 of KafkaModule.java, and the clusterId passed is EDIT: I see it got the clusterId from a stale URL call. Actually, it seems to be redirected to the non-existent cluster. I hit http://localhost:8080/ and get redirected to http://localhost:8080/docker-kafka-server/topic EDIT: if I hit http://localhost:8080/my-cluster-plain-text/topic direct, I get to a new error regarding my NW setup. will post results soon. |
I think I figured the issue out, it seems that browser cache is the culprit here, because I had a kafkahq deployed in docker in another experiment, there is some contamination of the cache, so when I access "localhost:8080", for some reason I get redirected to the clusterId for the docker-kafka-server. Nuking the cache seems to resolve it. |
Already have also this issue ! |
So this is not really a bug, but perhaps it is needed to add a no-cache header onto the html. I guess @hagay-david-devops has the same problem with cache. |
Hi , |
don't really want to add a no-cache header and let the browser do it's job. |
I'm running against this issue AFTER initial configuration. I'm running AKHQ for two weeks now, it connects to three 3-node clusters. My users are saying that AKHQ is really slow after running for a while. I've just restarted the container after one week of running with no issues. When looking in the log i see the exact same error being logged. Only a restart of the containers flushes stuff. Could this be browser related and if so, what kind of browser tools could I use to help find the root cause? |
I don't think it's a browser issue. Create a new issue with more log. |
In my experience (app 0.20 from helm chart 0.27), the /env endpoint gets only deployed to the "management" port, 28081 by default in the Helm chart. 8080 is the default port for the standard service, and will never get the /env endpoint! |
Hi
also bootstrap.servers is configure right , the log is prompting the following :L
Caused by: org.apache.kafka.common.config.ConfigException: Missing required configuration "bootstrap.servers" which has no default value.
any idea ?
thanks .
The text was updated successfully, but these errors were encountered: