Bug: openim docker start #56

lushou · 2023-12-18T01:19:39Z

What happened?

dps_paas_openim-server的日志

Use Docker to start all openim service

Begin to start all openim service scripts

All binaries have been installed in /openim/openim-server/_output/bin/platforms/linux/amd64。
You need to start the following scripts in order: openim-api.sh openim-rpc.sh openim-push.sh openim-msgtransfer.sh openim-msggateway.sh openim-crontask.sh openim-tools.sh

Pre Starting OpenIM services

Preparing to start OpenIM Tools...
Starting ncpu...
Starting PATH: /openim/openim-server/_output/bin/tools/linux/amd64/ncpu...
Specifying config: /openim/openim-server/config
Starting ncpu...
40Starting component...
Starting PATH: /openim/openim-server/_output/bin/tools/linux/amd64/component...
Specifying config: /openim/openim-server/config
Starting component...
Checking components Round 1...
Mysql starts successfully
Mongo starts successfully
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x28 pc=0xe9a32a]

goroutine 1 [running]:
main.exactIP({0xc0001fc7d0?, 0x3b9aca00?})
/openim/openim-server/tools/component/component.go:124 +0x2a
main.checkMinio()
/openim/openim-server/tools/component/component.go:225 +0x2db
main.main()
/openim/openim-server/tools/component/component.go:103 +0x4ce
!!! [1218 09:14:51] Call tree:
!!! [1218 09:14:51] 1: /openim/openim-server/scripts/install//openim-tools.sh:123 openim::tools::start_service(...)
!!! [1218 09:14:51] 2: /openim/openim-server/scripts/install//openim-tools.sh:166 openim::tools::pre-start(...)
!!! Error in /openim/openim-server/scripts/install//openim-tools.sh:106
Error in /openim/openim-server/scripts/install//openim-tools.sh:106. '${cmd}' exited with status 2
Call stack:
1: /openim/openim-server/scripts/install//openim-tools.sh:106 openim::tools::start_service(...)
2: /openim/openim-server/scripts/install//openim-tools.sh:123 openim::tools::pre-start(...)
3: /openim/openim-server/scripts/install//openim-tools.sh:166 main(...)
Exiting with status 1
!!! Error in /openim/openim-server/scripts/start-all.sh:75
Error in /openim/openim-server/scripts/start-all.sh:75. '${TOOLS_START_SCRIPTS_PATH} openim::tools::pre-start' exited with status 1
Call stack:
1: /openim/openim-server/scripts/start-all.sh:75 main(...)
Exiting with status 1
!!! Error in /openim/openim-server/scripts/docker-start-all.sh:31
Error in /openim/openim-server/scripts/docker-start-all.sh:31. '"${OPENIM_ROOT}"/scripts/start-all.sh' exited with status 1
Call stack:
1: /openim/openim-server/scripts/docker-start-all.sh:31 main(...)
Exiting with status 1

Use Docker to start all openim service

Begin to start all openim service scripts

All binaries have been installed in /openim/openim-server/_output/bin/platforms/linux/amd64。
You need to start the following scripts in order: openim-api.sh openim-rpc.sh openim-push.sh openim-msgtransfer.sh openim-msggateway.sh openim-crontask.sh openim-tools.sh

Pre Starting OpenIM services

Preparing to start OpenIM Tools...
Starting ncpu...
Starting PATH: /openim/openim-server/_output/bin/tools/linux/amd64/ncpu...
Specifying config: /openim/openim-server/config
Starting ncpu...
40Starting component...
Starting PATH: /openim/openim-server/_output/bin/tools/linux/amd64/component...
Specifying config: /openim/openim-server/config
Starting component...
Checking components Round 1...
Mysql starts successfully
Mongo starts successfully
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x28 pc=0xe9a32a]

