oceanbase / oceanbase/docker-images
[Bug]: Startup error
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 11
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
docker startup boot success!
connector error
sh-4.4# obclient -uroot -P2881
ERROR 2002 (HY000): Can't connect to local OceanBase server through socket '/app/mariadb/mysql.sock' (2)
Environment
docker
Fast reproduce steps
Startup script:
docker run -p 2881:2881 \
-p 2882:2882 \
--name oceanbase-cdc \
-e MODE=mini \
-e OB_SYS_PASSWORD=123456 \
-e OB_DATAFILE_SIZE=2G \
-e OB_LOG_DISK_SIZE=4G \
oceanbase/oceanbase-ce:4.2.1.6-106000012024042515
log:
find obd deploy information, skip configuring...
start ob cluster ...
Get local repositories ok
Search plugins ok
Load cluster param plugin ok
Open ssh connection x
[ERROR] OBD-1013: root@172.17.0.3 connect failed: time out
Trace ID: ba6d1590-cd8c-11ef-9636-0242ac110002
If you want to view detailed obd logs, please run: obd display-trace ba6d1590-cd8c-11ef-9636-0242ac110002
boot success!
docker container IP address:
sh-4.4# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
38: eth0@if39: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:ac:11:00:02 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 172.17.0.2/16 brd 172.17.255.255 scope global eth0
valid_lft forever preferred_lft forever
Expected behavior
No response
Actual behavior
No response
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with the provided docker run command, then inspect the startup log and the OBD trace using the suggested obd display-trace command. Check why the startup script reports boot success after the OBD connection timeout; done means the container starts the OceanBase server and obclient -uroot -P2881 connects successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- databases, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100