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

container exits randomly with Code 137 (but without OOM problems) #222

Closed
svenXY opened this issue Feb 7, 2019 · 2 comments
Closed

container exits randomly with Code 137 (but without OOM problems) #222

svenXY opened this issue Feb 7, 2019 · 2 comments
Labels
question Usability question, not directly related to an error with the image

Comments

@svenXY
Copy link

svenXY commented Feb 7, 2019

Hi,

I'm using the latest mariadb container with the DB directory in a volume in ~20 docker-hosts. It works flawlessly, except that very randomly, but sooner or later (several days and even weeks), containers exits with Exit Code 137. On the same systems are 3 docker containers with tomcat that do not exit and keep running.

So far, no memory reservations or limits were made for any of the containers, but the tomcat contaiers have decent Xmx and Xms settings that should leave more than enough memory for mariadb. Them being mostly dev and testing systems, they do not have a lot of traffic currently.
Futhermore, there are no memory or cpu spikes visible in monitoring.

I have already checked journalctl and the docker log for errors (especially since many posts mention OOM errors), but wasn't able to find anything that could give me any hint as to what goes wrong here.

Nothing in the docker logs and nothing in the systemd logs.

I'm using docker-compose v2.1 with a healthcheck. docker inspect on the exited container says "unhealthy", but the last 5 healthcheck all exited with 0, so this does not seem to be the problem either.

I'm out of ideas - do you have any suggestions what to change or how to get more information?

Thanks,
Sven

@wglambert wglambert added the question Usability question, not directly related to an error with the image label Feb 7, 2019
@tianon
Copy link
Contributor

tianon commented Feb 20, 2019

From moby/moby#21083 (comment), it appears the 137 is a SIGKILL -- are you sure you don't have something trying to do docker stop or even docker kill on this container/process?

The best I can suggest is perhaps disabling your HEALTHCHECK and see if you can still reproduce (to start narrowing it down).

In the future, these sorts of questions/requests would be more appropriately posted to the Docker Community Forums, the Docker Community Slack, or Stack Overflow (since this is more of a request for support rather than a reproducible issue with the image that we could actionably fix given the data provided).

@tianon tianon closed this as completed Feb 20, 2019
@advance512
Copy link

FYI for future readers, if your healthcheck isn't responding, an external orchestrator can stop the container, and you'll see code 137.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Usability question, not directly related to an error with the image
Development

No branches or pull requests

4 participants