goroutine 1 [running]:
main.exactIP({0xc0001fc7d0?, 0x3b9aca00?})
/openim/openim-server/tools/component/component.go:124 +0x2a
main.checkMinio()
/openim/openim-server/tools/component/component.go:225 +0x2db
main.main()
/openim/openim-server/tools/component/component.go:103 +0x4ce
!!! [1218 09:15:53] Call tree:
!!! [1218 09:15:53] 1: /openim/openim-server/scripts/install//openim-tools.sh:123 openim::tools::start_service(...)
!!! [1218 09:15:53] 2: /openim/openim-server/scripts/install//openim-tools.sh:166 openim::tools::pre-start(...)
!!! Error in /openim/openim-server/scripts/install//openim-tools.sh:106
Error in /openim/openim-server/scripts/install//openim-tools.sh:106. '${cmd}' exited with status 2
Call stack:
1: /openim/openim-server/scripts/install//openim-tools.sh:106 openim::tools::start_service(...)
2: /openim/openim-server/scripts/install//openim-tools.sh:123 openim::tools::pre-start(...)
3: /openim/openim-server/scripts/install//openim-tools.sh:166 main(...)
Exiting with status 1
!!! Error in /openim/openim-server/scripts/start-all.sh:75
Error in /openim/openim-server/scripts/start-all.sh:75. '${TOOLS_START_SCRIPTS_PATH} openim::tools::pre-start' exited with status 1
Call stack:
1: /openim/openim-server/scripts/start-all.sh:75 main(...)
Exiting with status 1
!!! Error in /openim/openim-server/scripts/docker-start-all.sh:31
Error in /openim/openim-server/scripts/docker-start-all.sh:31. '"${OPENIM_ROOT}"/scripts/start-all.sh' exited with status 1
Call stack:
1: /openim/openim-server/scripts/docker-start-all.sh:31 main(...)
Exiting with status 1
-bash: history: write error: Success

dps_paas_openim-chat的日志：
openImChatApiPort service does not start normally, not initiated port is 10008
please check /openim/openim-chat/scripts/../logs/openIM.log
================> Architecture: x86_64
================> BIN_DIR: /openim/openim-chat/scripts/..//openim/openim-chat/scripts/../_output/bin/platforms/linux/amd64
openImChatApiPort service does not start normally, not initiated port is 10008
please check /openim/openim-chat/scripts/../logs/openIM.log
================> Architecture: x86_64
================> BIN_DIR: /openim/openim-chat/scripts/..//openim/openim-chat/scripts/../_output/bin/platforms/linux/amd64
openImChatApiPort service does not start normally, not initiated port is 10008
please check /openim/openim-chat/scripts/../logs/openIM.log

What did you expect to happen?

如何处理呢

How can we reproduce it (as minimally and precisely as possible)?

1

Anything else we need to know?

No response

version

```console $ {name} version # paste output here ```

Cloud provider

OS version

```console # On Linux: $ cat /etc/os-release # paste output here $ uname -a # paste output here # On Windows: C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture # paste output here ```

Install tools

kubbot · 2023-12-18T01:20:10Z

Hello! Thank you for filing an issue.

If this is a bug report, please include relevant logs to help us debug the problem.

Join slack 🤖 to connect and communicate with our developers.

cubxxw · 2023-12-18T02:29:10Z

這個報錯提醒你是配置文件沒有配置成功
panic: runtime error: invalid memory address or nil pointer dereference

所以你需要去 openim-server/release-v3.4/config/ 改一下配置

cubxxw · 2023-12-18T02:29:46Z

object 中的 API_URL 配置，可以閱讀文檔https://github.com/openimsdk/open-im-server/blob/main/docs/contrib/environment.md

kubbot · 2023-12-18T02:29:58Z

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

API_URL configuration in object, you can read the document https://github.com/openimsdk/open-im-server/blob/main/docs/contrib/environment.md

kubbot · 2024-02-16T08:12:14Z

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.

kubbot · 2024-04-16T08:12:31Z

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.

kubbot · 2024-04-23T08:12:38Z

This issue was closed because it has been stalled for 7 days with no activity.

cubxxw changed the title ~~Bug: 启动出现问题~~ Bug: openim docker start Dec 18, 2023

kubbot added the lifecycle/stale label Apr 16, 2024

kubbot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 23, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Bug: openim docker start #56

Bug: openim docker start #56

lushou commented Dec 18, 2023

kubbot commented Dec 18, 2023

cubxxw commented Dec 18, 2023

cubxxw commented Dec 18, 2023

kubbot commented Dec 18, 2023

kubbot commented Feb 16, 2024

kubbot commented Apr 16, 2024

kubbot commented Apr 23, 2024

Bug: openim docker start #56

Bug: openim docker start #56

Comments

lushou commented Dec 18, 2023

What happened?

Use Docker to start all openim service

Begin to start all openim service scripts

Pre Starting OpenIM services

Use Docker to start all openim service

Begin to start all openim service scripts

Pre Starting OpenIM services

What did you expect to happen?

How can we reproduce it (as minimally and precisely as possible)?

Anything else we need to know?

version

Cloud provider

OS version

Install tools

kubbot commented Dec 18, 2023

cubxxw commented Dec 18, 2023

cubxxw commented Dec 18, 2023

kubbot commented Dec 18, 2023

kubbot commented Feb 16, 2024

kubbot commented Apr 16, 2024

kubbot commented Apr 23, 2024