Installation fails, "Unable to start service apnscp: Job for apnscp.service failed because a timeout was exceeded."

Hi,

I ran the bootstrapper on a fresh CentOS 7.5 system on Azure.
3 different attempts and I get:

TASK [apnscp/create-admin : copy] ***********************************************************************************
changed: [localhost]

TASK [apnscp/create-admin : Start apnscp] ***************************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Unable to start service apnscp: Job for apnscp.service failed because a timeout was exceeded. See \"systemctl status apnscp.service\" and \"journalctl -xe\" for details.\n"}

PLAY RECAP **********************************************************************************************************
localhost                  : ok=340  changed=1    unreachable=0    failed=1    skipped=194  rescued=0    ignored=0

Status:

[root@x x]# systemctl status apnscp.service
● apnscp.service - apnscp
   Loaded: loaded (/etc/systemd/system/apnscp.service; enabled; vendor preset: disabled)
   Active: failed (Result: timeout) since Sun 2019-06-30 10:36:43 UTC; 21s ago
   CGroup: /system.slice/apnscp.service
           ├─24974 apnscpd: master
           ├─24995 /usr/sbin/httpd -f /usr/local/apnscp/config/httpd.conf -k start
           ├─24996 /usr/sbin/httpd -f /usr/local/apnscp/config/httpd.conf -k start
           ├─24997 /usr/sbin/httpd -f /usr/local/apnscp/config/httpd.conf -k start
           ├─25093 apnscpd: idle
           ├─33433 apnscpd: master
           ├─33459 housekeeping
           ├─33460 apnscpd: idle
           └─33467 php /usr/local/apnscp/vendor/kelunik/acme-client/bin/acme setup -s acme-staging.api.letsencrypt...

Jun 30 10:36:33 n1 systemd[1]: Starting apnscp...
Jun 30 10:36:43 n1 systemd[1]: apnscp.service start operation timed out. Terminating.
Jun 30 10:36:43 n1 systemd[1]: Failed to start apnscp.
Jun 30 10:36:43 n1 systemd[1]: Unit apnscp.service entered failed state.
Jun 30 10:36:43 n1 systemd[1]: apnscp.service failed.
Jun 30 10:36:50 n1 apnscp.init[33409]: [42B blob data]

Manual attempt also fails:

[root@x x]# systemctl restart apnscp.service
Job for apnscp.service failed because a timeout was exceeded. See "systemctl status apnscp.service" and "journalctl -xe" for details.

Journal shows:

Jun 30 10:45:44 n1 systemd[1]: Starting apnscp...
-- Subject: Unit apnscp.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit apnscp.service has begun starting up.
Jun 30 10:45:54 n1 systemd[1]: apnscp.service start operation timed out. Terminating.
Jun 30 10:45:54 n1 systemd[1]: Failed to start apnscp.
-- Subject: Unit apnscp.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit apnscp.service has failed.
--
-- The result is failed.

A manual reboot of the system didn’t help. Trying to resume after a reboot:

TASK [common/acquire-lock : Check if PID /proc/5110/comm present] ***************************************************************************************************************************************************************************
ok: [localhost]

TASK [common/acquire-lock : Verify process matches ansible] *********************************************************************************************************************************************************************************
Pausing for 30 seconds
(ctrl+C then 'C' = continue early, ctrl+C then 'A' = abort)
[common/acquire-lock : Verify process matches ansible]
Ansible running with PID 5110.
Start time: 2019-06-30 11:00:49
Waiting for completion. My PID: 10313.
:
Press 'C' to continue the play or 'A' to abort
FAILED - RETRYING: Verify process matches ansible (30 retries left).
Pausing for 30 seconds

...

FAILED - RETRYING: Verify process matches ansible (1 retries left).
Pausing for 30 seconds
(ctrl+C then 'C' = continue early, ctrl+C then 'A' = abort)
[common/acquire-lock : Verify process matches ansible]
Ansible running with PID 5110.
Start time: 2019-06-30 11:00:49
Waiting for completion. My PID: 10313.
:
Press 'C' to continue the play or 'A' to abort
fatal: [localhost]: FAILED! => {"attempts": 30, "changed": false, "delta": 7, "echo": true, "rc": 0, "start": "2019-06-30 11:05:56.755575", "stderr": "", "stdout": "Paused for 7.36 seconds", "stop": "2019-06-30 11:06:04.112097", "user_input": ""}

NO MORE HOSTS LEFT **************************************************************************************************************************************************************************************************************************

PLAY RECAP **********************************************************************************************************************************************************************************************************************************
localhost                  : ok=4    changed=0    unreachable=0    failed=1    skipped=1    rescued=0    ignored=0

Has anyone encountered and resolved this?

Thanks

An update of all packages and upgrade of CentOS to 7.6 seems to have helped.

Which MySQL distribution? 10.3, 10.2, 10.1, or 10.0? And were you on apnscp v3.0.41 or 3.0.42? 3.0.42 was pushed yesterday that included a fix for a deprecation warning in phpredis impacting panel startup.

Installer automatically runs on boot if it hasn’t completed yet. That lock above indicates it’s already running in the background :slight_smile:

MySQL 10.3, apnscp v3.0.42

Silly me! I have never used Ansible before so that wasn’t very clear to me, I should’ve watched the log file instead of trying to resume. I will run another clean install just to get a little more experience with the process.

Thanks, Matt!

Let me know if you can reliably reproduce it. I built out on a 2 GB Vultr server just now with stock configuration, no issues.

Panel updates every night in addition to system packages when released, so you shouldn’t need to worry about manually updating anything. :+1: