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

File handle leak


    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • core
    • None
    • Jenkins 2.73.3

      After upgrade to 2.73.3 we noticed that after a few days Jenkins becomes unresponsive and gives "too many open files" error. The only way to overcome the issue is to restart the instance.

      The File Leak Detector Plugin does show some open handles for completed jobs but after a few hours those are pruned by themselves from the list. The total amount of open file handles never exceeds 2000 according to the plugin.

      However when we run 'lsof' we see the increase of open file handles over time (see the screenshot attached: the big drop on Nov 27 is due to the manual Jenkins restart).

      Here's the summary of 2 lsof runs with 1 day between them. The list of top files:


      100632 slave.log
      32294 log
      7685 timestamps
      4193 random
      3635 urandom


      708532 log
      297707 timestamps
      98280 slave.log
      90675 Common.groovy
      85995 BobHelper.groovy

      Common.groovy and BobHelper.groovy are used by some jobs.

            Unassigned Unassigned
            wheleph Volodymyr Sobotovych
            2 Vote for this issue
            6 Start watching this issue