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

Exception regularly thrown "/var/jenkins_home/deployment.out (No such file or directory)"

    Details

    • Similar Issues:

      Description

      Been seeing this regularly for some time now in Code Valet and other Jenkins environments

      java.io.FileNotFoundException: /var/jenkins_home/deployment.out (No such file or directory)
          at java.io.FileInputStream.open0(FileInputStream.java)
          at java.io.FileInputStream.open(FileInputStream.java:195)
          at java.io.FileInputStream.<init>(FileInputStream.java:138)
          at java.io.FileInputStream.<init>(FileInputStream.java:93)
          at com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask$DeploymentRegistrar.<init>(AzureVMAgentCleanUpTask.java:138)
          at com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask$DeploymentRegistrar.getInstance(AzureVMAgentCleanUpTask.java:151)
          at com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask.cleanDeployments(AzureVMAgentCleanUpTask.java:205)
          at com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask.cleanDeployments(AzureVMAgentCleanUpTask.java:196)
          at com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask.clean(AzureVMAgentCleanUpTask.java:571)
          at com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask.access$200(AzureVMAgentCleanUpTask.java:64)
          at com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask$3.call(AzureVMAgentCleanUpTask.java:583)
          at com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask$3.call(AzureVMAgentCleanUpTask.java:580)
          at java.util.concurrent.FutureTask.run(FutureTask.java:266)
          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
          at java.lang.Thread.run(Thread.java:745)
      

        Attachments

          Activity

          Hide
          zackliu Chenyang Liu added a comment -

          We serialize deployment info, so this exception will be thrown the first time used the plugin or the first time updated to new version.

          Does this exception being thrown in later use?

           

          Show
          zackliu Chenyang Liu added a comment - We serialize deployment info, so this exception will be thrown the first time used the plugin or the first time updated to new version. Does this exception being thrown in later use?  
          Hide
          rtyler R. Tyler Croy added a comment -

          Well for starters, an uncaught exception at all is pretty bad. If this is an expected scenarijo, then I don't think any exceptions should be raised to the System Log.

           

           

          That said, yes, this happens with some regularlity on restart for Jenkins environments. I've seen it 40 times in the past 2 months.

          Show
          rtyler R. Tyler Croy added a comment - Well for starters, an uncaught exception at all is pretty bad. If this is an expected scenarijo, then I don't think any exceptions should be raised to the System Log.     That said, yes, this happens with some regularlity on restart for Jenkins environments. I've seen it 40 times in the past 2 months.
          Hide
          azure_devops Azure DevOps added a comment -

          Fixed in 0.7.0

          Show
          azure_devops Azure DevOps added a comment - Fixed in 0.7.0

            People

            • Assignee:
              zackliu Chenyang Liu
              Reporter:
              rtyler R. Tyler Croy
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: