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

Build hangs in several phases (post build, pre build, email-ext)

      After upgrading Jenkins LTS version from 1.651.1 to 2.7.1 we have nearly all builds hanging. Some of them hanging in "Before Build" phase and some are seem to be finished but hanging also.

      For example the output for a hanging build in "before build" phase:

      [EnvInject] - Variables injected successfully.
      Email was triggered for: Before Build
      Sending email for trigger: Before Build

      And an example about the "finished build" phase:

      [INFO] BUILD SUCCESS
      [INFO] ------------------------------------------------------------------------
      [INFO] Total time: 01:33 min
      [INFO] Finished at: 2016-07-22T10:34:15+02:00
      [INFO] Final Memory: 71M/809M
      [INFO] ------------------------------------------------------------------------
      Waiting for Jenkins to finish collecting data
      channel stopped
      Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0
      Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0

      We guess it is a general problem with jenkins master/node .. nothing plugin specific. But for example builds with simple scripts (powershell) working and sending emails (so not email-ext specific) and some builds are finishing after a great period of time.

      We have no clue which circumstances making this behavior.

      We have also seen this after trying to upgrade LTS from 1.651.1 to 1.651.2 .. so possible some changes between those versions making the difference.

          [JENKINS-36870] Build hangs in several phases (post build, pre build, email-ext)

          Have you tried removing the email-ext plugin and confirmed it does or does not happen without it? "Enable Debug Mode" in global configuration may also provide more info or adjusting log levels at /log/levels.

          David van Laatum added a comment - Have you tried removing the email-ext plugin and confirmed it does or does not happen without it? "Enable Debug Mode" in global configuration may also provide more info or adjusting log levels at /log/levels.

          Thomas Wabner added a comment -

          Thanks for your help. We have tried to check with debug enabled and started to disable some plugins. Therefore we found one suspecting plugin which uses ldap callbacks to get email adresses for users from AD backend. And this plugin makes a deadlock.

          After disabled security at all, all build running fine. After patching the ldap plugin we have a working jenkins instance back.

          Thank you again.

          Thomas Wabner added a comment - Thanks for your help. We have tried to check with debug enabled and started to disable some plugins. Therefore we found one suspecting plugin which uses ldap callbacks to get email adresses for users from AD backend. And this plugin makes a deadlock. After disabled security at all, all build running fine. After patching the ldap plugin we have a working jenkins instance back. Thank you again.

            davidvanlaatum David van Laatum
            waffel Thomas Wabner
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: