Article ID: 119395, created on Dec 28, 2013, last review on May 7, 2014

  • Applies to:
  • Odin Business Automation Standard 4.x

Symptoms

All containers on a HW node are shown on both "Containers" and "Conflicts" tab:

Top > Service Director > Virtuozzo Manager > Nodes > %hwnode% > Containers

Top > Service Director > Virtuozzo Manager > Nodes > %hwnode% > Conflicts

Why this happen?

Troubleshooting

List of containers on this node is not updated in PBA-S correctly.

Enable DEBUG level in PBA-S log and run periodic task "Detected newly appeared Virtuozzo VE conflicts" (Top > Configuration Director > Logging and Errors > Action Log > Tasks Queue).

The logs indicate that PBA-S requested the HW node for the list of containers, but no reply has been received within 30 minutes:

/var/log/hspc/hspc.log
--->8---
[2013/12/27 16:39:27] [DEBUG] [25893] [HSPC::MT::OM::check_for_conflicts] Looking for conflicts for hw # %hw_id%
...
[2013/12/27 16:39:27] [INFO] [25893] [HSPC::OnDemand::VZAgent::open_hn_connection] Connected to Node 123.123.123.10
[2013/12/27 16:39:27] [INFO] [25893] [HSPC::OnDemand::open_hn_connection] RETURN=0
[2013/12/27 16:39:27] [DEBUG] [25893] [HSPC::OnDemand::AUTOLOAD] [VZI/OnDemand]: Called get_allve_info('HASH(0x23311cf8)','HASH(0x2583e008)')
[2013/12/27 16:39:27] [DEBUG] [25893] [HSPC::VZAgent::AbstractGate::new] Transport detected as param #1
[2013/12/27 16:39:27] [DEBUG] [25893] [HSPC::VZAgent::AbstractGate::new] new(): Creating class: `HSPC::VZAgent::VZA46::HNGate'
[2013/12/27 16:39:27] [DEBUG] [25893] [HSPC::VZAgent::VZA46::HNGate::list_ve] Getting VE LIST
---8<---

/var/log/hspc/vzagent.log
--->8---
[Fri Dec 27 16:39:27 2013] 25893: > 123.123.123.10 VZAgent
<packet id="1144" version="4.0.0" xmlns:ns1="http://www.swsoft.com/webservices/vza/4.0.0/vzatypes" xmlns:ns2="http://www.swsoft.com/webservices/vzl/4.0.0/backupm" xmlns:xsi="http://www.w3.org/2001/XMLSchema-i
nstance">
  <data>
    <vzaenvm>
      <get_info>
        <config></config>
      </get_info>
    </vzaenvm>
  </data>
  <target>vzaenvm</target>
</packet>

[Fri Dec 27 17:09:27 2013] 25893: < 123.123.123.10  VZAgent
<packet id="1144" origin="vzaenvm" priority="-6000" target="vzclient1176-4cec4a3a-21b7-25b1-b06e-577268f6984c" time="2013-12-28T01:09:31+0000" version="4.0.0" xmlns:ns1="http://www.swsoft.com/webservices/vzl/
4.0.0/protocol" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <data>
    <error code="307" message="Message processing was terminated because timeout was reached waiting for a response" />
  </data>
  <dst director="gend" />
</packet>
---8<---

Where 123.123.123.10 is IP Address of the %hwnode% in question.

Cause

The issue is likely caused by outdated VZAgent 4.6 on HW node.

For Parallels Virtuozzo Containers for Linux:

[root@hw_node ~]# rpm -q pva-release
pva-release-<OUTDATED_VERSION>

For Parallels Virtuozzo Containers for Windows:

HW NODE: Start > Control Panel > Programs and Features 
--->8---
Parallels Virtuozzo Automation  <OUTDATED_VERSION>
---8<---

Resolution

Upgrade VZAgent to the latest version.

Remember to verify and upgrade your PBA-S and Parallels Virtuozzo Containers to the latest version.

Additional information

Running Virtuozzo Containers are shown with status Offline in PBA-S

Search Words

Containers

all containers in a node conflicted

outdated vzagent

incorrect containers list

Message processing was terminated because timeout was reached waiting for a response

Conflicts

400e18f6ede9f8be5575a475d2d6b0a6 caea8340e2d186a540518d08602aa065 70a5401e8b9354cd1d64d0346f2c4a3e

Email subscription for changes to this article
Save as PDF