OpenVZ Forum: Support » Problem starting a copied container

Home » General » Support » Problem starting a copied container

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Problem starting a copied container [message #51083]

Sun, 26 January 2014 01:36

wk38524
Messages: 2
Registered: January 2014

Junior Member

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.

Report message to a moderator

Re: Problem starting a copied container [message #51087 is a reply to message #51083]

Mon, 27 January 2014 21:23

Paparaciz
Messages: 302
Registered: August 2009

Senior Member

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.

Report message to a moderator

Re: Problem starting a copied container [message #51088 is a reply to message #51087]

Tue, 28 January 2014 01:29

wk38524
Messages: 2
Registered: January 2014

Junior Member

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"

Report message to a moderator

Re: Problem starting a copied container [message #51090 is a reply to message #51083]

Thu, 30 January 2014 18:34

Paparaciz
Messages: 302
Registered: August 2009

Senior Member

sorry for late reply

maybe try to copy CT with rsync?

vzmigrate use such options:
RSYNC_OPTIONS="-aHAX --delete --numeric-ids"

Report message to a moderator

Previous Topic:	strange behaviour of the node
Next Topic:	LVM checksum problem after yum update from CentOS 5.9 to CentOS 5.10 (w/o vzkernel update)

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Mon Jul 14 15:57:29 GMT 2025

Total time taken to generate the page: 0.01628 seconds