<@U03QKFE9V6W>
```docker run -p 9030:9030 -p 803...
# questions-and-troubleshootinge
Evangelos Mouroutsos
05/02/2026, 2:16 PM@Rocky
Copy code
docker run -p 9030:9030 -p 8030:8030 -p 8040:8040 -itd --name quickstart starrocks/allin1-ubuntu Copy code
****************************************************************************************************
* ________ _________ ________ ________ ________ ________ ________ ___ __ ________
* |\ ____\|\___ ___\\ __ \|\ __ \|\ __ \|\ __ \|\ ____\|\ \|\ \ |\ ____\
* \ \ \___|\|___ \ \_\ \ \|\ \ \ \|\ \ \ \|\ \ \ \|\ \ \ \___|\ \ \/ /|\ \ \___|_
* \ \_____ \ \ \ \ \ \ __ \ \ _ _\ \ _ _\ \ \\\ \ \ \ \ \ ___ \ \_____ \
* \|____|\ \ \ \ \ \ \ \ \ \ \ \\ \\ \ \\ \\ \ \\\ \ \ \____\ \ \\ \ \|____|\ \
* ____\_\ \ \ \__\ \ \__\ \__\ \__\\ _\\ \__\\ _\\ \_______\ \_______\ \__\\ \__\____\_\ \
* |\_________\ \|__| \|__|\|__|\|__|\|__|\|__|\|__|\|_______|\|_______|\|__| \|__|\_________\
* \|_________| \|_________|
*
* ________ ___ ___ ___ ________ _____
* |\ __ \|\ \ |\ \ |\ \|\ ___ \ / __ \
* \ \ \|\ \ \ \ \ \ \ \ \ \ \ \\ \ \|\/_|\ \
* \ \ __ \ \ \ \ \ \ \ \ \ \ \\ \ \|/ \ \ \
* \ \ \ \ \ \ \____\ \ \____\ \ \ \ \\ \ \ \ \ \
* \ \__\ \__\ \_______\ \_______\ \__\ \__\\ \__\ \ \__\
* \|__|\|__|\|_______|\|_______|\|__|\|__| \|__| \|__|
*
****************************************************************************************************
StarRocks [(Blazing Fast)]> _
2026-05-02 14:15:24+00:00 INFO running in shared_nothing mode ...
2026-05-02 14:15:24,431 INFO Set uid to user 0 succeeded
2026-05-02 14:15:24,437 INFO RPC interface 'supervisor' initialized
2026-05-02 14:15:24,438 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2026-05-02 14:15:24,438 INFO supervisord started with pid 7
2026-05-02 14:15:25,441 INFO spawned: 'beservice' with pid 520
2026-05-02 14:15:25,443 INFO spawned: 'director' with pid 521
2026-05-02 14:15:25,450 INFO spawned: 'feproxy' with pid 522
2026-05-02 14:15:25,457 INFO spawned: 'feservice' with pid 524
2026-05-02 14:15:25+00:00 INFO checking if need to perform auto registring Backend ...
2026-05-02 14:15:25+00:00 INFO checking if FE service query port:9030 is alive or not ...
2026-05-02 14:15:25+00:00 WARN FE service query port:9030 is NOT alive yet!
2026-05-02 14:15:26,848 WARN exited: beservice (terminated by SIGSEGV; not expected)
2026-05-02 14:15:27+00:00 WARN FE service query port:9030 is NOT alive yet!
2026-05-02 14:15:28,730 INFO spawned: 'beservice' with pid 2152
2026-05-02 14:15:29+00:00 WARN FE service query port:9030 is NOT alive yet!
2026-05-02 14:15:29,730 WARN exited: beservice (terminated by SIGSEGV; not expected)
2026-05-02 14:15:30,732 INFO success: director entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
2026-05-02 14:15:30,732 INFO success: feproxy entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
2026-05-02 14:15:30,732 INFO success: feservice entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
2026-05-02 14:15:31+00:00 WARN FE service query port:9030 is NOT alive yet!
2026-05-02 14:15:31,733 INFO spawned: 'beservice' with pid 2670
2026-05-02 14:15:32,863 WARN exited: beservice (terminated by SIGSEGV; not expected)
2026-05-02 14:15:33+00:00 WARN FE service query port:9030 is NOT alive yet!
2026-05-02 14:15:35+00:00 INFO FE service query port:9030 is alive!
2026-05-02 14:15:35+00:00 INFO generate my.cnf file ...
2026-05-02 14:15:35+00:00 INFO check if need to add BE into FE service ...
2026-05-02 14:15:35,871 INFO spawned: 'beservice' with pid 3810
2026-05-02 14:15:36+00:00 INFO Add BE(127.0.0.1:9050) into FE service ...
2026-05-02 14:15:36,578 WARN exited: beservice (terminated by SIGSEGV; not expected)
2026-05-02 14:15:36,615 INFO gave up: beservice entered FATAL state, too many start retries too quickly
2026-05-02 14:15:36+00:00 INFO BE service already added into FE service ...
2026-05-02 14:15:36+00:00 INFO cluster initialization DONE!
2026-05-02 14:15:36+00:00 INFO wait a few seconds for BE's heartbeat ...
2026-05-02 14:15:46+00:00 INFO StarRocks Cluster information details:
*************************** 1. row ***************************
Id: 2
Name: 127.0.0.1_9010_1777731327822
IP: 127.0.0.1
EditLogPort: 9010
HttpPort: 8030
QueryPort: 9030
RpcPort: 9020
Role: LEADER
ClusterId: 1097874592
Join: true
Alive: true
ReplayedJournalId: 11
LastHeartbeat: 2026-05-02 22:15:44
IsHelper: true
ErrMsg:
StartTime: 2026-05-02 22:15:34
Version: 4.1.0-4ee68c0
*************************** 1. row ***************************
BackendId: 10001
IP: 127.0.0.1
HeartbeatPort: 9050
BePort: -1
HttpPort: -1
BrpcPort: -1
LastStartTime: NULL
LastHeartbeat: NULL
Alive: false
SystemDecommissioned: false
ClusterDecommissioned: false
TabletNum: 0
DataUsedCapacity: 0.000 B
AvailCapacity: 1.000 B
TotalCapacity: 0.000 B
UsedPct: 0.00 %
MaxDiskUsedPct: 0.00 %
ErrMsg:
Version:
Status: {"lastSuccessReportTabletsTime":"N/A"}
DataTotalCapacity: 0.000 B
DataUsedPct: 0.00 %
CpuCores: 0
MemLimit: 0.000B
NumRunningQueries: 0
MemUsedPct: 0.00 %
CpuUsedPct: 0.0 %
DataCacheMetrics: N/A
Location:
StatusCode: CONNECTING
2026-05-02 14:15:46+00:00 INFO
2026-05-02 14:15:46+00:00 INFO
2026-05-02 14:15:46+00:00 INFO * IMPORTANT NOTICE!
If FE/BE state needs to be persisted, please be sure the following directories are mounted:
* FE service meta: /data/deploy/starrocks/fe/meta
* BE service storage: /data/deploy/starrocks/be/storage
2026-05-02 14:15:46+00:00 INFO
2026-05-02 14:15:46+00:00 INFO FE mysql query port: 9030
2026-05-02 14:15:46+00:00 INFO FE http service port: 8080
2026-05-02 14:15:46+00:00 INFO
2026-05-02 14:15:46+00:00 INFO Enjoy the journey to StarRocks blazing-fast lake-house engine!
2026-05-02 14:15:46+00:00 WARN has 1 services into non-RUNNING status!
2026-05-02 14:15:46+00:00 WARN beservice FATAL Exited too quickly (process log may have details)
director RUNNING pid 521, uptime 0:00:21
feproxy RUNNING pid 522, uptime 0:00:21
feservice RUNNING pid 524, uptime 0:00:21
2026-05-02 14:15:52+00:00 WARN has 1 services into non-RUNNING status!
2026-05-02 14:15:52+00:00 WARN beservice FATAL Exited too quickly (process log may have details)
director RUNNING pid 521, uptime 0:00:27
feproxy RUNNING pid 522, uptime 0:00:27
feservice RUNNING pid 524, uptime 0:00:27
2026-05-02 14:15:57+00:00 WARN has 1 services into non-RUNNING status!
2026-05-02 14:15:57+00:00 WARN beservice FATAL Exited too quickly (process log may have details)
director RUNNING pid 521, uptime 0:00:32
feproxy RUNNING pid 522, uptime 0:00:32
feservice RUNNING pid 524, uptime 0:00:32
2026-05-02 14:16:02+00:00 WARN has 1 services into non-RUNNING status!
2026-05-02 14:16:02+00:00 WARN beservice FATAL Exited too quickly (process log may have details)
director RUNNING pid 521, uptime 0:00:37
feproxy RUNNING pid 522, uptime 0:00:37
feservice RUNNING pid 524, uptime 0:00:37
2026-05-02 14:16:07+00:00 WARN has 1 services into non-RUNNING status!
2026-05-02 14:16:07+00:00 WARN beservice FATAL Exited too quickly (process log may have details)
director RUNNING pid 521, uptime 0:00:42
feproxy RUNNING pid 522, uptime 0:00:42
feservice RUNNING pid 524, uptime 0:00:42
2026-05-02 14:16:12+00:00 WARN has 1 services into non-RUNNING status!
2026-05-02 14:16:12+00:00 WARN beservice FATAL Exited too quickly (process log may have details)
director RUNNING pid 521, uptime 0:00:47
feproxy RUNNING pid 522, uptime 0:00:47
feservice RUNNING pid 524, uptime 0:00:47
2026-05-02 14:16:17+00:00 WARN has 1 services into non-RUNNING status!
2026-05-02 14:16:17+00:00 WARN beservice FATAL Exited too quickly (process log may have details)
director RUNNING pid 521, uptime 0:00:52
feproxy RUNNING pid 522, uptime 0:00:52
feservice RUNNING pid 524, uptime 0:00:52
2026-05-02 14:16:22+00:00 WARN has 1 services into non-RUNNING status!
2026-05-02 14:16:22+00:00 WARN beservice FATAL Exited too quickly (process log may have details)
director RUNNING pid 521, uptime 0:00:57
feproxy RUNNING pid 522, uptime 0:00:57
feservice RUNNING pid 524, uptime 0:00:57
2026-05-02 14:16:27+00:00 WARN has 1 services into non-RUNNING status!
2026-05-02 14:16:27+00:00 WARN beservice FATAL Exited too quickly (process log may have details)
director RUNNING pid 521, uptime 0:01:02
feproxy RUNNING pid 522, uptime 0:01:02
feservice RUNNING pid 524, uptime 0:01:02
2026-05-02 14:16:32+00:00 WARN has 1 services into non-RUNNING status!
2026-05-02 14:16:32+00:00 WARN beservice FATAL Exited too quickly (process log may have details)
director RUNNING pid 521, uptime 0:01:07
feproxy RUNNING pid 522, uptime 0:01:07
feservice RUNNING pid 524, uptime 0:01:07
2026-05-02 14:16:38+00:00 WARN has 1 services into non-RUNNING status!
2026-05-02 14:16:38+00:00 WARN beservice FATAL Exited too quickly (process log may have details)
director RUNNING pid 521, uptime 0:01:13
feproxy RUNNING pid 522, uptime 0:01:13
feservice RUNNING pid 524, uptime 0:01:13
2026-05-02 14:16:43+00:00 WARN has 1 services into non-RUNNING status!
2026-05-02 14:16:43+00:00 WARN beservice FATAL Exited too quickly (process log may have details)
director RUNNING pid 521, uptime 0:01:18
feproxy RUNNING pid 522, uptime 0:01:18
feservice RUNNING pid 524, uptime 0:01:18
2026-05-02 14:16:48+00:00 WARN has 1 services into non-RUNNING status!
2026-05-02 14:16:48+00:00 WARN beservice FATAL Exited too quickly (process log may have details)
director RUNNING pid 521, uptime 0:01:23
feproxy RUNNING pid 522, uptime 0:01:23
feservice RUNNING pid 524, uptime 0:01:23