Search Engine: Elastic

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

  • Applies to:
  • Operations Automation 7.3

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
    

Cause

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

Resolution

  1. Make sure that apsbooster 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"/>
    
  2. Synchronize time between UI host and replication node. More then one minute time difference causes the issue:

    maxReplayDelay = Duration.ofMinutes(1);
    
  3. Make sure that /etc/localtime file is linked to proper timezone, if not, please correct this like in the example below:

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

    As alternative, you can configure time synchronization services like Chrony or NTPD on affected hosts.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 dd79f16c76b9dca75205ab5e9f5465ea 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF