| Debian 6 container not starting after vzctl/kernel upgrade [message #51911] |
Mon, 09 March 2015 11:34  |
balrog77
Messages: 3
Registered: March 2015
|
Junior Member |
|
|
Hello.
I have an old container with Debian 6, migrated from 32-bit OpenVZ NH. All was working ok for more than a year, but this night we rebooted the server (it is now, after reboot, running 2.6.32-042stab102.9 and vzctl 4.8) and this container wont start:
[root@cs12522 /]#vzctl start 202
Starting container...
Container is mounted
Adding IP address(es): 31.131.x.212
/bin/bash: command substitution: line 416: syntax error near unexpected token `)'
/bin/bash: command substitution: line 416: `cidr2mask $_MASK)'
Setting CPU units: 1000
Container start in progress...
[root@cs12522 /]#
These are running processes and tcp/ip configuration in container:
[root@cs12522 log]# vzctl enter 202
entered into CT 202
root@vz202:/# cat /etc/issue
Debian GNU/Linux 6.0 \n \l
root@vz202:/# ps fax
PID TTY STAT TIME COMMAND
1 ? Ss 0:00 init [2]
2 ? S 0:00 [kthreadd/202]
3 ? S 0:00 \_ [khelper/202]
36 ? Ss 0:00 /sbin/getty 38400 console
37 tty2 Ss+ 0:00 /sbin/getty 38400 tty2
38 ? Ss 0:00 vzctl: ttyp0
39 ttyp0 Ss 0:00 \_ -bash
43 ttyp0 R+ 0:00 \_ ps fax
root@vz202:/# ifconfig -a
lo Link encap:Local Loopback
LOOPBACK MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
BROADCAST POINTOPOINT NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
root@vz202:/#
Software versions:
Kernel: 2.6.32-042stab102.9
Vzctl: 4.8
Container config:
# RAM
PHYSPAGES="0:1835008"
# Swap
SWAPPAGES="0:512M"
# Disk quota parameters (in form of softlimit:hardlimit)
DISKSPACE="10485760:10485760"
DISKINODES="1000000:1000000"
QUOTATIME="0"
# CPU fair scheduler parameter
CPUUNITS="1000"
VE_ROOT="/vz/root/$VEID"
VE_PRIVATE="/vz/private/$VEID"
OSTEMPLATE="debian-6.0-x86"
ORIGIN_SAMPLE="basic"
IP_ADDRESS="31.131.x.212"
NAMESERVER="8.8.8.8 8.8.4.4"
HOSTNAME="vz202.priment.ru"
PRIVVMPAGES="unlimited"
LOCKEDPAGES="unlimited"
ONBOOT="yes"
Please help me revive the container, perhaps some additional info is needed?
Thanks in advance!
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
