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

Subprocess exited with an OOM, pipeline then zombied

      Over the weekend, two memory intensives jobs were built at the same time. This lead to the linux kernel killing the process in the build step

      Jenkins didn't seem to notice that was what happened, leading the the job hanging. Looking at the list of active processes (using ps -ef | grep jenkins) Jenkins didn't have any processes doing anything from what I could tell.

      As far as I can tell, pipeline should have seen the fact the subprocess has been terminated?

          [JENKINS-45873] Subprocess exited with an OOM, pipeline then zombied

          Patrick Rose added a comment -

          We've just been hit by this again.

          1. Jenkins was restarted by some system (I haven't been told what yet
          2. The process that it was using for the build was therefore kill halted
          3. Jenkins was brought back up
          4. The process it was using for the build doesn't exist, but Jenkins is stuck on that build step

          Patrick Rose added a comment - We've just been hit by this again. Jenkins was restarted by some system (I haven't been told what yet The process that it was using for the build was therefore kill halted Jenkins was brought back up The process it was using for the build doesn't exist, but Jenkins is stuck on that build step

            Unassigned Unassigned
            drugcrazed Patrick Rose
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: