Perforce Server Error
Contents |
Users work on files in client workspace directories on their own machines; these files are transferred to and
Perforce Connect To Server Failed Check $p4port
from a shared file repository located on a Perforce server. perforce wsaetimedout Every Perforce system uses one server and can have many client workstations. The following programs do the
Connect To Server Failed Check $p4port Wsaeconnrefused
bulk of Perforce's work: The Perforce Server (p4d) runs on the Perforce server machine, manages the shared file repository, and keeps track of users, workspaces, and other set p4port Perforce metadata. Perforce client programs (such as p4) run on Perforce client machines, sending user requests to the Perforce Server (p4d) for processing. Perforce client programs use TCP/IP to communicate with the Perforce Server. To use Perforce, you must supply your client program with the address and port of the Perforce server to which p4 command line connect to server you want to connect. See "Setting up your environment to use Perforce" on page21 for details. Before you begin This chapter assumes that your system administrator has already installed and configured a Perforce server (p4d) for you, and that the server is up and running. If this is not the case (for instance, if you're installing Perforce for the first time), you must install the Perforce server before continuing. For an overview of how to set up a server, see "Installing Perforce" on page143. The installation information in this manual is intended to help you install a server for evaluation purposes. If you're installing a production server, or are planning on extensive testing of your evaluation server, read the full installation instructions in the System Administrator's Guide. Setting up your environment to use Perforce In order to connect to a Perforce server, you must supply your Perforce client program with two pieces of information: the name of the host on which p4
→ P4V Javascript Disabled Detected You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality. 0 Unable to connect to P4 server from P4V Started by kristo5747, Oct 07 2014 04:48 PM client p4v port number
Perforce Connection Refused
Please log in to reply 7 replies to this topic #1 kristo5747 kristo5747 Newbie Members p4port environment variable 5 posts Posted 07 October 2014 - 04:48 PM My apologies if this is not the correct forum. I am your typical newbie.
Connect To Server Failed; Check $p4port. Wsaetimedout
You've been warned. I have inherited the role of Perforce admin for my team. Our server was installed by my predecessor on a RedHat server. I am trying to connect to it using the P4V client from my https://www.perforce.com/perforce/doc.051/manuals/p4guide/02_connect.html MS Windows workstation so I can create a depot. To get the client info, I logged in to my P4 server `blahblah33` and typed `p4 info`. blahblah33:/home/perforce => p4 info User name: perforce Client name: perforce Client host: blahblah33 Client root: /opt/perforce/WORKSPACE/perforce Current directory: /home/perforce Peer address: 147.22.111.80:14419 Client address: 147.22.111.80 Server address: blahblah:16666 Server root: /opt/perforce/P4ROOT Server date: 2014/10/07 10:31:43 -0600 MDT Server uptime: 15:46:13 Server version: P4D/LINUX26X86_64/2013.2/740201 (2013/11/11) Server license: MYEMPLOYER 36 users (support http://forums.perforce.com/index.php?/topic/3622-unable-to-connect-to-p4-server-from-p4v/ ends 2014/10/16) Server license-ip: 147.22.111.80:16666 Case Handling: sensitive When I enter ` blahblah33:16666` for my server in P4 client, it fails with the error message "Connect to server failed. Check $P4Port" (see attached screenshot). I have checked my hosts file and the ip address to `blahblah33` is correctly listed. I tried using the ip addresss instead of the host name, same error. What I noticed is that the documentation reads that the default port is `1666`, not `16666`. Does it matter? I am not even sure my Perforce server is running. Is there a P4 command I can run to check? Thanks in advance for your help. Back to top #2 P4Sam P4Sam Advanced Member Staff Moderators 484 posts LocationSan Francisco, CA Posted 07 October 2014 - 08:38 PM The "p4 info" output shows that the server is running.Possibly it's not listening on the right network interface?From your server try doing: p4 -p blahblah33:16666 info p4 -p localhost:16666 info If one of those works but not the other (even though they both point to the same machine, right?), you should be able to fix it by restarting the server with a P4PORT of just '16666' (rather than say 'localhost:16666'). Back to top #3 kristo5747 kristo5747 Newbie Members 5 posts Posted 07 October 2014 - 09:39 PM That's interesting. Why does it fail? blahblah33:/home/perforce => p4 -p localhost:16666
are created and edited by users on their own client hosts; these files are transferred to and from a shared file repository located on a Perforce server. Every running Perforce system https://www.perforce.com/perforce/doc.021/manuals/p4guide/02_connect.html uses a single server and can have many clients. As mentioned earlier, two http://ftp.perforce.com/perforce/r97.3/doc/cmdguide/html/connecti.htm programs do the bulk of Perforce's work: The p4d program runs on the Perforce server. It manages the shared file repository, and keeps track of users, clients, protections, and other Perforce metadata. The p4 program runs on each Perforce client. It sends the users' requests to the p4d server program for processing, and connect to communicates with p4d via TCP/IP. Each Perforce client program needs to know the address and port of the Perforce server with which it communicates. This address is stored in the P4PORT environment variable. Before you begin This chapter assumes that your system administrator has already set up a Perforce server (p4d) for you, and that it is already up and running. If this is not the connect to server case (for instance, if you're installing Perforce from scratch), you'll also have to install the Perforce server before continuing. See the appendix, "Installing Perforce" on page129, for information on how to install the server. The information in the appendix is intended to help you install a server for evaluation purposes. If you're installing a production server, or are planning on extensive testing of your evaluation server, we strongly encourage you to read the full installation instructions in the Perforce System Administrator's Guide. Setting up your environment to use Perforce A Perforce client program needs to know two things in order to talk to a Perforce server: the name of the host on which p4d is running, and the port on which p4d is listening These are set via a single environment variable, P4PORT. Note See "Setting and viewing environment variables" on page136 for information about how to set environment variables for most operating systems and shells. If your site is already using Perforce, it's possible that your system administrator has already set P4PORT for you; if not, you'll need to set it yourself. Either way, after setting P4PORT to point to your server, you should verify your