com.atlassian.bamboo.repository.RepositoryException: Failed to get changes: Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4

Atlassian JIRA | Johannes Stamminger | 1 decade ago
tip
Do you know that we can give you better hits? Get more relevant results from Samebug’s stack trace search.
  1. 0

    While one plan was executing I tried creation of a new one. After having pressed the "Continue" button on the perforce repository details page, the ui was blocked, no interaction any longer possible with the bamboo. In the logfiles I detected entries like INFO | jvm 1 | 2007/03/06 13:37:17 | /usr/local/bin/p4 -u <perforce user> -p <perforce server>:<perforce port> -c <perforce clientspec name> client -o occuring repeatedly multiple times per second (!) without any further error message. Maybe it was not the best idea but I renamed the p4-executable (the morning after a stop-start I had loss of data so I tried to avoid this - but this is a different story). After some time (not immediately!) this perforce server penetration stopped with INFO | jvm 1 | 2007/03/06 14:20:37 | com.atlassian.bamboo.repository.RepositoryException: Failed to get changes: Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | INFO | jvm 1 | 2007/03/06 14:20:37 | at com.atlassian.bamboo.repository.perforce.PerforceRepository.getChangesSinceLastBuild(PerforceRepository.java:290) INFO | jvm 1 | 2007/03/06 14:20:37 | at com.atlassian.bamboo.build.strategy.PollingBuildStrategy.requiresBuild(PollingBuildStrategy.java:126) INFO | jvm 1 | 2007/03/06 14:20:37 | at com.atlassian.bamboo.build.DefaultBuildChangeDetector.checkIfBuildNeedsBuilding(DefaultBuildChangeDetector.java:166) INFO | jvm 1 | 2007/03/06 14:20:37 | at com.atlassian.bamboo.build.DefaultBuildChangeDetector.doTask(DefaultBuildChangeDetector.java:114) INFO | jvm 1 | 2007/03/06 14:20:37 | at com.atlassian.bamboo.build.DefaultBuildChangeDetector.run(DefaultBuildChangeDetector.java:77) INFO | jvm 1 | 2007/03/06 14:20:37 | at edu.emory.mathcs.backport.java.util.concurrent.helpers.ThreadHelpers$1.run(ThreadHelpers.java:34) INFO | jvm 1 | 2007/03/06 14:20:37 | at java.lang.Thread.run(Thread.java:595) Though bamboo itself still claims itself as running. After stop & start all seems to be fine again (seems no data lost). Note 1: there was currently executing another plan Note 2: after re-doing same steps again this did not re-occur. But I noticed by way of a failed build that to my fault the perforce depot referring to in the plan config was not yet included in the perforce client spec. (may be those aspects are related to this issue)

    Atlassian JIRA | 1 decade ago | Johannes Stamminger
    com.atlassian.bamboo.repository.RepositoryException: Failed to get changes: Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4
  2. 0

    While one plan was executing I tried creation of a new one. After having pressed the "Continue" button on the perforce repository details page, the ui was blocked, no interaction any longer possible with the bamboo. In the logfiles I detected entries like INFO | jvm 1 | 2007/03/06 13:37:17 | /usr/local/bin/p4 -u <perforce user> -p <perforce server>:<perforce port> -c <perforce clientspec name> client -o occuring repeatedly multiple times per second (!) without any further error message. Maybe it was not the best idea but I renamed the p4-executable (the morning after a stop-start I had loss of data so I tried to avoid this - but this is a different story). After some time (not immediately!) this perforce server penetration stopped with INFO | jvm 1 | 2007/03/06 14:20:37 | com.atlassian.bamboo.repository.RepositoryException: Failed to get changes: Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | INFO | jvm 1 | 2007/03/06 14:20:37 | at com.atlassian.bamboo.repository.perforce.PerforceRepository.getChangesSinceLastBuild(PerforceRepository.java:290) INFO | jvm 1 | 2007/03/06 14:20:37 | at com.atlassian.bamboo.build.strategy.PollingBuildStrategy.requiresBuild(PollingBuildStrategy.java:126) INFO | jvm 1 | 2007/03/06 14:20:37 | at com.atlassian.bamboo.build.DefaultBuildChangeDetector.checkIfBuildNeedsBuilding(DefaultBuildChangeDetector.java:166) INFO | jvm 1 | 2007/03/06 14:20:37 | at com.atlassian.bamboo.build.DefaultBuildChangeDetector.doTask(DefaultBuildChangeDetector.java:114) INFO | jvm 1 | 2007/03/06 14:20:37 | at com.atlassian.bamboo.build.DefaultBuildChangeDetector.run(DefaultBuildChangeDetector.java:77) INFO | jvm 1 | 2007/03/06 14:20:37 | at edu.emory.mathcs.backport.java.util.concurrent.helpers.ThreadHelpers$1.run(ThreadHelpers.java:34) INFO | jvm 1 | 2007/03/06 14:20:37 | at java.lang.Thread.run(Thread.java:595) Though bamboo itself still claims itself as running. After stop & start all seems to be fine again (seems no data lost). Note 1: there was currently executing another plan Note 2: after re-doing same steps again this did not re-occur. But I noticed by way of a failed build that to my fault the perforce depot referring to in the plan config was not yet included in the perforce client spec. (may be those aspects are related to this issue)

    Atlassian JIRA | 1 decade ago | Johannes Stamminger
    com.atlassian.bamboo.repository.RepositoryException: Failed to get changes: Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4

    Root Cause Analysis

    1. com.atlassian.bamboo.repository.RepositoryException

      Failed to get changes: Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4

      at com.atlassian.bamboo.repository.perforce.PerforceRepository.getChangesSinceLastBuild()
    2. com.atlassian.bamboo
      DefaultBuildChangeDetector.run
      1. com.atlassian.bamboo.repository.perforce.PerforceRepository.getChangesSinceLastBuild(PerforceRepository.java:290)
      2. com.atlassian.bamboo.build.strategy.PollingBuildStrategy.requiresBuild(PollingBuildStrategy.java:126)
      3. com.atlassian.bamboo.build.DefaultBuildChangeDetector.checkIfBuildNeedsBuilding(DefaultBuildChangeDetector.java:166)
      4. com.atlassian.bamboo.build.DefaultBuildChangeDetector.doTask(DefaultBuildChangeDetector.java:114)
      5. com.atlassian.bamboo.build.DefaultBuildChangeDetector.run(DefaultBuildChangeDetector.java:77)
      5 frames
    3. Backport of JSR 166
      ThreadHelpers$1.run
      1. edu.emory.mathcs.backport.java.util.concurrent.helpers.ThreadHelpers$1.run(ThreadHelpers.java:34)
      1 frame
    4. Java RT
      Thread.run
      1. java.lang.Thread.run(Thread.java:595)
      1 frame