post upgrade 1.9 to 2.1 vz restart

P

pecito

New Member
Aug 6, 2012
10
0
1
Hi,
After upgrade from 1.9. to 2.1
after restarting vz

Code: 
 /etc/init.d/vz restartShutting down CT 2197
Bringing down interface venet0: ..done
Stopping OpenVZ: ..done
Starting OpenVZ: ..done
Bringing up interface venet0: ..done
host:~# vzlist 
Container(s) not found

container does not starting.
i using kernel
2.6.32-13-pve #1 SMP Mon Jul 9 08:39:20 CEST 2012 x86_64 GNU/Linux
before upgrade it was ok.
if i start them manualy all is ok.
In the var/log/vzctl.log i only see that
Code: 
vzctl : WARNING: Settings were not saved to config and will be lost after CT restart (use --save flag)

and nothing more.
after reboot of the server node they started.

please advise what to do.
 
Yes
Downloaded from your site.
And we have 3 nodes and they are
With the same problem
 
Last edited:
this is output

-rw-r----- 1 root www-data 1396 Aug 9 16:32 2197.conf
-rw-r----- 1 root www-data 1434 Aug 6 14:24 2197_old.conf
-rw-r----- 1 root www-data 1370 Aug 9 16:32 2200.conf
-rw-r----- 1 root www-data 1376 Aug 9 16:32 2201.conf
-rw-r----- 1 root www-data 1377 Aug 9 16:32 2202.conf
-rw-r----- 1 root www-data 1379 Aug 9 16:32 2251.conf
 
hi, again
The problem is that:
we made some backup script that every night
stop vz
/etc/init.d/vz stop
make snapshot of the lvm disks
lvcreate -s -n data-snap -L70G r5/data
where are all vps
and after that start vz
/etc/init.d/vz start
and after that all active vps have to be started again.
but they not starting.
I manualy checked commands
and they not started too.
the output was posted before.
Before upgrade it work fine.
If the way to start all vps is different tell me.
Because i think it is not necessary to reboot the server every night.
 
pecito said:
/etc/init.d/vz start
and after that all active vps have to be started again.
Click to expand...

Yes, we do not start any containers with '/etc/init.d/vz start' anymore, because
we introduced global startup ordering.

VMs and Containers are now started with '/etc/init.d/pve-manager start'
 
I guess you should modify you script to start/stop container itself. Stopping /etc/init.d/vz seems to be the wrong approach.
 
i guess first execute

# vzctl set <ctid> --bootorder <N>

to make an order of starting

and then check stop/start of pve-manager.
 
Is there a way to manage bootorder via
web interface of proxmox
because i find and read this URL
http://pve.proxmox.com/wiki/File:Screen-Startup-order.png

but in my menu only 6 rows in section options of my vps
i have only ==> start at boot, template, storage, cpu units,quota UGID limit, quota grace period.

nothing more
from png file i see that there are 11 , maybe it is for KVM only.
 
You must log in or register to reply here.
Top Bottom