Saturday, February 13, 2016

Pending - Waiting for next available executor/Disk space too low on /tmp - Jenkins

Pending - Waiting for next available executor/Disk space too low on /tmp - Jenkins

While we were trying to execute the job, it was displaying "Pending - Waiting for next available executor". When looking into the Jenkins node from the console, the Master node is offline and the error message displayed was "Disk space too low. Only xxxGB on /tmp" but the /tmp folder has space around 1GB.





Steps are followed to resolve the issue

  • Increase the space available in /tmp folder. If not able to increase the space in /tmp folder then TemporarySpaceMonitor can be disabled or the memory threshold value of the TemporarySpaceMonitor can be reduced in $JENKINS_HOME/nodeMonitors.xml(make sure atleast minimum memory is available)


<?xml version='1.0' encoding='UTF-8'?>
<hudson.util.DescribableList>
  <hudson.node__monitors.ArchitectureMonitor>
    <ignored>false</ignored>
  </hudson.node__monitors.ArchitectureMonitor>
  <hudson.node__monitors.ClockMonitor>
    <ignored>false</ignored>
  </hudson.node__monitors.ClockMonitor>
  <hudson.node__monitors.DiskSpaceMonitor>
    <ignored>false</ignored>
    <freeSpaceThreshold>1GB</freeSpaceThreshold>
  </hudson.node__monitors.DiskSpaceMonitor>
  <hudson.node__monitors.SwapSpaceMonitor>
    <ignored>false</ignored>
  </hudson.node__monitors.SwapSpaceMonitor>
  <hudson.node__monitors.TemporarySpaceMonitor>
    <ignored>false</ignored>//Change to true to disable monitoring 
    <freeSpaceThreshold>50MB</freeSpaceThreshold>
  </hudson.node__monitors.TemporarySpaceMonitor>
  <hudson.node__monitors.ResponseTimeMonitor>
    <ignored>false</ignored>
  </hudson.node__monitors.ResponseTimeMonitor>
</hudson.util.DescribableList>

  • Increase the number of executor from default value 2


  • Remove the following content from $JENKINS_HOME/config.xml

<temporaryOfflineCause class="hudson.node_monitors.DiskSpaceMonitorDescriptor$DiskSpace">
    <path>/tmp</path>
    <size>966733824</size>
    <triggered>true</triggered>
    <trigger>hudson.node_monitors.TemporarySpaceMonitor</trigger>
  </temporaryOfflineCause>

  • Restart the Jenkins server.


5 comments:

  1. Wow,another interesting articles,thanks for sharing that valuable information.More new information are get after refer that post.I hope this type of important articles.
    java training

    ReplyDelete
  2. Superb article i saw the article with execution models you had posted how to identify the space. This type of examples will clearly explain their program. It was such informative. Really its a wonderful article. Thank you for sharing and please keep update like this type of article because i want to learn more relevant to this topic.

    Salesforce Training

    ReplyDelete
  3. Awesome..You have clearly explained ...Its very useful for me to know about new things..Keep on blogging..
    Java Training in Chennai

    ReplyDelete
  4. yes its helpful thanks for sharing dear

    ReplyDelete