[Bug] 在Rocky Linux无法启动

[Clownsw]

Search before asking

• [X] I searched in the issues and found nothing similar.

Version

1.1.0-standalone

Describe the bug and provide the minimal reproduce step

docker run -it -d --name iotdb-server -p 6667:6667 -e TZ=Asia/Shanghai -e LANG=zh_CN.UTF-8 -e cn_internal_address=iotdb-service -e cn_target_config_node_list=iotdb-service:10710 -e cn_internal_port=10710 -e cn_consensus_port=10720 -e dn_rpc_address=iotdb-service -e dn_internal_address=iotdb-service -e dn_target_config_node_list=iotdb-service:10710 -e dn_mpp_data_exchange_port=10740 -e dn_schema_region_consensus_port=10750 -e dn_data_region_consensus_port=10760 -e dn_rpc_port=6667 apache/iotdb:1.1.0-standalone

What did you expect to see?

在ubuntu可以正常启动

root@devops:/home/devops/hertzbeat/script/docker-compose/hertzbeat-iotdb# docker logs compose-iotdb
update dn_internal_address /iotdb/conf/iotdb-datanode.properties
update dn_data_region_consensus_port /iotdb/conf/iotdb-datanode.properties
update cn_target_config_node_list /iotdb/conf/iotdb-confignode.properties
update cn_internal_port /iotdb/conf/iotdb-confignode.properties
update dn_rpc_address /iotdb/conf/iotdb-datanode.properties
update dn_mpp_data_exchange_port /iotdb/conf/iotdb-datanode.properties
update dn_rpc_port /iotdb/conf/iotdb-datanode.properties
update cn_consensus_port /iotdb/conf/iotdb-confignode.properties
update cn_internal_address /iotdb/conf/iotdb-confignode.properties
update dn_schema_region_consensus_port /iotdb/conf/iotdb-datanode.properties
update dn_target_config_node_list /iotdb/conf/iotdb-datanode.properties
Checking whether the ports are already occupied...
---------------------
Starting IoTDB DataNode
---------------------
WARN:
WARN: the value of net.core.somaxconn (=4096) is too small, please set it to a larger value using the following command.
WARN:     sudo sysctl -w net.core.somaxconn=65535
WARN: The original net.core.somaxconn value will be set back when the os reboots.
WARN:
setting local JMX...
Maximum memory allocation pool = 14055MB, initial memory allocation pool = 1200MB
If you want to change this configuration, please check conf/datanode-env.sh.
2024-04-30 11:19:38,706 [main] INFO  o.a.i.d.c.IoTDBDescriptor:157 - Start to read config file file:/iotdb/conf/iotdb-common.properties 
2024-04-30 11:19:38,718 [main] INFO  o.a.i.d.c.IoTDBDescriptor:174 - Start to read config file file:/iotdb/conf/iotdb-datanode.properties 
2024-04-30 11:19:38,809 [main] INFO  o.a.i.d.c.IoTDBDescriptor:1547 - initial allocateMemoryForRead = 4421635276 
2024-04-30 11:19:38,810 [main] INFO  o.a.i.d.c.IoTDBDescriptor:1548 - initial allocateMemoryForWrite = 4421635276 
2024-04-30 11:19:38,811 [main] INFO  o.a.i.d.c.IoTDBDescriptor:1549 - initial allocateMemoryForSchema = 1473878425 
2024-04-30 11:19:38,811 [main] INFO  o.a.i.d.c.IoTDBDescriptor:1550 - initial allocateMemoryForConsensus = 1473878425 
2024-04-30 11:19:38,812 [main] INFO  o.a.i.d.c.IoTDBDescriptor:1674 - allocateMemoryForSchemaRegion = 736939212 
2024-04-30 11:19:38,813 [main] INFO  o.a.i.d.c.IoTDBDescriptor:1677 - allocateMemoryForSchemaCache = 442163527 
2024-04-30 11:19:38,813 [main] INFO  o.a.i.d.c.IoTDBDescriptor:1681 - allocateMemoryForPartitionCache = 147387842 
2024-04-30 11:19:38,814 [main] INFO  o.a.i.d.c.IoTDBDescriptor:1684 - allocateMemoryForLastCache = 147387842 
2024-04-30 11:19:38,860 [main] INFO  o.a.i.t.c.c.TSFileDescriptor:129 - try loading iotdb-common.properties from /iotdb/conf/iotdb-common.properties 
2024-04-30 11:19:38,876 [main] INFO  o.a.i.d.c.IoTDBDescriptor:386 - IoTDB enable memory control: true 
2024-04-30 11:19:38,881 [main] INFO  o.a.i.d.c.IoTDBDescriptor:1298 - MQTT host is not configured, will use dn_rpc_address. 
2024-04-30 11:19:38,979 [main] INFO  o.a.i.db.service.DataNode:145 - IoTDB-DataNode environment variables: 

What did you see instead?

update dn_internal_address /iotdb/conf/iotdb-datanode.properties
update dn_data_region_consensus_port /iotdb/conf/iotdb-datanode.properties
update cn_target_config_node_list /iotdb/conf/iotdb-confignode.properties
update cn_internal_port /iotdb/conf/iotdb-confignode.properties
update dn_rpc_address /iotdb/conf/iotdb-datanode.properties
update dn_mpp_data_exchange_port /iotdb/conf/iotdb-datanode.properties
update dn_rpc_port /iotdb/conf/iotdb-datanode.properties
update cn_consensus_port /iotdb/conf/iotdb-confignode.properties
update cn_internal_address /iotdb/conf/iotdb-confignode.properties
update dn_schema_region_consensus_port /iotdb/conf/iotdb-datanode.properties
update dn_target_config_node_list /iotdb/conf/iotdb-datanode.properties
Checking whether the ports are already occupied...

Anything else?

No response

Are you willing to submit a PR?

• [x] I'm willing to submit a PR!

[github-actions[bot]]

Hi, this is your first issue in IoTDB project. Thanks for your report. Welcome to join the community!

[HTHou]

https://discourse.pi-hole.net/t/pi-hole-docker-lsof-pni-53-using-100-cpu/47484/5 Try this may fix this problem.

[HTHou]

https://github.com/apache/iotdb/issues/13151 社区也有人遇到并解决了类似的问题