Jump to content

p4 stopped working after moving(IP change)

NAS p4 p4d troubleshoot

  • Please log in to reply
1 reply to this topic

#1 BeyondAffinity



  • Members
  • Pip
  • 1 posts

Posted 29 February 2020 - 09:50 AM

I've been using a NAS(Synology) to run p4 / p4d and it worked flawlessly(I think) for past 3 years.

I've recently moved and booted up P4V on my new workstation, and RpcTransport: partner is not a Perforce client/server. is all it spits out now.
I've changed P4PORT according to the new IP, and that's about all I've done on my side, but it just stopped working.

I've searched around for this but can't seem to really troubleshoot this on my own so I post this for some help.

#2 Schiavone1404



  • Members
  • Pip
  • 1 posts

Posted 07 May 2020 - 09:03 AM

I have the exact same problem starting up the perforce server.
I followed the guide to create an startup script using systemd successfully but the result is the same than the original post when trying to start the service.

When running: systemctl start helix-p4dctl

I get this: Job for helix-p4dctl.service failed because the control process exited with error code.
See "systemctl status helix-p4dctl.service" and "journalctl -xe" for details.

And running both give me the same than when using the init.d script so the problem is not how to start it but something else

Also tagged with one or more of these keywords: NAS, p4, p4d, troubleshoot

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users