Article ID: 127077, created on Oct 3, 2015, last review on Oct 3, 2015

  • Applies to:
  • Odin Business Automation Standard 4.5

Symptoms

OBAS can not provision new subscriptions to a certain Plesk node after the Plesk node container was migrated to a new Virtuozzo hardware node.

Cause

New Virtuozzo Hardware node with migrated Plesk Container is not added to OBAS.

Resolution

  1. Go Top > Service Director > Virtuozzo Manager > Nodes and add new the hardware node with the migrated Plesk Container.
  2. Go Top > Migration Director > Conflict Resolver > Containers and resolve the conflict with the Plesk Container.
  3. Go Top > Service Director > Plesk Manager > Nodes > Plesk_node > General Settings tab and check settings in Plesk Container Properties section. Please make sure that the new hardware node is specified there. If the Container ID was changed during the migration it should be changed accordingly in Plesk Container Properties section.

Search Words

Plesk Container

billing hosting

624ca542e40215e6f1d39170d8e7ec75 caea8340e2d186a540518d08602aa065 400e18f6ede9f8be5575a475d2d6b0a6 70a5401e8b9354cd1d64d0346f2c4a3e

Email subscription for changes to this article
Save as PDF