Article ID: 123262, created on Oct 25, 2014, last review on Oct 25, 2014

  • Applies to:
  • Virtuozzo containers for Linux 4.7
  • Virtual Automation

Symptoms

Updating PVA Agent on PVCfL 4.7 active node triggers relocation

Cause

Cluster is verifying node state by querying three service - vz, pvaagent, pvapp. Relocation occurs because cluster considers node to be down when PVA Agent is getting interrupted during update installation.

Resolution

Prior to updating PVA Agent clustered service should be frozen with a following command:

# clusvcadm -Z <cluster_service_name>

Note, after PVA Agent update installation pvapp and pvaagentd services will be enabled for autostart again, so it will be necessary to disable their automatic startup once again:

# chkconfig pvapp off
# chkconfig pvaagentd off

Once PVA Agent update is finished, verify that services are running using following command:

# pvaagent status;pvapp status
pvaagentd (pid  28063) is running...
pvappd (pid  28118) is running...

If one of the services is not running, start it manually. If both services are running you may unfreeze the clustered service now:

# clusvcadm -U <cluster_service_name>

NOTE: Do not unfreeze the clustered service until you make sure all monitored services are running, otherwise it will trigger relocation.

Search Words

RHCS

agent

PVA

update

RHEL

relocation

cluster

319940068c5fa20655215d590b7be29b 2897d76d56d2010f4e3a28f864d69223 e8e50b42231236b82df27684e7ec0beb d02f9caf3e11b191a38179103495106f 0c05f0c76fec3dd785e9feafce1099a9

Email subscription for changes to this article
Save as PDF