search

bitnami / charts

Bitnami Helm Charts
https://bitnami.com
Other
8.97k stars 9.2k forks source link

[bitnami/mongodb] I get connection error when using configmap #24862

Closed apinizer1 closed 6 months ago

apinizer1 commented 6 months ago

Name and Version

bitnami/mongodb

What architecture are you using?

arm64

What steps will reproduce the bug?

Hello I can install it without configmap. But when I use configmap to add data, I get the error shown in the image.

1 2

What is the expected behavior?

If I do not use configmap, the installation is successful without any errors.

mongodb 21:16:08.08 INFO  ==> Advertised Hostname: 192.168.1.32
mongodb 21:16:08.08 INFO  ==> Advertised Port: 30000
mongodb 21:16:08.10 INFO  ==> Pod name matches initial primary pod name, configuring node as a primary
mongodb 21:16:08.12
mongodb 21:16:08.12 Welcome to the Bitnami mongodb container
mongodb 21:16:08.13 Subscribe to project updates by watching https://github.com/bitnami/containers
mongodb 21:16:08.14 Submit issues and feature requests at https://github.com/bitnami/containers/issues
mongodb 21:16:08.14
mongodb 21:16:08.14 INFO  ==> ** Starting MongoDB setup **
mongodb 21:16:08.17 INFO  ==> Validating settings in MONGODB_* env vars...
mongodb 21:16:08.23 INFO  ==> Initializing MongoDB...
mongodb 21:16:08.32 INFO  ==> Enabling authentication...
mongodb 21:16:08.33 INFO  ==> Deploying MongoDB with persisted data...
mongodb 21:16:08.33 INFO  ==> Writing keyfile for replica set authentication...
mongodb 21:16:08.43 INFO  ==> ** MongoDB setup finished! **

mongodb 21:16:08.46 INFO  ==> ** Starting MongoDB **

What do you see instead?

mongodb 20:54:27.92 INFO  ==> Advertised Hostname: 192.168.1.32
mongodb 20:54:27.93 INFO  ==> Advertised Port: 30000
mongodb 20:54:27.93 INFO  ==> Pod name matches initial primary pod name, configuring node as a primary
mongodb 20:54:27.95
mongodb 20:54:27.96 Welcome to the Bitnami mongodb container
mongodb 20:54:27.96 Subscribe to project updates by watching https://github.com/bitnami/containers
mongodb 20:54:27.96 Submit issues and feature requests at https://github.com/bitnami/containers/issues
mongodb 20:54:27.97
mongodb 20:54:27.97 INFO  ==> ** Starting MongoDB setup **
mongodb 20:54:28.00 INFO  ==> Validating settings in MONGODB_* env vars...
mongodb 20:54:28.05 INFO  ==> Initializing MongoDB...
mongodb 20:54:28.12 INFO  ==> Enabling authentication...
mongodb 20:54:28.14 INFO  ==> Deploying MongoDB with persisted data...
mongodb 20:54:28.14 INFO  ==> Writing keyfile for replica set authentication...
mongodb 20:54:28.24 INFO  ==> Loading user's custom files from /docker-entrypoint-initdb.d ...
MongoNetworkError: connect ECONNREFUSED 192.168.1.32:27017
Current Mongosh Log ID: 660dc2094f6ae9349f6d865b
Connecting to:          mongodb://<credentials>@192.168.1.32:27017/?directConnection=true&appName=mongosh+1.5.0
MongoNetworkError: connect ECONNREFUSED 192.168.1.32:27017
mongodb 20:54:33.27 INFO  ==> Stopping MongoDB...
carrodher commented 6 months ago

The issue may not be directly related to the Bitnami container image or Helm chart, but rather to how the application is being utilized or configured in your specific environment.

Having said that, if you think that's not the case and are interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.

If you have any questions about the application itself, customizing its content, or questions about technology and infrastructure usage, we highly recommend that you refer to the forums and user guides provided by the project responsible for the application or technology.

With that said, we'll keep this ticket open until the stale bot automatically closes it, in case someone from the community contributes valuable insights.

github-actions[bot] commented 6 months ago

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

github-actions[bot] commented 6 months ago

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.