Hello,
this is my first real posting in the forum.
I am a happy openvz user for more than a year now, I would rate my skills a bit above a beginners level.
Today I'm really stuck and I would be glad if someone had an idea of what I might have done wrong.
About my system:
My system is pure 64bit, currently using centos 5.5 on both sides (host and VE).
Running kernel version: 2.6.18-164.15.1.el5.028stab068.9
Installed software on the host:
vzctl-lib-3.0.25.1-1
ovzkernel-2.6.18-194.26.1.el5.028stab079.2
vzquota-3.0.12-1
ovzkernel-2.6.18-164.15.1.el5.028stab068.9
ovzkernel-2.6.18-194.8.1.el5.028stab070.4
vzctl-3.0.25.1-1
Just to report in advance: I am regularly updating all packages, but the machine is running now for 193 days, so it might be the case that the user space tools have become incompatible with the running kernel and I am not recognizing this. As it is a production system I am avoiding downtime and so on.
That said, here is my issue:
A few days ago I stopped one of my bigger VEs and today I tried to start it up again with no success:
# vzctl --verbose start 204
Starting container ...
umount: /mnt/dir1/root/home/backups: not mounted
Error executing umount script /etc/vz/conf/204.umount
Adding IP address(es): x.x.x.x
Running container script: /etc/vz/dists/scripts/redhat-add_ip.sh
Setting CPU units: 4000
Configuring meminfo: 8048000
Set hostname: xxxxxxx
Running container script: /etc/vz/dists/scripts/redhat-set_hostname.sh
Running container script: /etc/vz/dists/scripts/set_dns.sh
File resolv.conf was modified
Error: Unable to apply new quota values: quota not running
Container start failed (try to check kernel messages, e.g. "dmesg | tail")
Stopping container ...
Container was stopped
Error: Unable to apply new quota values: quota not running
umount: /mnt/dir1/root/home/backups: not mounted
Error executing umount script /etc/vz/conf/204.umount
Just to explain the mounting issues: each of my VE's has a directory "backups" which is just bind-mounted from another drive. As far as I can tell there is no problem with the mount scripts, they always worked well.
A maybe interesting observation:
There is a different VE (CTID 300) that has absolutely no problems with starting/stopping/restarting etc.
A statement about quotas:
I haven't explicitly set up quotas(I think I don't need them), every VE has a own logical volume in a LVM environment. Excuse me if I am missing something here and am asking something really simple, but: I could observe this:
# vzquota show 204
vzquota : (error) Can't open quota file for id 204, maybe you need to reinitialize quota: No such file or directory
vzquota : (error) Quota file must exist for show command
# vzquota show 300
vzquota : (warning) Quota is running, so data reported from quota file may not reflect current values
resource usage softlimit hardlimit grace
1k-blocks 5475684 31457280 31457280
inodes 73450 200000 220000
vzquota off 204
vzquota : (error) Can't open quota file for id 204, maybe you need to reinitialize quota: No such file or directory
Maybe I should try reinitializing? Is this safe? Is there something I am missing? What else could be the case?
Thank you for reading so far and thanks in advance to anyone who can give some advice.
- Oliver
OpenVZ Forum
Members
Search
Help
Register
Login
Home
