$P4PORTcom.tek42.perforce.PerforceException: Connect to server failed; check $P4PORT

Jenkins JIRA | Robert Boothby | 6 years ago
  1. 0

    We've been trying to configure a Windows 2008R2 slave (our first slave with this OS) to run a job that is already known to run successfully on other Windows XP and 2003 machines. We know that the plugin runs fine on a Windows 2008 master. We have confirmed that Perforce has been installed successfully by running all the equivalent commands from the command line and have checked and double checked the configuration and executable locations. We suspect that the problem is associated with the fact that with Windows 2008 the command line syntax has become far more strict and that the Perforce plugin uses different code paths to build the command line and execute the perforce process. On the master the plugin uses the Launcher classes to run the Perforce binary but on the slave it appears to use CmdLineExecutor class. The following exception is seen in the logs: [TEST_util] $ C:\PROGRA~1\Perforce\p4.exe workspace -o hudson_1_glp_4.0_utility_test-3510769 Caught exception communicating with perforce. Connect to server failed; check $P4PORTcom.tek42.perforce.PerforceException: Connect to server failed; check $P4PORT at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:381) at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:291) at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:53) at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1183) at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:574) at hudson.model.AbstractProject.checkout(AbstractProject.java:1180) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:506) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:422) at hudson.model.Run.run(Run.java:1362) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:145)

    Jenkins JIRA | 6 years ago | Robert Boothby
    $P4PORTcom.tek42.perforce.PerforceException: Connect to server failed; check $P4PORT
  2. 0

    We've been trying to configure a Windows 2008R2 slave (our first slave with this OS) to run a job that is already known to run successfully on other Windows XP and 2003 machines. We know that the plugin runs fine on a Windows 2008 master. We have confirmed that Perforce has been installed successfully by running all the equivalent commands from the command line and have checked and double checked the configuration and executable locations. We suspect that the problem is associated with the fact that with Windows 2008 the command line syntax has become far more strict and that the Perforce plugin uses different code paths to build the command line and execute the perforce process. On the master the plugin uses the Launcher classes to run the Perforce binary but on the slave it appears to use CmdLineExecutor class. The following exception is seen in the logs: [TEST_util] $ C:\PROGRA~1\Perforce\p4.exe workspace -o hudson_1_glp_4.0_utility_test-3510769 Caught exception communicating with perforce. Connect to server failed; check $P4PORTcom.tek42.perforce.PerforceException: Connect to server failed; check $P4PORT at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:381) at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:291) at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:53) at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1183) at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:574) at hudson.model.AbstractProject.checkout(AbstractProject.java:1180) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:506) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:422) at hudson.model.Run.run(Run.java:1362) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:145)

    Jenkins JIRA | 6 years ago | Robert Boothby
    $P4PORTcom.tek42.perforce.PerforceException: Connect to server failed; check $P4PORT
  3. 0

    We've been trying to configure a Windows 2008R2 slave (our first slave with this OS) to run a job that is already known to run successfully on other Windows XP and 2003 machines. We know that the plugin runs fine on a Windows 2008 master. We have confirmed that Perforce has been installed successfully by running all the equivalent commands from the command line and have checked and double checked the configuration and executable locations. We suspect that the problem is associated with the fact that with Windows 2008 the command line syntax has become far more strict and that the Perforce plugin uses different code paths to build the command line and execute the perforce process. On the master the plugin uses the Launcher classes to run the Perforce binary but on the slave it appears to use CmdLineExecutor class. The following exception is seen in the logs: [TEST_util] $ C:\PROGRA~1\Perforce\p4.exe workspace -o hudson_1_glp_4.0_utility_test-3510769 Caught exception communicating with perforce. Connect to server failed; check $P4PORTcom.tek42.perforce.PerforceException: Connect to server failed; check $P4PORT at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:381) at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:291) at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:53) at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1183) at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:574) at hudson.model.AbstractProject.checkout(AbstractProject.java:1180) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:506) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:422) at hudson.model.Run.run(Run.java:1362) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:145)

    Jenkins JIRA | 6 years ago | Robert Boothby
    $P4PORTcom.tek42.perforce.PerforceException: Connect to server failed; check $P4PORT
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    We've been trying to configure a Windows 2008R2 slave (our first slave with this OS) to run a job that is already known to run successfully on other Windows XP and 2003 machines. We know that the plugin runs fine on a Windows 2008 master. We have confirmed that Perforce has been installed successfully by running all the equivalent commands from the command line and have checked and double checked the configuration and executable locations. We suspect that the problem is associated with the fact that with Windows 2008 the command line syntax has become far more strict and that the Perforce plugin uses different code paths to build the command line and execute the perforce process. On the master the plugin uses the Launcher classes to run the Perforce binary but on the slave it appears to use CmdLineExecutor class. The following exception is seen in the logs: [TEST_util] $ C:\PROGRA~1\Perforce\p4.exe workspace -o hudson_1_glp_4.0_utility_test-3510769 Caught exception communicating with perforce. Connect to server failed; check $P4PORTcom.tek42.perforce.PerforceException: Connect to server failed; check $P4PORT at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:381) at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:291) at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:53) at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1183) at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:574) at hudson.model.AbstractProject.checkout(AbstractProject.java:1180) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:506) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:422) at hudson.model.Run.run(Run.java:1362) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:145)

    Jenkins JIRA | 6 years ago | Robert Boothby
    $P4PORTcom.tek42.perforce.PerforceException: Connect to server failed; check $P4PORT
  6. 0

    We've been trying to configure a Windows 2008R2 slave (our first slave with this OS) to run a job that is already known to run successfully on other Windows XP and 2003 machines. We know that the plugin runs fine on a Windows 2008 master. We have confirmed that Perforce has been installed successfully by running all the equivalent commands from the command line and have checked and double checked the configuration and executable locations. We suspect that the problem is associated with the fact that with Windows 2008 the command line syntax has become far more strict and that the Perforce plugin uses different code paths to build the command line and execute the perforce process. On the master the plugin uses the Launcher classes to run the Perforce binary but on the slave it appears to use CmdLineExecutor class. The following exception is seen in the logs: [TEST_util] $ C:\PROGRA~1\Perforce\p4.exe workspace -o hudson_1_glp_4.0_utility_test-3510769 Caught exception communicating with perforce. Connect to server failed; check $P4PORTcom.tek42.perforce.PerforceException: Connect to server failed; check $P4PORT at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:381) at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:291) at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:53) at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1183) at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:574) at hudson.model.AbstractProject.checkout(AbstractProject.java:1180) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:506) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:422) at hudson.model.Run.run(Run.java:1362) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:145)

    Jenkins JIRA | 6 years ago | Robert Boothby
    $P4PORTcom.tek42.perforce.PerforceException: Connect to server failed; check $P4PORT

    1 unregistered visitors
    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. $P4PORTcom.tek42.perforce.PerforceException

      Connect to server failed; check $P4PORT

      at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse()
    2. com.tek42.perforce
      Workspaces.getWorkspace
      1. com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:381)
      2. com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:291)
      3. com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:53)
      3 frames
    3. hudson.plugins.perforce
      PerforceSCM.checkout
      1. hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1183)
      2. hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:574)
      2 frames
    4. Hudson
      Executor.run
      1. hudson.model.AbstractProject.checkout(AbstractProject.java:1180)
      2. hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:506)
      3. hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:422)
      4. hudson.model.Run.run(Run.java:1362)
      5. hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
      6. hudson.model.ResourceController.execute(ResourceController.java:88)
      7. hudson.model.Executor.run(Executor.java:145)
      7 frames