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

run rocketmq-broker using docker EXIT(137) #78

Closed
zhiqunz opened this issue Jul 6, 2018 · 5 comments
Closed

run rocketmq-broker using docker EXIT(137) #78

zhiqunz opened this issue Jul 6, 2018 · 5 comments

Comments

@zhiqunz
Copy link

@zhiqunz zhiqunz commented Jul 6, 2018

BUG REPORT

when I try to build and run name server and broker on MAC,
using the following sh:

rocketmq-externals/rocketmq-docker/4.1.0-incubating/play.sh

name server is ok, but broker container was automatically KILLED and exit(137)

Anyway, I tried to start the broker in name server container.

The broker was automatically killed. Is there any suggestion?

error message:

root@46dca5673f74:/opt/rocketmq-4.1.0-incubating# sh bin/mqbroker -n localhost:9876 &
[1] 35
root@46dca5673f74:/opt/rocketmq-4.1.0-incubating# Killed

[1]+  Exit 137                sh bin/mqbroker -n localhost:9876

@k19810703

This comment has been minimized.

Copy link

@k19810703 k19810703 commented Jul 6, 2018

I have the same problem.

@ququzone

This comment has been minimized.

Copy link

@ququzone ququzone commented Jul 16, 2018

also same problem

@huanwei

This comment has been minimized.

Copy link
Contributor

@huanwei huanwei commented Jul 27, 2018

@k19810703 @ququzone As I mentioned in my PR, I believe the issue you encountered was due to the default setting of broker's JVM is much more higher than your node's memory resource capacity. To avoid this you need to adjust your parameters according. For example:

JAVA_OPT="${JAVA_OPT} -server -Xms256m -Xmx256m -Xmn128m"
@xiaozongyang

This comment has been minimized.

Copy link
Contributor

@xiaozongyang xiaozongyang commented Jul 30, 2018

@zhiqunz @ququzone @k19810703 Would you mind providing more details about your docker environment? Maybe you can log in to your docker container and check out your memory size limit.
@zhiqunz by the way, if you install docker on your mac by homebrew and start the docker-machine service by command brew services start docker-machine the docker-machine will be running on the normal user instead of root. So when you run the script play.sh, which run the docker command with root user will get an error. When I try that shell command sudo docker build -t apache/incubator-rocketmq-namesrv:4.1.0-incubating ./namesrv in play.sh in my shell, I got an error with message:

Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

@ququzone @k19810703 So would you mind providing more details about your docker environment and the error message?

@huanwei huanwei mentioned this issue Aug 6, 2018
5 of 5 tasks complete
@vongosling

This comment has been minimized.

Copy link
Member

@vongosling vongosling commented Aug 7, 2018

@zhiqunz Could you check our community latest contribution, any problem, welcome to send email to our user email list

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

Successfully merging a pull request may close this issue.

None yet
6 participants
You can’t perform that action at this time.