OOMKilled has nothing to do with the host resources, but the process in the
container using more memory than available.
Try increasing the memory limits and read
https://blog.csanchez.org/2017/05/31/running-a-jvm-in-a-container-without-getting-killed/

On Thu, Feb 22, 2018 at 10:19 AM, <bran...@rabb.it> wrote:

> Disk space and memory are all at an extremely low utilization for all of
> my hosts. So it's not real resource exhaustion. I'm thinking timeline wise
> it seems that OOMkilled state is possibly a result of kubernetes
> terminating the pod due to disconnection.
>
>
> INFO: Excess workload after pending Spot instances: 1
> Feb 22, 2018 9:05:10 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud
> provision
> INFO: Template: Kubernetes Pod Template
> Feb 22, 2018 9:05:10 AM okhttp3.internal.platform.Platform log
> INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot
> class path?
> Feb 22, 2018 9:05:10 AM hudson.slaves.NodeProvisioner$StandardStrategyImpl
> apply
> INFO: Started provisioning Kubernetes Pod Template from kubernetes with 1
> executors. Remaining excess workload: 0
> Feb 22, 2018 9:05:20 AM hudson.slaves.NodeProvisioner$2 run
> INFO: Kubernetes Pod Template provisioning successfully completed. We have
> now 2 computer(s)
> Feb 22, 2018 9:05:20 AM okhttp3.internal.platform.Platform log
> INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot
> class path?
> Feb 22, 2018 9:05:20 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Created Pod: jnlp-t2c36 in namespace jenkins-test
> Feb 22, 2018 9:05:20 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (0/100): jnlp-t2c36
> Feb 22, 2018 9:05:26 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (1/100): jnlp-t2c36
> Feb 22, 2018 9:05:32 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (2/100): jnlp-t2c36
> Feb 22, 2018 9:05:38 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (3/100): jnlp-t2c36
> Feb 22, 2018 9:05:44 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (4/100): jnlp-t2c36
> Feb 22, 2018 9:05:47 AM hudson.model.Descriptor verifyNewInstance
> WARNING: Father of ContainerEnvVar [getValue()=http://jenkins-
> test-jenkins:8080, getKey()=JENKINS_URL] and its getDescriptor() points
> to two different instances. Probably malplaced @Extension. See
> http://hudson.361315.n4.nabble.com/Help-Hint-needed-
> Post-build-action-doesn-t-stay-activated-td2308833.html
> Feb 22, 2018 9:05:50 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (5/100): jnlp-t2c36
> Feb 22, 2018 9:05:56 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (6/100): jnlp-t2c36
> Feb 22, 2018 9:06:02 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (7/100): jnlp-t2c36
> Feb 22, 2018 9:06:08 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (8/100): jnlp-t2c36
> Feb 22, 2018 9:06:14 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (9/100): jnlp-t2c36
> Feb 22, 2018 9:06:20 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (10/100): jnlp-t2c36
> Feb 22, 2018 9:06:26 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (11/100): jnlp-t2c36
> Feb 22, 2018 9:06:32 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (12/100): jnlp-t2c36
> Feb 22, 2018 9:06:38 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (13/100): jnlp-t2c36
> Feb 22, 2018 9:06:44 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (14/100): jnlp-t2c36
> Feb 22, 2018 9:06:50 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (15/100): jnlp-t2c36
> Feb 22, 2018 9:06:56 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (16/100): jnlp-t2c36
> Feb 22, 2018 9:07:02 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (17/100): jnlp-t2c36
> Feb 22, 2018 9:07:08 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (18/100): jnlp-t2c36
> Feb 22, 2018 9:07:14 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (19/100): jnlp-t2c36
> Feb 22, 2018 9:07:20 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (20/100): jnlp-t2c36
> Feb 22, 2018 9:07:26 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (21/100): jnlp-t2c36
> Feb 22, 2018 9:07:32 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (22/100): jnlp-t2c36
> Feb 22, 2018 9:07:38 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (23/100): jnlp-t2c36
> Feb 22, 2018 9:07:44 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (24/100): jnlp-t2c36
> Feb 22, 2018 9:07:50 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (25/100): jnlp-t2c36
> Feb 22, 2018 9:07:56 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (26/100): jnlp-t2c36
> Feb 22, 2018 9:08:02 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (27/100): jnlp-t2c36
> Feb 22, 2018 9:08:03 AM hudson.slaves.CloudRetentionStrategy check
> INFO: Disconnecting jnlp-t2c36
> Feb 22, 2018 9:08:03 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave
> _terminate
> INFO: Terminating Kubernetes instance for agent jnlp-t2c36
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/62e322fe-2a9e-4f3e-ab6a-494e4991d9f3%40googlegroups.
> com
> <https://groups.google.com/d/msgid/jenkinsci-users/62e322fe-2a9e-4f3e-ab6a-494e4991d9f3%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CALHFn6NtF9FH%3D_npMHVwzR75Ua-JFqxn5hOutU2mGJayM0ODtw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to