You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@iotdb.apache.org by GitBox <gi...@apache.org> on 2022/09/04 11:06:30 UTC
[GitHub] [iotdb] Fiekers opened a new issue, #7229: confignode server: ConfigurationException: Parameter internal_address can not be 192.168.1.41, please set to: 0.0.0.0
Fiekers opened a new issue, #7229:
URL: https://github.com/apache/iotdb/issues/7229
**Describe the bug**
Configuring internal_address as the host ip program cannot run，and if the configuration ip is 0.0.0.0, when the service is the leader, the datanode cannot join the cluster.
**To Reproduce**
Steps to reproduce the behavior:
1. confignode config
internal_address=192.168.1.41
target_config_nodes=192.168.1.41:22277,192.168.1.42:22277,192.168.1.43:22277
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: reviews-unsubscribe@iotdb.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [iotdb] github-actions[bot] commented on issue #7229: confignode server: ConfigurationException: Parameter internal_address can not be 192.168.1.41, please set to: 0.0.0.0
Posted by GitBox <gi...@apache.org>.
github-actions[bot] commented on issue #7229:
URL: https://github.com/apache/iotdb/issues/7229#issuecomment-1236312911
Hi, this is your first issue in IoTDB project. Thanks for your report. Welcome to join the community!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: reviews-unsubscribe@iotdb.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org