[Bug]: Docker 4.2.0.0 restart failed.

[derecknowayback]

When i try to start docker container with version 4.2.0.0, it failed.

2023-11-28 22:03:14 [WARN] failed to start 127.0.0.1 obagent
2023-11-28 22:03:14 [ERROR] obagent start failed
2023-11-28 22:03:14 Wait for observer init ok
2023-11-28 22:03:14 +---------------------------------------------+
2023-11-28 22:03:14 |                   observer                  |
2023-11-28 22:03:14 +-----------+---------+------+-------+--------+
2023-11-28 22:03:14 | ip        | version | port | zone  | status |
2023-11-28 22:03:14 +-----------+---------+------+-------+--------+
2023-11-28 22:03:14 | 127.0.0.1 | 4.2.0.0 | 2881 | zone1 | ACTIVE |
2023-11-28 22:03:14 +-----------+---------+------+-------+--------+
2023-11-28 22:03:14 obclient -h127.0.0.1 -P2881 -uroot -Doceanbase -A
2023-11-28 22:03:14 
2023-11-28 22:03:14 See https://www.oceanbase.com/product/ob-deployer/error-codes .
2023-11-28 22:03:14 Trace ID: d137ee02-8df6-11ee-a930-0242ac110002
2023-11-28 22:03:14 If you want to view detailed obd logs, please run: obd display-trace d137ee02-8df6-11ee-a930-0242ac110002
boot failed!2:03:14 

[derecknowayback]

@hnwyllmm plz have a look

[hnwyllmm]

It seems the obagent component in the 4.2.0 docker image use a wrong config file.
@LINxiansheng Please do a double check and upload a new docker image if need.

[derecknowayback]

It seems the obagent component in the 4.2.0 docker image use a wrong config file. @LINxiansheng Please do a double check and upload a new docker image if need.

thx! It happens when I try to restart the docker container. It was perfect when I first created the container, but after shutdown docker engine and tried to reboot, it failed.

[lyhkk]

@hnwyllmm I met the exactly same question when i try to restart my container with version 4.2.1. Thank for your attention.

[derecknowayback]

@hnwyllmm do u have any idea about this issue? Like some related doc ? I am about to fix this, plz assign it to me.

[hnwyllmm]

@hnwyllmm do u have any idea about this issue? Like some related doc ? I am about to fix this, plz assign it to me.

�Sorry. I have no idea about it now. If you'd like to fix this, could you please show us your solution first? And thanks very much for that.

[derecknowayback]

@hnwyllmm do u have any idea about this issue? Like some related doc ? I am about to fix this, plz assign it to me.

�Sorry. I have no idea about it now. If you'd like to fix this, could you please show us your solution first? And thanks very much for that.

aha, ok. I am working on it. BTW: Do u guys have any plan to support higher version ob for arm64 ?For arm64 arch, I did't see any docker-image version higher than 4.2.0.0.

[hnwyllmm]

Now there are already have docker-images on arm64:

[derecknowayback]

Now there are already have docker-images on arm64:

Thanks a lot!

[adamtang79]

Is this one fixed? I had this container setup yesterday and it can't survive a restart.

[XHXJ]

Is anyone still working on it?

When you restart the docker container, or restart the computer,oceanbase will not start, it was fine the first time it ran. This problem occurs as soon as the container restarts after a second stop.

Docker Desktop 4.25.2 (129061)

oceanbase/oceanbase-ce latest fbf1216b8fb4

2023-12-21 10:12:57 find obd deploy information, skip configuring...
2023-12-21 10:12:57 start ob cluster ...
2023-12-21 10:12:57 Get local repositories ok
2023-12-21 10:12:57 Search plugins ok
2023-12-21 10:12:57 Open ssh connection ok
2023-12-21 10:12:58 Load cluster param plugin ok
2023-12-21 10:12:58 Cluster status check ok
2023-12-21 10:12:58 Check before start observer ok
2023-12-21 10:12:58 [WARN] OBD-1011: (172.17.0.5) The recommended value of fs.aio-max-nr is 1048576 (Current value: 65536)
2023-12-21 10:12:58 [WARN] OBD-1007: (172.17.0.5) The recommended number of core file size is unlimited (Current value: 0)
2023-12-21 10:12:58 [WARN] OBD-1007: (172.17.0.5) The recommended number of stack size is unlimited (Current value: 8192)
2023-12-21 10:12:58 [WARN] OBD-1017: (172.17.0.5) The value of the "vm.max_map_count" must be within [327600, 1310720] (Current value: 262144, Recommended value: 655360)
2023-12-21 10:12:58 
2023-12-21 10:12:58 Check before start obagent ok
2023-12-21 10:12:58 Start observer ok
2023-12-21 10:13:01 observer program health check ok
2023-12-21 10:13:04 Connect to observer ok
2023-12-21 10:13:04 Start obagent ok
2023-12-21 10:13:24 obagent program health check x
2023-12-21 10:13:24 [WARN] failed to start 172.17.0.5 obagent
2023-12-21 10:13:24 [ERROR] obagent start failed
2023-12-21 10:13:24 Wait for observer init ok
2023-12-21 10:13:24 +----------------------------------------------+
2023-12-21 10:13:24 |                   observer                   |
2023-12-21 10:13:24 +------------+---------+------+-------+--------+
2023-12-21 10:13:24 | ip         | version | port | zone  | status |
2023-12-21 10:13:24 +------------+---------+------+-------+--------+
2023-12-21 10:13:24 | 172.17.0.5 | 4.2.1.2 | 2881 | zone1 | ACTIVE |
2023-12-21 10:13:24 +------------+---------+------+-------+--------+
2023-12-21 10:13:24 obclient -h172.17.0.5 -P2881 -uroot -p'123456' -Doceanbase -A
2023-12-21 10:13:24 
2023-12-21 10:13:24 See https://www.oceanbase.com/product/ob-deployer/error-codes .
2023-12-21 10:13:24 Trace ID: 754f7008-9fa6-11ee-a059-0242ac110005
2023-12-21 10:13:24 If you want to view detailed obd logs, please run: obd display-trace 754f7008-9fa6-11ee-a059-0242ac110005
boot failed!0:13:24

[adamtang79]

I found as long as I turn off the docker container before shutdown/restart OS(windows). Next time if startup failed, just try a few times and it will startup successfully. I had tried on not turn off docker container and restart/shutdown OS and 10 times startup were failed.

[XHXJ]

Now there are already have docker-images on arm64:

Thanks a lot!

Hello, is this issue still being fixed?