OpenVZ Forum - RDF feed
type: channel
items: Problem starting a copied container
items: Re: Problem starting a copied container

Problem starting a copied container
type: item
description: I created a simple CentOS 6 based container that I plan to use for testing a monitoring system. This container works great by itself. I used the instructions at openvz.org/Cloning_VE to make a copy and changed the hostname and IP address in the config file. But, I can't start the new container. I get the following in vzctl.log: 2014-01-25T19:31:11-0600 vzctl : CT 201 : Starting container... 2014-01-25T19:31:12-0600 vzctl : CT 201 : Container is mounted 2014-01-25T19:31:12-0600 vzctl : CT 201 : Adding IP address(es): 192.168.0.201 2014-01-25T19:31:13-0600 vzctl : CT 201 : Setting CPU limit: 10 2014-01-25T19:31:13-0600 vzctl : CT 201 : Setting CPU units: 1000 2014-01-25T19:31:13-0600 vzctl : CT 201 : Setting CPUs: 1 2014-01-25T19:31:13-0600 vzctl : CT 201 : Container start failed (try to check kernel messages, e.g. "dmesg | tail") 2014-01-25T19:31:13-0600 vzctl : CT 201 : Killing container ... 2014-01-25T19:31:14-0600 vzctl : CT 201 : Locked by: pid 2207, cmdline vzctl start 201 2014-01-25T19:31:14-0600 vzctl : CT 201 : Container already locked 2014-01-25T19:31:15-0600 vzctl : CT 201 : Container was stopped 2014-01-25T19:31:15-0600 vzctl : CT 201 : Container is unmounted It doesn't matter if the original container is running or not. Any clues on this? There is nothing in /vz/lock.
creator: wk38524
date: 2014-01-26T01:36:23-00:00

Re: Problem starting a copied container
type: item
description: so what "dmesg" shows for you about this problem? please report HN linux version, kernel, openvz tools and friends versions. does CT is ploop or simfs layout? please show ctid.conf files from copied CT and new CT.
creator: Paparaciz
date: 2014-01-27T21:23:25-00:00

Re: Problem starting a copied container
type: item
description: Only thing that dmesg shows is: [ 65.901793] CT: 201: started [ 67.204622] CT: 201: stopped I guess it's simfs since the filesystem shows as /dev/simfs ----- Hardware node is CentOS 6.5 Kernel is 2.6.32-042stab084.17 vzctl-core-4.6.1-1.x86_64 vzstats-0.5.2-1.noarch vzquota-3.1-1.x86_64 vzctl-4.6.1-1.x86_64 --- Original container PHYSPAGES="0:51200" DISKSPACE="1024000:1024000" DISKINODES="50000:50000" QUOTATIME="0" CPUUNITS="1000" HOSTNAME="vz200" VE_ROOT="/vz/root/$VEID" VE_PRIVATE="/vz/private/$VEID" OSTEMPLATE="centos-6-x86-20131201" ORIGIN_SAMPLE="basic" IP_ADDRESS="192.168.0.200" NAMESERVER="10.1.1.1" SWAPPAGES="0" CPULIMIT="10" CPUS="1" ONBOOT="yes" --- Copied container PHYSPAGES="0:51200" DISKSPACE="1024000:1024000" DISKINODES="50000:50000" QUOTATIME="0" CPUUNITS="1000" HOSTNAME="vz201" VE_ROOT="/vz/root/$VEID" VE_PRIVATE="/vz/private/$VEID" OSTEMPLATE="centos-6-x86-20131201" ORIGIN_SAMPLE="basic" IP_ADDRESS="192.168.0.201" NAMESERVER="10.1.1.1" SWAPPAGES="0" CPULIMIT="10" CPUS="1" ONBOOT="no"
creator: wk38524
date: 2014-01-28T01:29:05-00:00

Re: Problem starting a copied container
type: item
description: sorry for late reply maybe try to copy CT with rsync? vzmigrate use such options: RSYNC_OPTIONS="-aHAX --delete --numeric-ids"
creator: Paparaciz
date: 2014-01-30T18:34:12-00:00