Symptoms

  1. Service 'pau' does not start. Operation fails with error:

    [root@osscore ~]# /etc/init.d/pau start
Starting pau (via systemctl):  Job for pau.service failed because the control process exited with error code. See "systemctl status pau.service" and "journalctl -xe" for details.
                                                           [FAILED]

  2. System log /var/log/messages contains the record like:

    Apr  5 02:44:55.012 pau[4423]: pau started with errors, please see server log for details
Apr  5 02:44:55.012 pau[4423]: [  OK  ]
Apr  5 02:44:55.012 systemd[1]: Started SYSV: WildFly startup script.
Apr  5 02:44:55.012 systemd[1]: Starting SYSV: Starts and stops the PA service...
Apr  5 02:45:04.222 pa-agent[5414]: Starting pa-agent: SCMonitor::startAllSC failed: Failed to list active SCs. Is service pau running?
Apr  5 02:45:04.799 systemd[1]: pa-agent.service: control process exited, code=exited status=1
Apr  5 02:45:04.799 pa-agent[5414]: start failed

  3. Service pa-agent is not running on the node:

    [root@osscore ~]# service pa-agent status
pa-agent is stopped

Cause

Server is not productive enough to start 'pau' fast enough before the operation is interrupted by timeout.

Resolution

Contact Odin Technical Support to work around the case.

Internal content

Link on internal Article