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

Random "process apparently never started" error

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • pipeline-maven-plugin
    • None
    • Jenkins 2.150.2
      Pipeline Maven plugin 3.6.7

      Just got this on XWiki's CI:
      https://ci.xwiki.org/blue/organizations/jenkins/XWiki%2Fxwiki-platform/detail/master/1403/pipeline

      INFO] --- maven-surefire-plugin:2.22.0:test (default-test) @ xwiki-platform-image-plugin ---

[INFO] Surefire report directory: /home/hudsonagent/jenkins_root/workspace/XWiki_xwiki-platform_master-ZGNMAWOYB6APYNMYWF7HH475RM4M6C6RE2U76Y5M5RWNQJWOLFGA/xwiki-platform-core/xwiki-platform-image/xwiki-platform-image-plugin/target/surefire-reports

[INFO] 

[INFO] -------------------------------------------------------

[INFO]  T E S T S

[INFO] -------------------------------------------------------

[INFO] Running com.xpn.xwiki.plugin.image.ImagePluginTest

process apparently never started in /home/hudsonagent/jenkins_root/workspace/XWiki_xwiki-platform_master-ZGNMAWOYB6APYNMYWF7HH475RM4M6C6RE2U76Y5M5RWNQJWOLFGA@tmp/durable-41a561b2

sh: 1: cannot create /home/hudsonagent/jenkins_root/workspace/XWiki_xwiki-platform_master-ZGNMAWOYB6APYNMYWF7HH475RM4M6C6RE2U76Y5M5RWNQJWOLFGA@tmp/durable-41a561b2/jenkins-result.txt.tmp: Directory nonexistent

mv: cannot stat `/home/hudsonagent/jenkins_root/workspace/XWiki_xwiki-platform_master-ZGNMAWOYB6APYNMYWF7HH475RM4M6C6RE2U76Y5M5RWNQJWOLFGA@tmp/durable-41a561b2/jenkins-result.txt.tmp': No such file or directory

script returned exit code -2

      Any idea what could be the cause?
      Thanks

          [JENKINS-55796] Random "process apparently never started" error

          Eugene G added a comment -

          I'm not sure if my case somehow linked to the case from the ticket but for those who will be looking for similar problems: in my case it was caused by dead sidecar docker container:

          docker.image('elasticsearch:6.4.0').withRun() { es ->
    image.inside("--link ${es.id}:es") {
        sh 'my_script.sh' // process apparently never started in ...
    }
}

          So Elasticsearch image started and exited with an error but Jenkins doesn't control this, so I got the problem.

          Eugene G added a comment - I'm not sure if my case somehow linked to the case from the ticket but for those who will be looking for similar problems: in my case it was caused by dead sidecar docker container: docker.image( 'elasticsearch:6.4.0' ).withRun() { es -> image.inside( "--link ${es.id}:es" ) { sh 'my_script.sh' // process apparently never started in ... } } So Elasticsearch image started and exited with an error but Jenkins doesn't control this, so I got the problem.

            Unassigned Unassigned
            vmassol Vincent Massol
            Votes:
            3 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: