Article ID: 129490, created on Sep 22, 2016, last review on Sep 30, 2016

  • Applies to:
  • Odin Business Automation Standard 4.5

Symptoms

On attempt to migrate a container via OBAS, container's status is changed to Migrating, appropriate actions are displayed in the Action Log. However, after some time the status of the container is reverted, related Actions stuck in In progress state, the container remains on the source hardware node.

Cause

Migration procedure fails by timeout directly on the hardware node. The following records can be found in /var/log/pva/agent/agent.log:

T=23:10:50:106; L=(inf); PID=49371; TID=7fde40fba700; P=VZLConnection [LoopThreadProc] New Event Loop Thread has been started, see thread ID
T=23:10:50:196; L=(inf); PID=49371; TID=7fde4d9a4760; P=VZLMigratorLocal [migrateVirtualToVirtual] [migrateVirtualToVirtual] migrate EID=b45651f6-4ada-3443-b24b-260bb1cf8957, timeout=36000
T=23:10:50:376; L=(inf); PID=49374; TID=7fde4d9a4760; P=VZLControl [OpProc] New Operator Thread Started [processm]
T=23:10:50:377; L=(udf); PID=49374; TID=7fde4d9a4760; P=VZLCommon [configure] log_level set to: 3
T=23:10:50:381; L=(inf); PID=49374; TID=7fde4d9a4760; P=VZLControl Reconfigure plugins log, func: 0, process:, ignore:
T=23:10:53:134; L=(udf); PID=35171; TID=7fde4d9a4760; P=VZABasicFunctionality [timeoutEvent] Process status change ctid#1234 (b45651f6-4ada-3443-b24b-260bb1cf8957) old:3/0 -> new:3/10

After 10 hours (36000 timeout value):

T=09:10:50:829; L=(inf); PID=35035; TID=7fde4d9a4760; P=VZLControl [terminate] Terminating 49374
T=09:10:50:829; L=(inf); PID=35035; TID=7fde4d9a4760; P=VZLControl [terminate] Terminating 49371
T=09:10:50:844; L=(inf); PID=35035; TID=7fde4d9a4760; P=VZLControl [close] Close transport 49374 with code -4: Connection closed
T=09:10:50:854; L=(inf); PID=35035; TID=7fde4d9a4760; P=VZLControl [disconnect] Disconnect transport 49374
T=09:10:50:871; L=(inf); PID=35035; TID=7fde4d9a4760; P=VZLControl [close] Close transport 49371 with code -4: Connection closed
T=09:10:50:969; L=(inf); PID=35035; TID=7fde4d9a4760; P=VZLControl [disconnect] Disconnect transport 49371
T=09:10:51:087; L=(inf); PID=35162; TID=7fde4d9a4760; P=VZLOperatorCommon [disconnectClient] proc_info: Stopping the monitor for relocator
T=09:10:51:177; L=(inf); PID=35174; TID=7fde4d9a4760; P=VZLOperatorCommon [disconnectClient] vzaproc_info: Stopping the monitor for relocator
T=09:11:03:062; L=(udf); PID=35171; TID=7fde4d9a4760; P=VZABasicFunctionality [timeoutEvent] Process status change ctid#1234 (b45651f6-4ada-3443-b24b-260bb1cf8957) old:3/10 -> new:3/0

The issue is likely related to the size of the container:

# vzquota show 1234
   resource          usage       softlimit      hardlimit    grace
  1k-blocks      129601788       167772160      167772160
     inodes        4407831        16000000       16000000

Resolution

OBAS does not manage migration timeout. This option is set on hardware node.Please consider to perform migration directly on the hardware node by following the steps below:

  1. Before performing migration please follow recommendations from Virtuozzo KB Preparing containers for migration.

  2. Migrate container in question by the following command:

    # vzmigrate root@192.168.0.2 1234 --keep-dst --timeout 72000
    

    where "192.168.0.2" is the IP address of a destination node, "1234" -- the container ID.

  3. After migration is completed, run the task Detected newly appeared Virtuozzo Container conflicts under Top > Configuration Director > Logging and Errors > Action Log > Tasks Queue tab.
  4. Go Top > Migration Director > Conflicts Resolver > Containers and search for conflicts by the container ID "1234". Two conflicts will be displayed: press on Container is not registered.

    screen _1

  5. On the next screen choose choose "Register this Container (recommended) option and press "Next".

    alttext

  6. On the next screen choose Change HW node for the Container registered in system (this Container just has been migrated manually) option and press "Next".

    alttext

As a result the container will change its location in OBAS and will be bound to its subscription.

See also

Container migration fails: Connection reset by peer

Search Words

manual migration

migration

direct container migration

conflicts resolver

624ca542e40215e6f1d39170d8e7ec75 caea8340e2d186a540518d08602aa065 400e18f6ede9f8be5575a475d2d6b0a6 70a5401e8b9354cd1d64d0346f2c4a3e

Email subscription for changes to this article
Save as PDF