com.tek42.perforce.PerforceException: Failed to open connection to: p4

Jenkins JIRA | yschimke | 8 years ago
  1. 0

    After downgrading to 1.0.11 of the perforce plugin, we are occasionally getting the following non fatal Exception. com.tek42.perforce.PerforceException: Failed to open connection to: p4 at com.tek42.perforce.process.CmdLineExecutor.exec(CmdLineExecutor.java:63) at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:184) at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:26) at hudson.plugins.perforce.PerforceSCM.pollChanges(PerforceSCM.java:345) at hudson.model.AbstractProject.pollSCMChanges(AbstractProject.java:633) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:253) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:285) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) at java.util.concurrent.FutureTask.run(FutureTask.java:123) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) Caused by: java.io.IOException: java.io.IOException: Too many open files at java.lang.UNIXProcess.<init>(UNIXProcess.java:148) at java.lang.ProcessImpl.start(ProcessImpl.java:65) at java.lang.ProcessBuilder.start(ProcessBuilder.java:451) at com.tek42.perforce.process.CmdLineExecutor.exec(CmdLineExecutor.java:58) ... 12 more lsof shows that the file count is jumping between high 200s to over 1000 which is when we start getting this error. Most of the file handles are pipes. java 1313 platot 206r FIFO 0,7 101871703 pipe java 1313 platot 207r FIFO 0,7 101876010 pipe java 1313 platot 212r FIFO 0,7 101871708 pipe java 1313 platot 305r FIFO 0,7 101689401 pipe

    Jenkins JIRA | 8 years ago | yschimke
    com.tek42.perforce.PerforceException: Failed to open connection to: p4
  2. 0

    After downgrading to 1.0.11 of the perforce plugin, we are occasionally getting the following non fatal Exception. com.tek42.perforce.PerforceException: Failed to open connection to: p4 at com.tek42.perforce.process.CmdLineExecutor.exec(CmdLineExecutor.java:63) at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:184) at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:26) at hudson.plugins.perforce.PerforceSCM.pollChanges(PerforceSCM.java:345) at hudson.model.AbstractProject.pollSCMChanges(AbstractProject.java:633) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:253) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:285) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) at java.util.concurrent.FutureTask.run(FutureTask.java:123) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) Caused by: java.io.IOException: java.io.IOException: Too many open files at java.lang.UNIXProcess.<init>(UNIXProcess.java:148) at java.lang.ProcessImpl.start(ProcessImpl.java:65) at java.lang.ProcessBuilder.start(ProcessBuilder.java:451) at com.tek42.perforce.process.CmdLineExecutor.exec(CmdLineExecutor.java:58) ... 12 more lsof shows that the file count is jumping between high 200s to over 1000 which is when we start getting this error. Most of the file handles are pipes. java 1313 platot 206r FIFO 0,7 101871703 pipe java 1313 platot 207r FIFO 0,7 101876010 pipe java 1313 platot 212r FIFO 0,7 101871708 pipe java 1313 platot 305r FIFO 0,7 101689401 pipe

    Jenkins JIRA | 8 years ago | yschimke
    com.tek42.perforce.PerforceException: Failed to open connection to: p4
  3. 0

    We’ve upgraded our perforce from 2012.1 to 2012.2, which supports ssl. But with the new version, the perforce plugin is having problem before the sync. It’s trying to run “p4 where” command at // level, instead of the changelist. This was a fixed bug back in 2011 in v1.2.9, which worked with the latest 2012.2. However, the newer 1.3.x won’t work. 1.3.x work fine with perforce 2012.1 with no problem. Upgraded to the latest jenkins, but no difference. copying a segment of the log: === Started by user admin Building remotely on blinnv12g in workspace /scratch/linux86/jks/perforce_test2/dev Using remote perforce client: jkspilot2_p4-161040911 [dev] $ /usr/local/bin/p4 workspace -o jkspilot2_p4-161040911 [dev] $ /usr/local/bin/p4 login -p [dev] $ /usr/local/bin/p4 -P 6BD4xxxxxxxxxxxxxxxxxxxxxxx workspace -o jkspilot2_p4-161040911 Last build changeset: 277259 [dev] $ /usr/local/bin/p4 -P 6BD4xxxxxxxxxxxxxxxxxxxxxxx counter change [dev] $ /usr/local/bin/p4 -P 6BD4xxxxxxxxxxxxxxxxxxxxxxx -s changes //jkspilot2_p4-161040911/...@277260,@277278 [dev] $ /usr/local/bin/p4 -P 6BD4xxxxxxxxxxxxxxxxxxxxxxx describe -s 277277 [dev] $ /usr/local/bin/p4 -P 6BD4xxxxxxxxxxxxxxxxxxxxxxx -G where //... Caught exception communicating with perforce. P4 Where Parsing Error: Some commands just want to watch the database churn. com.tek42.perforce.PerforceException: P4 Where Parsing Error: Some commands just want to watch the database churn. at hudson.plugins.perforce.PerforceSCMHelper.parseWhereMapping(PerforceSCMHelper.java:159) at com.tek42.perforce.parse.Changes.calculateWorkspacePaths(Changes.java:82) at com.tek42.perforce.parse.Changes.getChangelist(Changes.java:71) at com.tek42.perforce.parse.Changes.getChangelistsFromNumbers(Changes.java:425) at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:662) at hudson.model.AbstractProject.checkout(AbstractProject.java:1325) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:682) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:587) at hudson.model.Run.execute(Run.java:1543) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) ERROR: Unable to communicate with perforce. P4 Where Parsing Error: Some commands just want to watch the database churn. Email was triggered for: Failure Sending email for trigger: Failure Sending email to: s@xxx.com Finished: FAILURE ===

    Jenkins JIRA | 4 years ago | Sherrie Ma
    com.tek42.perforce.PerforceException: P4 Where Parsing Error: Some commands just want to watch the database churn.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    We’ve upgraded our perforce from 2012.1 to 2012.2, which supports ssl. But with the new version, the perforce plugin is having problem before the sync. It’s trying to run “p4 where” command at // level, instead of the changelist. This was a fixed bug back in 2011 in v1.2.9, which worked with the latest 2012.2. However, the newer 1.3.x won’t work. 1.3.x work fine with perforce 2012.1 with no problem. Upgraded to the latest jenkins, but no difference. copying a segment of the log: === Started by user admin Building remotely on blinnv12g in workspace /scratch/linux86/jks/perforce_test2/dev Using remote perforce client: jkspilot2_p4-161040911 [dev] $ /usr/local/bin/p4 workspace -o jkspilot2_p4-161040911 [dev] $ /usr/local/bin/p4 login -p [dev] $ /usr/local/bin/p4 -P 6BD4xxxxxxxxxxxxxxxxxxxxxxx workspace -o jkspilot2_p4-161040911 Last build changeset: 277259 [dev] $ /usr/local/bin/p4 -P 6BD4xxxxxxxxxxxxxxxxxxxxxxx counter change [dev] $ /usr/local/bin/p4 -P 6BD4xxxxxxxxxxxxxxxxxxxxxxx -s changes //jkspilot2_p4-161040911/...@277260,@277278 [dev] $ /usr/local/bin/p4 -P 6BD4xxxxxxxxxxxxxxxxxxxxxxx describe -s 277277 [dev] $ /usr/local/bin/p4 -P 6BD4xxxxxxxxxxxxxxxxxxxxxxx -G where //... Caught exception communicating with perforce. P4 Where Parsing Error: Some commands just want to watch the database churn. com.tek42.perforce.PerforceException: P4 Where Parsing Error: Some commands just want to watch the database churn. at hudson.plugins.perforce.PerforceSCMHelper.parseWhereMapping(PerforceSCMHelper.java:159) at com.tek42.perforce.parse.Changes.calculateWorkspacePaths(Changes.java:82) at com.tek42.perforce.parse.Changes.getChangelist(Changes.java:71) at com.tek42.perforce.parse.Changes.getChangelistsFromNumbers(Changes.java:425) at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:662) at hudson.model.AbstractProject.checkout(AbstractProject.java:1325) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:682) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:587) at hudson.model.Run.execute(Run.java:1543) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) ERROR: Unable to communicate with perforce. P4 Where Parsing Error: Some commands just want to watch the database churn. Email was triggered for: Failure Sending email for trigger: Failure Sending email to: s@xxx.com Finished: FAILURE ===

    Jenkins JIRA | 4 years ago | Sherrie Ma
    com.tek42.perforce.PerforceException: P4 Where Parsing Error: Some commands just want to watch the database churn.
  6. 0

    Perforce Plugin - hudson - Hudson Wiki

    hudson-ci.org | 4 months ago
    com.tek42.perforce.PerforceException: No output for: p4 workspace -o SE_SCM_TEST_USER_1

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. com.tek42.perforce.PerforceException

      Failed to open connection to: p4

      at com.tek42.perforce.process.CmdLineExecutor.exec()
    2. com.tek42.perforce
      CmdLineExecutor.exec
      1. com.tek42.perforce.process.CmdLineExecutor.exec(CmdLineExecutor.java:63)
      1 frame