Search results

Our biggest machines are 32GB at the moment, so this should hold us for awhile. :) We have a 30 machine proxmox cluster now. The UI is still pretty usable, but we are getting close to it being too much for the browser (or the latency to gather all the info, I think).

We are trying to create a container with 32GB of memory, but we are getting and error which indicates that 8GB is the max. Is this a proxmox or openvz limitation? Also, is this a real limitation or can we adjust a file somewhere to get around it?

Should this be built into the normal startup routine then, or you are saying to run this manually if there is a problem after a power blip?

From our ops staff: ================================ Waiting for account to be activated. Answering the question (pass this on to the forum if you wish): to reproduce, shut down uncleanly. Killing power, an IPMI reset, or other forced host kill should do the trick. System will attemp...

The bug manifested itself during power failure for us. The machines weren't able to fsck when they came back up because LVM wasn't enabled before fsck was attempted. I think the problem is that checkroot happens before lvm is started, but I will point our ops person at this thread and see if...

I received this from one of our operations staff: Two of the grid servers rebooted due to a power outage and failed to come back up properly. The reason in both cases was a failed root filesystem fsck. On looking at the systems, root is an LVM volume, and in /etc/rcS.d/, chkroot.sh...

Just wondering what the is largest number of host machines that a proxmox cluster has reached so far? Just trying to get an idea of how it scales up and when the cross-node communication starts to become slower/impractical.

I was looking for a way to allow a subset of users to login using their own credentials and be granted "root" access. We use ldap/kerberos, so it would be useful to setup a kerberos principal for proxmox and have users access it via GSS-API via the browser.

Ah... I had just done an apt-get upgrade. I've gone through and upgraded the machines and the versions now show correct. Thanks.

Ok, so it's not easy to control access just to proxmox using ldap or such unless it's the common login setup? Do you have to login as "root" to proxmox consoles. What credentials are required by the login?

Hmm. I'm getting this: ian@grid02-dev:~$ pveversion -v pve-manager: 1.0-10 (pve-manager/1.0/3463) qemu-server: 1.0-5 pve-kernel: not correctly installed pve-kvm: not correctly installed pve-firmware: not correctly installed vncterm: 0.9-1 vzctl: 3.0.23-1dso1~etch0 vzdump: 1.1-1...

I have 4 machines together as a proxmox cluster. Machine one has vmids 101, 102, 104, 105, etc... (103 is skipped). Machine two has 103, 107, 108. When I go to create a new image, it is picking 103 as the next available VMID. Does it not look at the whole cluster? It seems to only be picking...

I didn't _want_ to re-init the keys, but they got changed by our puppet installation. It turns out that the /var/lib/vz directories were mode 700 so the webapp couldn't read the application templates. Not sure how that happened, but possibly during the upgrade to proxmox 1.0.

Is there an IRC channel for proxmox? I'm in #proxmox on freenode if anyone wants to get one together.

I managed to bork our proxmox setup. Many of the features are unavailable from the webapp and I can't see our appliance templates through the browser (though they are on the disk). How do I re-init the /root/.ssh/authorized_keys file for proxmox. I think that's what got messed up.

I think you need to do a "pveca -d ID" to the nodes before you readd them. I can't remember if you do that from the slaves or the master, but I think it's from the master.

My site is switching from a permissive /etc/pam.d/other (debian default) to a restrictive one. It seems that proxmox webapp login was using the "other" configuration. What is the name of the pam.d module I would need to create for proxmox auth to work in a restrictive-by-default setup?