-
Notifications
You must be signed in to change notification settings - Fork 8
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
Deploying as a cloud foundry app: out of available brokers #24
Comments
Kafka Version: 2.1.0 I too am seeing this happen after what appears to be a successful app startup. The app runs for about 5 minutes and then the following:
There are no firewalls in front of the kafka instance. In addition, none of the topics in the config.toml get created. I am assuming this is do to the broker never getting reached. Any help here would be greatly appreciated. |
Maybe found the answer here. I modified the cli.go script to log the username and subscription id and got the following:
Which tells me that the app is not recognizing my config.toml file, or is not using it. |
DefaultCfgPath, in the cli.go script, points at the .toml file used by the app. Turns out that config.toml is not the default, but the example toml file is. I changed this to the location of my config.toml file and now get the correct settings in the log. Hope this helps. |
The README file mentions this project can be installed as a cloud foundry app. So, I wanted to do exactly that, I already have the kafka-boshrelease and kafka-service-broker-boshrelease deployed, and the error I'm getting is:
Can anyone route me to a working example :)?
The text was updated successfully, but these errors were encountered: