cloudmin pro bug `Starting up new OpenVZ container ..`

Browser keeps loading even though OpenVZ container started already (but "the ..done message is not showing up")

Verified with vzctl enter 10000

Creating virtual system with OpenVZ ..
.. creation started.

Waiting for creation to complete ...................
.. creation has completed successfully.

Adding OpenVZ container IP address ..
.. done

Setting nameservers to match host system ..
.. done

Updating configuration files with hostname and IP address ..
.. done

Updating network configuration files ..
.. done

Starting up new OpenVZ container .. 


If you login to the host system, is there a command like "vzctl start XXX --wait" running? And if so, try killing it ..

Actually, Cloudmin should only wait 120 seconds for a new container to start up at most..

I didn't see any vzctl start. And Cloudmin waited longer than 120 seconds I think.

Now I tried again and saw three vzstart processes with ps aux | egrep -i vzctl:

root       35528  0.0  0.0   9148   856 ?        S    14:58   0:00 vzctl start 10001 --wait
root       35617  0.0  0.0   9148   232 ?        S    14:58   0:00 vzctl start 10001 --wait
root       35618  0.0  0.0   9148   400 ?        Ss   14:58   0:00 vzctl start 10001 --wait

This time I got the following error message

.. failed to start : Warning: configuration file for distribution cloudmin-10001 not found, using defaults from /etc/vz/dists/default
Starting container ...
Container is unmounted Container is mounted Adding IP address(es):
Setting CPU units: 1000
Set hostname: test File resolv.conf was modified Container start in progress, waiting ... 

But the container started actually successfully and vzctl enter 10001 worked. Although I got the following error message with yum update

Traceback (most recent call last):
  File "/usr/bin/yum", line 29, in ?
    yummain.user_main(sys.argv[1:], exit_code=True)
  File "/usr/share/yum-cli/", line 229, in user_main
    errcode = main(args)

reboot inside the container stopped the contained, but didn't start it.

vzctl start 10001 displayed the following message

Warning: configuration file for distribution cloudmin-10001 not found, using defaults from /etc/vz/dists/default

yum update still doesn't work. I am not sure whether the yum problem is related to the OpenVZ config.

Wow, something really odd is clearly going wrong here..

Any chance I could login to your system myself to debug the underlying issue?

Alternately, which Linux distribution and version, and which OpenVZ packages are you running?

where do I send the password?

Howdy -- you can either mark this ticket as private, and post the login details here -- or you can email those to

If you email it, make sure you include the root password, your server's IP address, and include a link to this request in the message body. Thanks!

I didn't see your email .. what was the subject line?

Got it .. taking a look now.

I looked into this, and found that the issue was your OpenVZ container was taking more than 120 seconds to start up .. although it does start eventually.

The cause of that was the newaliases command taking a long time to run at boot. That in turn happens because it doesn't like the hostname test , as it contains no domain name!

So the solution is to make sure your VM gets created with a proper hostname, like . Normally this would be automatic .. but the DNS issue from your other bug is preventing it. The work-around is to enter a full hostname in the "Internet hostname" field when creating a new OpenVZ container.

Initially I tried the full domain name in Internet hostname for a KVM instance, and got an error message that that it is not allowed (which is the reason why I created the other ticket). But now I tried an fqdn for OpenVZ internet hostname and it went through. Is there a reason for these different rules?

I guess in my case (only one host and two or three containers) it is easier to use the command line (vzctl, vzdump etc) to create containers (while Virtualmin and Webmin are much easier than command line :-).

I am curious, how do you determine that a server is "started"?

Cloudmin uses the command vzlist -a to find the state of all containers ..