为了更快的定位您的问题，请提供以下信息，谢谢
【详述】部署docker版本的starrocks后，修改了root的密码，重启docker后，starrocks无法启动
【背景】启动docker后，进入容器
docker exec -it a171 /bin/bash
登录starrocks的控制台
mysql -P9030 -h127.0.0.1 -uroot --prompt="StarRocks > "
修改密码
set password=password(‘asdas#@#$12M’);
后重启docker
docker restart a171
【业务影响】
starrocks无法正常启动
【StarRocks版本】
Build version: 3.3.4
Commit hash: 56bcf6f
Build type: RELEASE
Build time: 2024-09-29 11:26:17
Build distributor id: ubuntu
Build arch: aarch64
Build user: StarRocks@localhost (Ubuntu 22.04.4 LTS)
Java compile version: openjdk full version “11.0.23+9-post-Ubuntu-1ubuntu122.04.1”
【集群规模】例如：1fe+1be
【机器信息】CPU虚拟核/内存/网卡，例如：16C/32G/千兆
【联系方式】bean_lion@163.com
【附件】
StarRocks [(Blazing Fast)]> _
2024-12-02 03:39:30,775 INFO Set uid to user 0 succeeded
Unlinking stale socket /data/deploy/starrocks/supervisor/supervisor.sock
2024-12-02 03:39:31,080 INFO RPC interface ‘supervisor’ initialized
2024-12-02 03:39:31,080 CRIT Server ‘unix_http_server’ running without any HTTP authentication checking
2024-12-02 03:39:31,081 INFO supervisord started with pid 7
2024-12-02 03:39:32,083 INFO spawned: ‘beservice’ with pid 523
2024-12-02 03:39:32,086 INFO spawned: ‘broker’ with pid 524
2024-12-02 03:39:32,090 INFO spawned: ‘director’ with pid 525
2024-12-02 03:39:32,093 INFO spawned: ‘feproxy’ with pid 528
2024-12-02 03:39:32,096 INFO spawned: ‘feservice’ with pid 531
2024-12-02 03:39:32+00:00 INFO checking if need to perform auto registring Backend and Broker …
2024-12-02 03:39:32+00:00 INFO checking if FE service query port:9030 is alive or not …
2024-12-02 03:39:32+00:00 WARN FE service query port:9030 is NOT alive yet!
2024-12-02 03:39:34+00:00 WARN FE service query port:9030 is NOT alive yet!
2024-12-02 03:39:36+00:00 WARN FE service query port:9030 is NOT alive yet!
2024-12-02 03:39:37,637 INFO success: beservice entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
2024-12-02 03:39:37,637 INFO success: broker entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
2024-12-02 03:39:37,637 INFO success: director entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
2024-12-02 03:39:37,637 INFO success: feproxy entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
2024-12-02 03:39:37,637 INFO success: feservice entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
2024-12-02 03:39:38+00:00 WARN FE service query port:9030 is NOT alive yet!
2024-12-02 03:39:40+00:00 WARN FE service query port:9030 is NOT alive yet!
2024-12-02 03:39:42+00:00 WARN FE service query port:9030 is NOT alive yet!
2024-12-02 03:39:44+00:00 INFO FE service query port:9030 is alive!
2024-12-02 03:39:44+00:00 INFO generate my.cnf file …
2024-12-02 03:39:45+00:00 INFO check if need to add BE into FE service …
2024-12-02 03:39:45+00:00 ERROR Password error, stop retrying!
If the root user password is changed, please re-run the container with ‘-e MYSQL_PWD=<root_password>’
2024-12-02 03:39:45+00:00 ERROR will force shutdown in 15 seconds …
2024-12-02 03:40:00,359 INFO waiting for beservice, broker, director, feproxy, feservice to die
Shut down
2024-12-02 03:40:00,422 INFO exited: director (exit status 1; not expected)
2024-12-02 03:40:01,424 INFO stopped: feservice (exit status 143)
2024-12-02 03:40:01,427 INFO stopped: feproxy (exit status 0)
2024-12-02 03:40:02,429 INFO stopped: broker (terminated by SIGTERM)
2024-12-02 03:40:03,437 INFO stopped: beservice (terminated by SIGKILL)