Search results

I had a similar problem and had to reboot the hardware node. Also, when rebooting it could not stop the 1 problem container. So I had to kill -9 that process in order to let the reboot continue. I did see before the problem with the container that the DCACHESIZE limit was being hit in...

Possibly the BlueOnyx system is rewriting it. I went ahead and just set up a cron to run the script below to check and fix it. #!/usr/bin/perl #checks the network config file $tempfile = "/root/tempfile.txt"; if (-e "$tempfile") { system ("rm $tempfile"); } $conffile =...

Dietmar Thanks for your reply. The output of the pveversion -v is: pve-manager: 1.6-2 (pve-manager/1.6/5087) running kernel: 2.6.32-3-pve proxmox-ve-2.6.32: 1.6-14 pve-kernel-2.6.32-3-pve: 2.6.32-14 qemu-server: 1.1-18 pve-firmware: 1.0-7 libpve-storage-perl: 1.0-13 vncterm...

I installed proxmox 1.6 a few days a ago on a new server and have it running locally at 192.168.1.101 I am able to access the "master node" with no problem. I then created a new openvz container from a blueonyx template and put it at 192.168.1.111. It's set as venet If I change the...