Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-20947

Failed to monitor for Free Swap Space

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Component/s: remoting
    • Labels:
    • Environment:
      Jenkins Master : Win 2008 R2 x 64
      Jenkins Slave : Win 2003 x86
      Tomcat web container , connecting to slave using JNLP
    • Similar Issues:

      Description

      Builds running on the slave hang at the initial pre checkout step
      10:42:10 Started by upstream project "Trunk_Master" build number 135
      10:42:10 originally caused by:
      10:42:10 Started by user Build Team
      10:42:10 Starting limited count build: 1
      10:42:10 [EnvInject] - Loading node environment variables.
      10:42:10 Building remotely on SlaveX in workspace C:\Hudson\workspace\Trunk_TS

      Jenkins logs show this error on the slave at the time it is hung.

      WARNING hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor monitor

      Failed to monitor SlaveX for Free Swap Space
      java.util.concurrent.TimeoutException
      at hudson.remoting.Request$1.get(Request.java:275)
      at hudson.remoting.Request$1.get(Request.java:210)
      at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59)
      at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:97)
      at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:282)

      Let me know if you need more details

      Thanks
      Shobha

        Attachments

          Issue Links

            Activity

            Hide
            mtaylor Matt Taylor added a comment -

            Experiencing this same issue with a slave that is used on demand.

            jenkins.err.zip

            Show
            mtaylor Matt Taylor added a comment - Experiencing this same issue with a slave that is used on demand. jenkins.err.zip
            Hide
            xtaylor21x Matt Taylor added a comment -

            Please someone help still experiencing this.

            Show
            xtaylor21x Matt Taylor added a comment - Please someone help still experiencing this.
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            JENKINS-48309 may be a culprit. TimeoutException may happen before the timeout time really passes, and the stacktraces from Matt Taylor and the issue reporter point to the affected code.

            Nov 02, 2016 2:51:12 PM hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor monitor
            WARNING: Failed to monitor PRW8-32-A for Free Swap Space
            java.util.concurrent.TimeoutException
            	at hudson.remoting.Request$1.get(Request.java:279)
            	at hudson.remoting.Request$1.get(Request.java:207)
            	at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59)
            	at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:96)
            	at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:305)
            
            Show
            oleg_nenashev Oleg Nenashev added a comment - JENKINS-48309 may be a culprit. TimeoutException may happen before the timeout time really passes, and the stacktraces from Matt Taylor and the issue reporter point to the affected code. Nov 02, 2016 2:51:12 PM hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor monitor WARNING: Failed to monitor PRW8-32-A for Free Swap Space java.util.concurrent.TimeoutException at hudson.remoting.Request$1.get(Request.java:279) at hudson.remoting.Request$1.get(Request.java:207) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:96) at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:305)
            Hide
            rsbeckerca Randall Becker added a comment - - edited

            I also just started experiencing this situation under 2.222.3 under Java 1.8_242 under z/OS USS. This was after increasing the Node SSH timeout to something large. The Node log is showing:

            ERROR: Failed to monitor for Response Time
            java.util.concurrent.TimeoutException
            {{ at hudson.remoting.Request$1.get(Request.java:316)}}
            {{ at hudson.remoting.Request$1.get(Request.java:240)}}
            {{ at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59)}}
            {{ at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitorDetailed(AbstractAsyncNodeMonitorDescriptor.java:114)}}
            {{ at hudson.node_monitors.ResponseTimeMonitor$1.monitor(ResponseTimeMonitor.java:57)}}
            {{ at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:306)}}
            ERROR: Failed to monitor for Free Disk Space
            java.util.concurrent.TimeoutException
            {{ at hudson.remoting.Request$1.get(Request.java:316)}}
            {{ at hudson.remoting.Request$1.get(Request.java:240)}}
            {{ at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59)}}
            {{ at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitorDetailed(AbstractAsyncNodeMonitorDescriptor.java:114)}}
            {{ at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:78)}}
            {{ at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:306)}}
            ERROR: Failed to monitor for Free Temp Space
            java.util.concurrent.TimeoutException
            {{ at hudson.remoting.Request$1.get(Request.java:316)}}
            {{ at hudson.remoting.Request$1.get(Request.java:240)}}
            {{ at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59)}}
            {{ at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitorDetailed(AbstractAsyncNodeMonitorDescriptor.java:114)}}
            {{ at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:78)}}
            {{ at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:306)...}}

            in a loop until the SSH timeout hits, which then cancels the job by closing the connection. Are we possibly missing a dependency on the server? The server only has a straight up JDK with no additional tools (other than git and perl).

            Show
            rsbeckerca Randall Becker added a comment - - edited I also just started experiencing this situation under 2.222.3 under Java 1.8_242 under z/OS USS. This was after increasing the Node SSH timeout to something large. The Node log is showing: ERROR: Failed to monitor for Response Time java.util.concurrent.TimeoutException {{ at hudson.remoting.Request$1.get(Request.java:316)}} {{ at hudson.remoting.Request$1.get(Request.java:240)}} {{ at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59)}} {{ at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitorDetailed(AbstractAsyncNodeMonitorDescriptor.java:114)}} {{ at hudson.node_monitors.ResponseTimeMonitor$1.monitor(ResponseTimeMonitor.java:57)}} {{ at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:306)}} ERROR: Failed to monitor for Free Disk Space java.util.concurrent.TimeoutException {{ at hudson.remoting.Request$1.get(Request.java:316)}} {{ at hudson.remoting.Request$1.get(Request.java:240)}} {{ at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59)}} {{ at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitorDetailed(AbstractAsyncNodeMonitorDescriptor.java:114)}} {{ at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:78)}} {{ at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:306)}} ERROR: Failed to monitor for Free Temp Space java.util.concurrent.TimeoutException {{ at hudson.remoting.Request$1.get(Request.java:316)}} {{ at hudson.remoting.Request$1.get(Request.java:240)}} {{ at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59)}} {{ at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitorDetailed(AbstractAsyncNodeMonitorDescriptor.java:114)}} {{ at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:78)}} {{ at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:306)...}} in a loop until the SSH timeout hits, which then cancels the job by closing the connection. Are we possibly missing a dependency on the server? The server only has a straight up JDK with no additional tools (other than git and perl).
            Hide
            leodan Leonor Daniel added a comment - - edited

            Also having this issue on Jenkins 2.229, with a Mac OS X 10.14.6 node that has java JDK 1.8.0_202 and remoting version: 4.3:

            ERROR: Failed to monitor for Free Swap Space
            java.util.concurrent.TimeoutException
            	at hudson.remoting.Request$1.get(Request.java:316)
            	at hudson.remoting.Request$1.get(Request.java:240)
            	at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59)
            	at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitorDetailed(AbstractAsyncNodeMonitorDescriptor.java:114)
            	at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:78)
            	at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:306)
            

            I disabled Swap Space monitoring but that made no difference. The node cannot be recovered once it gets in that state unless the machine is manually rebooted. This happens multiple times a week.

            Show
            leodan Leonor Daniel added a comment - - edited Also having this issue on Jenkins 2.229, with a Mac OS X 10.14.6 node that has java JDK 1.8.0_202 and remoting version: 4.3: ERROR: Failed to monitor for Free Swap Space java.util.concurrent.TimeoutException at hudson.remoting.Request$1.get(Request.java:316) at hudson.remoting.Request$1.get(Request.java:240) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitorDetailed(AbstractAsyncNodeMonitorDescriptor.java:114) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:78) at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:306) I disabled Swap Space monitoring but that made no difference. The node cannot be recovered once it gets in that state unless the machine is manually rebooted. This happens multiple times a week.

              People

              • Assignee:
                Unassigned
                Reporter:
                shobhad Shobha Dashottar
              • Votes:
                9 Vote for this issue
                Watchers:
                18 Start watching this issue

                Dates

                • Created:
                  Updated: