Search Engine: Elastic

Article ID: 119591, created on Jan 11, 2014, last review on Feb 6, 2017

  • Applies to:
  • Odin Business Automation Standard 4.5

Symptoms

My container does not appear in Conflict Resolver and cannot be registered in OBAS.

Cause

It's by design that containers with id less than 100 and more than 1000000 do not appear in Conflict Resolver.

Resolution

Change container id on HW node with vzmlocal, new id must be more than 100 and less than 1000000. For example to change container id from %old_id% to %new_id%:

[root@vz_node ~]# vzmlocal %old_id%:%new_id%

Run task "Detected newly appeared Virtuozzo Container conflicts" in OBAS (Top > Configuration Director > Logging and Errors > Action Log > Tasks Queue) to make new container appear in Conflict Resolver.

400e18f6ede9f8be5575a475d2d6b0a6 caea8340e2d186a540518d08602aa065 624ca542e40215e6f1d39170d8e7ec75 70a5401e8b9354cd1d64d0346f2c4a3e

Email subscription for changes to this article
Save as PDF