Home:ALL Converter>How to find logs for command terminated with exit code 137 error after kubectl exec command is triggered at pod

How to find logs for command terminated with exit code 137 error after kubectl exec command is triggered at pod

Ask Time:2018-12-13T23:00:55         Author:Margaret real

Json Formatter

My pod is created and while executing below command in pod after sometime getting error as command terminated with exit code 137

kubectl exec gradlecommandfromcommandline -- ./gradlew gatlingRun- 
simulations.RuntimeParameters -DUSERS=500 -DRAMP_DURATION
=5 -DDURATION=30

How to debug the problem ,i mean what is the issue,mind you the same docker equivalent command runs fine with docker run,but issue is only after i execute kubectl exec command on pod,As i suspected memory issue in kubectl so i do specified memory limits within 'default' namespace using below

apiVersion: v1
kind: LimitRange
metadata:
name: mem-min-max-demo-lr
spec:
limits:
- max:
  memory: 1Gi
min:

  memory: 500Mi

type: Container

Author:Margaret real,eproduced under the CC 4.0 BY-SA copyright license with a link to the original source and this disclaimer.
Link to original article:https://stackoverflow.com/questions/53764644/how-to-find-logs-for-command-terminated-with-exit-code-137-error-after-kubectl-e
yy