Recent content by FORCED-INDUCTN

Hello, I am working on a free WHMCS module for Proxmox, that (if I can pull it off) I want to release to the public. I have messed around and hacked up PHP scripts for years but never created or taken on a project like this. So please forgive me if my question are too noobish. I have been...

Hello, I have a 240GB RAID 10 array and a 60GB SSD for caching. When I install Proxmox to the RAID10 array with the SSD in the server, the boot sector gets written to the SSD because it is /dev/sda. The problem with this is the SSD is not redundant, if I lose the SSD the server will not be...

No, it didn't work before both nodes were reboot, and it still doesn't.

[ironworks~] pveversion -v pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1) running kernel: 2.6.32-18-pve proxmox-ve-2.6.32: 2.3-88 pve-kernel-2.6.32-11-pve: 2.6.32-66 pve-kernel-2.6.32-14-pve: 2.6.32-74 pve-kernel-2.6.32-18-pve: 2.6.32-88 pve-kernel-2.6.32-17-pve: 2.6.32-83 lvm2: 2.02.95-1pve2...

Thanks for the response dietmar. I appologize, I did introduce that typo when creating this post (I have now fixed the typo). I ran ccs_config_validate -l /etc/pve/cluster.conf.new and it appears to have crashed?! [ironworks/etc/pve] ccs_config_validate -l /etc/pve/cluster.conf.new *** glibc...

Hello. I'm trying to make some VMs HA managed, but when I hit "activate" in the "HA" tab I get this error message: config validation failed: /usr/sbin/ccs_config_validate: line 186: 674512 Aborted ccs_config_dump > $tempfile (500) I have run into problems like this before, and tried to run...

I was able to fix my cluster, here are the steps I took: -Shut down all VMs on all nodes -vgchange -c n on all VGs -Killed clvmd process -returned locking type to "1" in /etc/lvm/lvm.conf -backed up virtual machines -reboot -Everything was happy :) Thanks guys, --Will

I thought changing clustered LVM to stand alone LVM sounded risky. I have been considering something similar to what you have suggested. The problem is that DRBD is in split brain :( Also with out the ability to migrate VMs or back them up I am somewhat stuck. Luckily most of the LVs exist on...

Ahh OK, so is it safe to change /etc/hosts just like normal? Can I also change /etc/pve/.members if I have too? --Will

I think the safest approach I have right now is to migrate all VMs to one node. Then convert the clustered LVM back to stand a lone LVM. Then move the VMs back. Problem is I can't migrate VMs now :( When I try to migrate a VM from either node it uses the wrong IP address. When I run a pvecm...

Cool, so can I make this change with everything "online?" I assume that the locking only comes into play when something has to deal directly with LVM. So if the proxmox tools (pvesm looks cool, didn't know that was there!) are the only ones that lock correctly, should I not use the LVM tools...

Great! So right now I have "locking_type = 3" set in lvm.conf, for what I believe is LVM's built in locking? What should I change that too? These are the options in LVM.conf: Type of locking to use. Defaults to local file-based locking (1). Turn locking off by setting to 0 (dangerous: risks...

Thank you for your quick reply! Well that explains why cLVM is so "weird" and not on by default in proxmox....duh. I had a lot of problems with DRBD and locking with LVM so lots of googling had lead me to that setting. 1. I have no problem getting rid of cLVM 2/3. These are production servers...

Hello, I tried to make a backup of a virtual machine and got this: INFO: starting new backup job: vzdump 19217 --remove 0 --mode snapshot --storage vmbackup.fortress --node ironworks INFO: Starting Backup of VM 19217 (qemu) INFO: status = running INFO: backup mode: snapshot INFO: ionice...