Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RHEL 7.7] Cannot start NDID API, because the MQ container not start. #46

Open
pokpitch opened this issue Feb 4, 2020 · 8 comments
Open

Comments

@pokpitch
Copy link

pokpitch commented Feb 4, 2020

Environment

  • NDID, smart-contract v4.0.0
  • NDID, api v3.0.1
  • Red Hat Enterprise Linux Server 7.7

[docker_mq-rp_1 exited with code 139
[docker_mq-as_1 exited with code 139
[mdocker_mq-idp-1_1 exited with code 139
[api-ndid_1] Segmentation fault (core dumped)
[docker_mq-idp-2_1] exited with code 139

docker compose up logs:
api-compose-up-with-mq-error.log

@pokpitch pokpitch changed the title Cannot start NDID API, because the MQ container not start. [RHEL 7.7] Cannot start NDID API, because the MQ container not start. Apr 14, 2020
@peerawichh
Copy link

รบกวนขอ log ของ mq ด้วยครับ

@pokpitch
Copy link
Author

รบกวนขอ log ของ mq ด้วยครับ

log ผม attached ไว้กับ issue แล้วครับ
อาการนี้สังเกตและสรุปได้ว่า เกิดขึ้นเวลาผม ใช้ instance ECS (IaaS) ของ Huawei Cloud ครับ
พอนำไปทดสอบกับ Cloud Provider อื่นไม่เจอปัญหานี้ครับ

@peerawichh
Copy link

อันนี้ลองลงตัว example หรือเปล่าครับ

@pokpitch
Copy link
Author

scenarios คือ

  1. docker-compose up ../smart-contract/docker/docker-compose.yml อันนี้ไม่มีปัญหาอะไร
  2. docker-compose up ../api/docker/docker-compose.yml ตรงนี้จะเกิดปัญหาที่แจ้งไปด้านบนขึ้นครับ

@re7eal
Copy link
Collaborator

re7eal commented May 10, 2020

This is a known issue of api and mq v3.0.1 Docker images. Try building a new image from source code and see if the issue still persists.

@pokpitch
Copy link
Author

pokpitch commented Jun 17, 2020

This is a known issue of api and mq v3.0.1 Docker images. Try building a new image from source code and see if the issue still persists.

Thanks for your reply,
Now, I build a new image based on v4.0.1 source code and smart-contract is v5.0.0

  • API containers started (The core dumped problems is gone)
  • All MQ containers still have errors (docker_mq-xxx_1 exited with code 139)

Please find attached for API docker-compose up log,

MobaXterm_192.168.211.34admin_20200617_121829.txt

@re7eal
Copy link
Collaborator

re7eal commented Jun 29, 2020

If you're fine with using the latest version then, please try 4.0.1 or 4.1.0 image available on Docker Hub. If it still doesn't work or you want to build an image yourself, you might want to delete all Docker base images on the machine that you're building an image and try building it again.

@pokpitch
Copy link
Author

I just found the root cause that mq-server can not start properly on my environment.

host is set ipv6 to disable, the grpc server on mq-server can not bind anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants