This issue has been resolved. Our solution is to restart the server, which is probably your bug. This kind of problem can occur after more than a year of operation. Earlier versions of 2.1 and the like have had similar issues. So the restart is done.
Here are the questions:
It has been running for more than 400 days.
Today, KVM is normal and LXC cannot be started. After logging in the Web management terminal, the display is all "?"
Restarted the relevant service through the following command, logged in the Web management interface shows...
sorry. my system Proxmox VE 4.3 .
I would like to establish a need to use vpn LXC to iptables_nat But suggested that the system does not support.
I need to do so can allow system support?thanks.
LXC CT system : centos 7
version: proxmox 2.1
i have 7 server create Cluster . one day 6 nodes is over . only left server is no master.
i link this server is ok. but i can't modify this server .
add ip address ,
prompt: ovz: command 'vzctl --skiplock set 105 --ipadd 18.104.22.168 --save' failed: exit code...
Proxmox VE version 3.2-1/1933730b
my new create CT . but i can't not console shell.
starting udev:cp:cannot create special file '/dev/console'
cp: cannot create special file '/dev/core':
INIT: no more processes left in this runlevel
can't not command shell why?
but i can...