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

Unable to delete a job that has a fstrigger

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • fstrigger-plugin
    • None

      I have a fstrigger that polls every minute, and most of the time when I try to delete the job I get an error:
      java.io.IOException: Unable to delete /some/path/.nfs00000000018e26ca00236d2f

      so I look at that file, and it contains the fstrigger polling log.

      If I disable the fstrigger, then I am able to delete the job.

          [JENKINS-12176] Unable to delete a job that has a fstrigger

          Jim Searle created issue -
          Gregory Boissinot made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

          Gregory Boissinot added a comment -

          Thanks for raising this issue.
          Could you give your Jenkins core version and the fstrigger Jenkins plugin version you are using.

          Additionally, is '/some/path' a directory polled by the FSTrigger plugin?

          Gregory Boissinot added a comment - Thanks for raising this issue. Could you give your Jenkins core version and the fstrigger Jenkins plugin version you are using. Additionally, is '/some/path' a directory polled by the FSTrigger plugin?

          Jim Searle added a comment - - edited

          Jenkins version 1.436
          fstrigger version 1.18
          The /some/path is /JENKINS_HOME/JOB_NAME directory.

          thanks for looking into it.

          Jim Searle added a comment - - edited Jenkins version 1.436 fstrigger version 1.18 The /some/path is /JENKINS_HOME/JOB_NAME directory. thanks for looking into it.

          Gregory Boissinot added a comment -

          Your monitored folder is the job folder itself. Therefore when you delete the job, it must not have left active processes on this folder.
          I think it should be fixed with FSTrigger 0.21. Before this version, there were left processes because they were not properly closed.
          Could you upgrade the plugin and test it?

          Gregory Boissinot added a comment - Your monitored folder is the job folder itself. Therefore when you delete the job, it must not have left active processes on this folder. I think it should be fixed with FSTrigger 0.21. Before this version, there were left processes because they were not properly closed. Could you upgrade the plugin and test it?

          Jim Searle added a comment -

          The monitored folder is not the job folder, it is a different path. The file that is locked is the trigger-polling-files.log file in the job workspace.

          But, I will try the 0.21 to see if that solves the problem.

          Jim Searle added a comment - The monitored folder is not the job folder, it is a different path. The file that is locked is the trigger-polling-files.log file in the job workspace. But, I will try the 0.21 to see if that solves the problem.

          Gregory Boissinot added a comment -

          Should be fixed.
          The issue was certainly of the same reasons of JENKINS-11907 for an another XTrigger plugin.

          Gregory Boissinot added a comment - Should be fixed. The issue was certainly of the same reasons of JENKINS-11907 for an another XTrigger plugin.
          Gregory Boissinot made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]

          Jim Searle added a comment -

          We are debugging a "too many open files" issue, and following the instructions here: https://wiki.jenkins-ci.org/display/JENKINS/I'm+getting+too+many+open+files+error

          I do a: ls -la /proc/2141/fd
          on our jenkins machine, and it looks like every single job that uses the fstrigger keeps it's log file open all the time:
          /<jenkins_home>/jobs/<job_name>/trigger-polling-files.log

          Jim Searle added a comment - We are debugging a "too many open files" issue, and following the instructions here: https://wiki.jenkins-ci.org/display/JENKINS/I'm+getting+too+many+open+files+error I do a: ls -la /proc/2141/fd on our jenkins machine, and it looks like every single job that uses the fstrigger keeps it's log file open all the time: /<jenkins_home>/jobs/<job_name>/trigger-polling-files.log
          Jim Searle made changes -
          Resolution Original: Fixed [ 1 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]

            gbois Gregory Boissinot
            jimsearle Jim Searle
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: