Search Engine: Elastic

Article ID: 132348, created on Mar 7, 2018, last review on Jun 5, 2019

  • Applies to:
  • Operations Automation 8.0
  • Operations Automation 7.3
  • Operations Automation 7.4

Symptoms

  1. APS Booster was configured and all tasks were completed successfully.

  2. UI hosts were connected to Database Replica Nodes be steps from Documentation

  3. Following error appears in /var/log/pa/pui/pui.log on UI hosts:

    00:00:00.001 [EJB default - 7] DEBUG c.o.a.s.b.e.ReplicationAndBoosterStatusBean - replica status check
    00:00:00.005 [EJB default - 7] DEBUG c.o.a.s.b.ejb.WebServerStatusChecker - replica status: replay delay = 168909 ms, WAL diff = 0 bytes
    00:00:00.005 [EJB default - 7] DEBUG c.o.a.s.b.ejb.WebServerStatusChecker - replica is out of sync - 168909 ms since last WAL replay
    00:00:00.005 [EJB default - 7] DEBUG c.o.a.s.b.ejb.WebServerStatusChecker - booster is inactive, replica is out of sync
    
  4. APS REST API requests with OAuth authentication fail with:

    Authorization failed. Invalid authorization signature. Please check application settings.
    

Cause

Database replication does not work due difference in time between UI host and Database Replica node.

Resolution

  1. Make sure that APS Booster is enabled on the UI node:

    # grep apsbooster /usr/local/pem/wildfly-10.1.0.Final/standalone/configuration/standalone_xml_history/standalone-full-ha.boot.xml
    <property name="com.parallels.pui.apsbooster.enabled" value="true"/>
    

    and in runtime:

    # sh /usr/local/pem/wildfly-11.0.0.Final/bin/jboss-cli.sh -c --commands="/system-property=com.parallels.pui.apsbooster.enabled:read-resource"
    {
        "outcome" => "success",
        "result" => {"value" => "true"}
    }
    
  2. Synchronize time between UI host and replication node. More than one minute time difference causes the issue:

    maxReplayDelay = Duration.ofMinutes(1);
    

NOTE: In case UI cluster deployed in Azure, please follow this KB article:

How to change timezone on Azure UI cluster

  1. Make sure that /etc/localtime file is linked to a proper timezone, if not, correct this like in the example below:

    localtime -> /usr/share/zoneinfo/Etc/GMT+8
    

    As an alternative, configure time synchronization services like Chrony or NTPD on the affected hosts.

5356b422f65bdad1c3e9edca5d74a1ae 8fc71f07abe5b233fea1ae0377cd5e3d dd79f16c76b9dca75205ab5e9f5465ea 1941880841f714e458ae4dc3d9f3062d adc6deaa66054d8a194d131ba07f2785 aab95f5cf9bcfa920cc1dda8487f084a 55fe109b4b4fe3fbb893f22dbb85a41a

Email subscription for changes to this article
Save as PDF