Search Engine: Elastic

Article ID: 130832, created on May 18, 2017, last review on May 18, 2017

  • Applies to:
  • Operations Automation 7.0

Symptoms

While following the steps to migrate Business Automation Database node, a failed task appears after node reregistration:

Task name Install certificate on node '192.0.2.2'
Output Transaction rolled back

Tracing /var/log/pa/core.log while running the task on OA MN, the following errors appear:

May 18 08:34:33.924 : DBG [task:19375313:27108 RequestProcessor-8752 pau ]: c.p.p.c.ServiceInvoker Service invocation for service HostMngmt$$$view182 took 1 ms
May 18 08:34:33.924 : DBG [task:19375313:27108 1:12659:7f5a80e5f700 lib ]: [ SDK::Platform::performHCL] ===> ENTRY
May 18 08:34:33.924 : DBG [task:19375313:27108 1:12659:7f5a80e5f700 lib ]: [ SDK::Platform::performHCL] performHCL on IOR:0100000...
May 18 08:50:07.744 : DBG [task:19375313:27108 1:12659:7f5a80e5f700 lib ]: [ SDK::Platform::performHCL] <=== EXIT (by exception) [933.820282]
May 18 08:50:07.745 : DBG [task:19375313:27108 RequestProcessor-8823 pau ]: c.p.p.s.h.e.HostMngmtBean CORBA::TRANSIENT|COMM_FAILURE while contacting host 10101, marking it as unmanageable

Port 8352 on BA DB cannot be reached from OA MN:

[root@osscore odin]# telnet 192.0.2.2 8352
Trying 192.0.2.2...
telnet: connect to address 192.0.2.2: No route to host

Cause

BA DB Firewall restricts the connectivity with OA Management Node.

Resolution

Configure the new BA DB node Firewall in accordance with the requirements:

Firewall Configuration Guide

Adding port 8352 to the list of allowed ports will help to finish the task successfully:

# iptables -I INPUT -p tcp -m state --state NEW -m tcp --dport 8352  -j ACCEPT

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 0871c0b47b3b86ae3b1af4c2942cd0ce 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF