Article ID: 118098, created on Oct 22, 2013, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo containers for Linux 4.7

Symptoms

I have a Virtuozzo Container subscription in OBAS. I made a container disabled from command line:

~# vzctl CT_ID --disable yes --save

Will container be started through OBAS?

Cause

With OBAS 4.3.4 and PVA 6.0: when container start was disabled with "--disable yes", it cannot be started because of the following error:

/var/log/hspc/hspc.log
---8<---
[2013/10/19 09:11:45] [DEBUG] [10257] [HSPC::ErrorStack::set_last_error] [ErrorStack]: 131327 VZAgent provisioning error.
[2013/10/19 09:11:45] [WARN] [10257] [HSPC::VZAgent::_report_problem] Error invoking external utility: vzctl start #CT_ID failed: Container start functionality is disabled
[2013/10/19 09:11:45] [ERROR] [10257] [HSPC::VZAgent::_report_problem] Error invoking external utility: vzctl start #CT_ID failed: Container start functionality is disabled
--->8--- 

Resolution

Upgrade OBAS to version 4.3.4 and PVA on HW node to 6.0 or above. Refer to these KB articles for the details:

Parallels Virtual Automation builds, releases, and supported virtualization products

How to upgrade OBAS system to the latest available version?

Search Words

--disable yes

disabled failed

Container start functionality is disabled

e8e50b42231236b82df27684e7ec0beb 2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f 400e18f6ede9f8be5575a475d2d6b0a6 caea8340e2d186a540518d08602aa065 0c05f0c76fec3dd785e9feafce1099a9

Email subscription for changes to this article
Save as PDF