[Bug] 麒麟系统 docker 部署iotdb，启动后卡在 Checking whether the ports are already occupied...

[FlickerMi]

Search before asking

• I searched in the issues and found nothing similar.

Version

iotdb版本：iotdb:1.3.1-standalone
服务器版本：麒麟V10 x86_64
Linux version 4.19.90-52.22.v2207.ky10.x86_64 (KYLINSOFT@COMPILE.MACHINE) (gcc version 7.3.0 (GCC)) #1 SMP Tue Mar 14 12:19:10CST 2023

Describe the bug and provide the minimal reproduce step

使用docker启动iotdb，docker-compose.yml：

version : '3.8'

services:
  iotdb:
    container_name: iotdb
    image: apache/iotdb:1.3.1-standalone
    restart: always
    hostname: iotdb-service
    ports:
      - "6667:6667"
      - "31999:31999"
      - "8123:8123"
      - "9003:9003"
    volumes:
      - ./data:/iotdb/data
      - ./logs:/iotdb/logs
      - ./conf:/iotdb/conf
    environment:
      - TZ=Asia/Shanghai
      - enable_rest_service=true
      - cn_internal_address=iotdb-service
      - cn_internal_port=10710
      - cn_consensus_port=10720
      - cn_seed_config_node=iotdb-service:10710
      - dn_rpc_address=iotdb-service
      - dn_internal_address=iotdb-service
      - dn_rpc_port=6667
      - dn_mpp_data_exchange_port=10740
      - dn_schema_region_consensus_port=10750
      - dn_data_region_consensus_port=10760
      - dn_target_config_node_list=iotdb-service:10710
      #- dn_seed_config_node=iotdb-service:10710
    networks:
      - cc-network

networks:
  cc-network:
    external: true

docker compose up -d 后，日志卡在Checking whether the ports are already occupied...，并且容器CPU飙升。

输出日志：

Checking whether the ports are already occupied...

What did you expect to see?

正常启动

What did you see instead?

Checking whether the ports are already occupied...

Anything else?

No response

Are you willing to submit a PR?

• I'm willing to submit a PR!

[HTHou]

试试 dn_target_config_node_list=iotdb-service:10710 恢复成 dn_seed_config_node=iotdb-service:10710 ？

[FlickerMi]

试试 dn_target_config_node_list=iotdb-service:10710 恢复成 dn_seed_config_node=iotdb-service:10710 ？

还是不行，也是卡在Checking whether the ports are already occupied...

还有其它什么方案能帮助排查问题吗？

[HTHou]

https://discourse.pi-hole.net/t/pi-hole-docker-lsof-pni-53-using-100-cpu/47484/5 看到一个类似的 lsof cpu 占用高的情况，试试最后面的这个方法？

[FlickerMi]

@HTHou 已经解决，主要是容器内openfiles的ulimit太高，导致启动iotdb时，lsof命令checkConfigNodePortUsages的时侯挂起了。

解决方法：修改/etc/docker/daemon.json 默认ulimits，设置小点

参考内容：https://unix.stackexchange.com/questions/722948/lsof-is-frozen-inside-the-container

[Dannyshcn]

docker run --ulimit nofile=20000:20000 -d --name my_container my_image 可以避免重启容器服务

[wold9168]

对于使用docker compose的用户，可以考虑将以下设置项加入docker compose相应的服务中：

ulimits:
  nofile:
    soft: 65536
    hard: 65536

我认为最好在上游的文档中就该问题进行更详细的补充说明，同时考虑将该ulimits设置加入到文档中提供的docker-compose.yml中，并用注释加以说明。让有需要的用户自行删去。