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

Multiple dead executors on slaves post 1.379 upgrade

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • remoting
    • None
    • CentOS Linux 5.x kernel 2.6.18-194.3.1.el5
      hudson.war 1.379 under Tomcat 5.5.28
      Slave OSs: CentOS Linux 5.x, Windows XP 32bit, Windows Server 2008 64bit

      Post upgrade to 1.379 we are experiencing increased ocurrances of dead executors on our slave systems. Prior to this release we had never encountered a dead executor on any system, master or slave. Immediately after deploying the 1.379 WAR, 6 executors spread out among a variety of slave platforms (Linux, WinXP 32bit, Win2k8 64bit) died. Today one more died on a Linux slave. Restarting Hudson clears out the dead executors, but disconnecting and reconnecting the slaves does not. I have not tried rebooting the slaves themselves yet. The stack trace below has consistently been the output associated with the dead executors.

      java.lang.AbstractMethodError
      at hudson.model.Executor.getEstimatedRemainingTimeMillis(Executor.java:340)
      at hudson.model.queue.LoadPredictor$CurrentlyRunningTasks.predict(LoadPredictor.java:77)
      at hudson.model.queue.MappingWorksheet.(MappingWorksheet.java:303)
      at hudson.model.Queue.pop(Queue.java:753)
      at hudson.model.Executor.grabJob(Executor.java:175)
      at hudson.model.Executor.run(Executor.java:113)

          [JENKINS-7707] Multiple dead executors on slaves post 1.379 upgrade

          I have always this bug !
          Same stack trace. Right now, 1 executor of 2 died

          have you any idea ?

          bertrandgressier added a comment - I have always this bug ! Same stack trace. Right now, 1 executor of 2 died have you any idea ?

          Finally it's ok !
          it's due to old Batch mode plugin in my conf ...
          I upgrade this and now all seems good

          bertrandgressier added a comment - Finally it's ok ! it's due to old Batch mode plugin in my conf ... I upgrade this and now all seems good

          I am noticing this on 1385. I suspect that it might be related to the SCM Trigger after the polling.
          @bertrandgressier: which plugin (Batch) are you taking about?

          carlo_bonamico added a comment - I am noticing this on 1385. I suspect that it might be related to the SCM Trigger after the polling. @bertrandgressier: which plugin (Batch) are you taking about?

          I speak to hudson plugin : batch task http://wiki.jenkins-ci.org/display/JENKINS/Batch+Task+Plugin

          This bug is due with a plugin in your conf

          bertrandgressier added a comment - I speak to hudson plugin : batch task http://wiki.jenkins-ci.org/display/JENKINS/Batch+Task+Plugin This bug is due with a plugin in your conf

          kutzi added a comment -

          IMO these are different issues. The one including the batch task plugin was introduced in Hudson 1.383 or 1.384

          kutzi added a comment - IMO these are different issues. The one including the batch task plugin was introduced in Hudson 1.383 or 1.384

          I just noticed that at the time the issue appeared, I had both upgraded to 1384, AND set the maximum thread number for SCM polling to 20. Apparently, removing the thread polling limit made the issue disappear. Also, the issue in fact appeared to happen just after the SCM polling for a big project had taken place. I have about 40 projects on the server, and 4 slaves.

          carlo_bonamico added a comment - I just noticed that at the time the issue appeared, I had both upgraded to 1384, AND set the maximum thread number for SCM polling to 20. Apparently, removing the thread polling limit made the issue disappear. Also, the issue in fact appeared to happen just after the SCM polling for a big project had taken place. I have about 40 projects on the server, and 4 slaves.

          Alan Harder added a comment -

          The original reporter has mentioned not seeing this issue anymore.. does anyone else still see dead slaves with this exception on the latest Hudson release?

          java.lang.AbstractMethodError
          at hudson.model.Executor.getEstimatedRemainingTimeMillis(Executor.java:340)

          Alan Harder added a comment - The original reporter has mentioned not seeing this issue anymore.. does anyone else still see dead slaves with this exception on the latest Hudson release? java.lang.AbstractMethodError at hudson.model.Executor.getEstimatedRemainingTimeMillis(Executor.java:340)

          usammmy added a comment -

          Upgraded to .385. We haven't seen this issue for a while.

          usammmy added a comment - Upgraded to .385. We haven't seen this issue for a while.

          I am not seeing it on 1.385 and latest Batch Task plugin

          carlo_bonamico added a comment - I am not seeing it on 1.385 and latest Batch Task plugin

          Alan Harder added a comment -

          Ok, thanks.. closing this out. Reopen if anyone sees this AbstractMethodError on a recent release.

          Alan Harder added a comment - Ok, thanks.. closing this out. Reopen if anyone sees this AbstractMethodError on a recent release.

            Unassigned Unassigned
            dru_n dru_n
            Votes:
            6 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: