Search results

Strange issue. I updated my SAN the other day which brought it offline for about 30 seconds during a power cycle of the controllers. 30 seconds is well within the configured timeouts in iscsi.conf. After the controllers came back online all of my VMs were fully functional but proxmox itself...

I have verified that I am running the latest bios. Thanks for the idea though. I should mention that this hardware has been running proxmox in production for a couple years now. I have been running 2.1 on the nodes being affected by this issue for some time and it has been rock solid.

My host machines are hard locking on VM start (and intermittently elsewhere) with a kernel:Kernel panic - not syncing: Fatal exception in interrupt message. The same nodes appear to function without issue on 2.6.32-11. All of the nodes that are exhibiting this behavior are dell blade servers...

I think you are correct that this is not a vm issue. Went back to basics and performed a test by balancing port 80 and it worked just fine. I am trying to load balance a pool of DNS servers and it is failing on port 53 for some reason. I have deployed dozens of LVS instances in the last couple...

I am trying to setup a KVM virtual machine to act as a load balancer. I have installed and configured IPVS and Piranha on a RHEL 6 guest but it fails to forward requests to the "real servers". Logs only say: nanny[1917]: READ to SERVER:PORT timed out. I assume that routing is the issue here but...

Re: Ran out of disk space during backup - now some /etc/qemu-server/XYZ.conf are empt I ran into this issue last night. Exact same problem. My NFS share was inactive (my fault, I brought it down for service), I ran a vzdump, and it ran out of space. Same error shown above. I have not tracked...

So I start work today by trying the standard update and upgrade process once more before I reload and the server updates to 5.0.5 without any issues. All of my nodes are now on 5.0.5. I am going to load a fourth server with the iso and see if I have the same issue. Maybe there is some...

Yeah I tried that too. Just weird. Tried again today and it pulled a couple updates from the pve server (qemu-server and pve-manager). But still at 5.0.3. Unless you can think of anything else to check and since this is a newly loaded server I am gonna just do a reinstall. That way maybe I...

sources.list are identical on all three nodes After aptitude install lsb-release (step included for posterity). Nodes 1 and 2 lsb_release -a returns: No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 5.0.4 (lenny) Release: 5.0.4 Codename: lenny...

Guys, I am installing PVE on a third node in my blade enclosure (identical hardware in all blades). I have it loaded and basic configuration done and have also upgraded to the 32 branch of the kernel. Same steps as the first 2 nodes. When I cat /etc/debian_version on nodes 1 and 2 it prints...