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

137 exit code, but my limit is not set #77924

Closed
ajax-2 opened this issue May 15, 2019 · 5 comments

Comments

Projects
None yet
4 participants
@ajax-2
Copy link

commented May 15, 2019

error

Hey, All friends, my pod is exit with code 137 when i connect mysql in this pod.

error message

command terminated with non-zero exit code: Error executing in Docker Container: 137

environment

  • kubernetes: 1.14.1
  • docker: 18.0.9
  • mysql: 5.7
  • install method: helm

What

image
This is my pod, it's running, enn~ very good!
So i use nextcloud in web, and external mysql is this pod. But pod don't work, and tell me the message!
image

Hope

I wanna know Why it don't work, And i should do what to solve it.

note

In my logic machine, not vm, it work well!
And my pod resource is not set limit!

/sig podexit

@k8s-ci-robot

This comment has been minimized.

Copy link
Contributor

commented May 15, 2019

@ajax-2: There are no sig labels on this issue. Please add a sig label by either:

  1. mentioning a sig: @kubernetes/sig-<group-name>-<group-suffix>
    e.g., @kubernetes/sig-contributor-experience-<group-suffix> to notify the contributor experience sig, OR

  2. specifying the label manually: /sig <group-name>
    e.g., /sig scalability to apply the sig/scalability label

Note: Method 1 will trigger an email to the group. See the group list.
The <group-suffix> in method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@neolit123

This comment has been minimized.

Copy link
Member

commented May 15, 2019

/triage support
/remove-kind bug

hi, you might get better responses on slack or stackoverflow.
but also there are already a lot of related issues:
https://github.com/kubernetes/kubernetes/search?q=137+exit+code&type=Issues

@zq-david-wang

This comment has been minimized.

Copy link

commented May 16, 2019

If your pod restarted, "describe pod " should have useful information.

@ajax-2

This comment has been minimized.

Copy link
Author

commented May 16, 2019

If your pod restarted, "describe pod " should have useful information.

我看了下,启动后没有任何其他的日志,只显示健康检查失败,然后我把健康检查去掉了,还是出错

@ajax-2

This comment has been minimized.

Copy link
Author

commented May 16, 2019

/triage support
/remove-kind bug

hi, you might get better responses on slack or stackoverflow.
but also there are already a lot of related issues:
https://github.com/kubernetes/kubernetes/search?q=137+exit+code&type=Issues

Yeah, It's a good idea, Maybe i can get answer in stackoverflow! Thanks

@ajax-2 ajax-2 closed this May 16, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.