Article ID: 129626, created on Oct 17, 2016, last review on Nov 15, 2016

  • Applies to:
  • Odin Business Automation Standard 4.5

Symptoms

A Container was migrated manually between Virtuozzo hardware nodes registered in OBAS. Despite the OBAS version 4.5.6, there are two conflicts under Top > Migration Director > Conflicts Resolver > Containers

#1042 container.tld     Container is not registered.           target_node      192.168.0.5
#1042 container.tld     Container was not found on the node.   source_node      192.168.0.5

Cause

One or several of application templates installed on the affected container are not synchronized with the destination (target) hardware node.

The task Detected newly appeared Virtuozzo Container conflicts results in the following messages displayed in DEBUG OBAS log (/var/log/hspc/hspc.log):

[2016/10/04 11:36:23] [DEBUG] [32145] [HSPC::MT::OM::VE::check] TRACE [02]: . -> HSPC::MT::OM::VE->check (no_expand_ips=>1; sec_env=>; skip_apps=>1; skip_hosts=>1; skip_billing=>1; strict_ip_checking=>; skip_qos=>1; skip_dns=>1; hwn_rule=>; skip_notification=>1; strict_hw_checking=>; skip_ip=>1; skip_hw_check=>) =>  found errors: Application template Plesk8-vault is not synchronized with hardware node target_node.tld.
Application template Pp is not synchronized with hardware node target_node.tld.
Application template Pp-watchdog is not synchronized with hardware node target_node.tld.
Application template Pp-webmail is not synchronized with hardware node target_node.tld.
Application template Pp-migration is not synchronized with hardware node target_node.tld.
Application template Pp-panel-addons is not synchronized with hardware node target_node.tld.
Application template Pp-webhosting-addons is not synchronized with hardware node target_node.tld.
Application template Pp-preconfigure is not synchronized with hardware node target_node.tld.
Application template Pp-bind is not synchronized with hardware node target_node.tld.
Application template Ls-techtools is not synchronized with hardware node target_node.tld.
Application template Pp-postfix is not synchronized with hardware node target_node.tld.
Application template Pp-nginx is not synchronized with hardware node target_node.tld.
[2016/10/04 11:36:23] [DEBUG] [32145] [HSPC::Transaction::__logstr] TRANSACTION #16 [01] rollback HSPC::MT::OM::VE->save
[2016/10/04 11:36:23] [DEBUG] [32145] [HSPC::WebDB::_db_rollback] ROLLBACK TRANSACTION (MAIN)
[2016/10/04 11:36:23] [WARN] [32145] [HSPC::MT::OM::VE::save] Virtuozzo Container: Error occurred while saving Virtuozzo Container: Application template Plesk8-vault is not synchronized with hardware node target_node.tld.

......

Applications may be different in your case.

Resolution

Please make sure that the application templates in question are Synchronized: go Top > Service Director > Virtuozzo Manager > Nodes > <hardware_node_name> > Applications, search for the affected application template, select it and press the Synchronize button.

After the templates are Synchronized, wait for the periodic task Detected newly appeared Virtuozzo Container conflicts to complete or run it manually to speed up the procuedure.

See also

Manual Container migration between Virtuozzo nodes

Synchronizing Templates With Hardware Nodes

Search Words

application is not synchronized with hardware node

vzmigrate

Error occurred while saving Virtuozzo Container

conflicts resolver

624ca542e40215e6f1d39170d8e7ec75 caea8340e2d186a540518d08602aa065 400e18f6ede9f8be5575a475d2d6b0a6 70a5401e8b9354cd1d64d0346f2c4a3e

Email subscription for changes to this article
Save as PDF