Jump to content


Latest Version Fails to Start


  • Please log in to reply
2 replies to this topic

#1 brians

brians

    Newbie

  • Members
  • Pip
  • 1 posts

Posted 06 July 2019 - 01:55 AM

Hi - Hopefully someone can help me figure out what broke in my installation of p4d.

Was running the previous 2019.1 release without issue, but the latest maintenance release failed installation and I can't get the daemon to start.

This is running on ubuntu 16.04:

$ cat /var/log/dpkg.log.1 | grep upgrade | grep helix
2019-07-01 11:35:56 upgrade helix-cli:amd64 2019.1-1796703~xenial 2019.1-1813586~xenial
2019-07-01 11:35:56 upgrade helix-cli-base:amd64 2019.1-1796703~xenial 2019.1-1813586~xenial
2019-07-01 11:35:56 upgrade helix-p4dctl:amd64 2019.1-1796703~xenial 2019.1-1813586~xenial
2019-07-01 11:35:57 upgrade helix-p4d:amd64 2019.1-1796703~xenial 2019.1-1813586~xenial
2019-07-01 11:35:57 upgrade helix-p4d-base:amd64 2019.1-1796703~xenial 2019.1-1813586~xenial
2019-07-01 11:35:57 upgrade helix-p4d-base-19.1:amd64 2019.1-1796703~xenial 2019.1-1813586~xenial

$ sudo dpkg --configure -a
Setting up helix-p4dctl (2019.1-1813586~xenial) ...
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.
invoke-rc.d: initscript helix-p4dctl, action "start" failed.
● helix-p4dctl.service - LSB: Starts all Perforce services
   Loaded: loaded (/etc/init.d/helix-p4dctl; bad; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2019-07-01 17:11:34 PDT; 9ms ago
Docs: man:systemd-sysv-generator(8)
  Process: 5155 ExecStart=/etc/init.d/helix-p4dctl start (code=exited, status=1/FAILURE)

Jul 01 17:11:33 ubu64 systemd[1]: Starting LSB: Starts all Perforce services...
Jul 01 17:11:34 ubu64 systemd[1]: helix-p4dctl.service: Control process exited, code=exited status=1
Jul 01 17:11:34 ubu64 systemd[1]: Failed to start LSB: Starts all Perforce services.
Jul 01 17:11:34 ubu64 systemd[1]: helix-p4dctl.service: Unit entered failed state.
Jul 01 17:11:34 ubu64 systemd[1]: helix-p4dctl.service: Failed with result 'exit-code'.
dpkg: error processing package helix-p4dctl (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of helix-p4d:
helix-p4d depends on helix-p4dctl (>> 2018.2-1672238~); however:
  Package helix-p4dctl is not configured yet.

dpkg: error processing package helix-p4d (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
helix-p4dctl
helix-p4d

$ systemctl status helix-p4dctl.service
● helix-p4dctl.service - LSB: Starts all Perforce services
   Loaded: loaded (/etc/init.d/helix-p4dctl; bad; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2019-07-01 21:30:04 PDT; 8s ago
Docs: man:systemd-sysv-generator(8)
  Process: 10311 ExecStart=/etc/init.d/helix-p4dctl start (code=exited, status=1/FAILURE)

Jul 01 21:30:03 ubu64 p4dctl[10324]: error: Connect to server failed; check $P4PORT.
connect: 127.0.0.1:1666: Connection refused
Jul 01 21:30:04 ubu64 systemd[1]: helix-p4dctl.service: Control process exited, code=exited status=1
Jul 01 21:30:04 ubu64 systemd[1]: Failed to start LSB: Starts all Perforce services.
Jul 01 21:30:04 ubu64 systemd[1]: helix-p4dctl.service: Unit entered failed state.
Jul 01 21:30:04 ubu64 systemd[1]: helix-p4dctl.service: Failed with result 'exit-code'.



  124,0-1    Bot

#2 Domenic

Domenic

    Advanced Member

  • Members
  • PipPipPip
  • 98 posts

Posted 08 July 2019 - 06:44 PM

Have you checked the Perforce server log file? That may provide better info than what the OS is logging..

If the previous version worked and all you did was update the executables maybe your license has expired?

#3 Matt Janulewicz

Matt Janulewicz

    Advanced Member

  • Members
  • PipPipPip
  • 172 posts
  • LocationSan Francisco, CA

Posted 17 July 2019 - 09:06 AM

Dumb, uninformed suggestion (from a RedHat guy no less), but often (but not always) "journalctl -xe" spits out more error messages when service status isn't helpful.
-Matt Janulewicz
Staff SCM Engineer, Perforce Administrator
Dolby Laboratories, Inc.
1275 Market St.
San Francisco, CA 94103, USA
majanu@dolby.com




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users