Article ID: 113015, created on Dec 16, 2011, last review on Oct 11, 2015

  • Applies to:
  • Operations Automation 5.4

Symptoms

While preparing for a Parallels Operations Automation (POA) upgrade, it is essential to verify the POA slave node's availability from within the POA internal intercommunication system (CORBA).

Note: this utility has been incorporated into pa_updates_installer precheck.

Resolution

Use the script from the attached archive to verify the POA slave node's availability:

~# ./ping_slave.sh
pinging host 1: SUCCESS
.
.
.
pinging host 13: SUCCESS
pinging host 14: SUCCESS
pinging host 15: FAILED
pinging host 16: FAILED
pinging host 17: FAILED
pinging host 18: FAILED
pinging host 19: SUCCESS
pinging host 20: FAILED

The hosts' initial lookup is done through the database so, in some cases, it will be necessary to adjust the script accordingly.

This script also produces a debug output, which is stored in the file ping.res (in the current directory). This output can be helpful during further troubleshooting.

For example, the hostnames of unavailable hosts can be obtained quickly through:

~# grep ERROR ping.res

Parallels KB article "How to fix unmanageable POA-managed server" also can be helpful during troubleshooting.

Attachments

5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e caea8340e2d186a540518d08602aa065 ac82ce33439a9c1feec4ff4f2f638899 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF