Search results

Have a couple of questions. We have been running proxmox v1.9 - v2.2 for ages with NO issues. We have a small server internally that houses 2 Windows 2008 R2 servers and 2 Linux containers. Has ran forever no issues. Yesterday, I started creating a Windows 2012 server machine and since that...

If I go into the web interface from any machine in the cluster I can start, stop, restart,... any of the nodes no matter which cluster node that they are contained on. However, from the command line using commands like vzlist or qm only seem to operate on the cluster node and its containers...

Well that is an excellent reason for it not working. Thanks for the quick response!

We now have some containers running on one of the two nodes in the cluster after the latest updates this morning. We decided that we should try migration as this is one of the major features we are looking for. Output from the web interface yields: Starting online migration of CT 100 to...

The updates pushed out this morning have resolved the issue reported. Time to move forward... Thanks!

Unfortuntately this only leads to the next error. While I was able to create the LVM storage and it shows up under the web interface the logs now are loaded with: dlm: closing connection to node 2 INFO: task clvmd:2196 blocked for more than 120 seconds. "echo 0 >...

Rebooting both nodes in the cluster apparrently cleared up the issues. Was able to create LVM groups on both. Still display size bug exists and it should not be necessary of course to reboot to add storage.

Created a 50GB LUN (which was reported at 50MB so I think you are always off by one "unit") and had the same results. Sat at Please Wait for about 30 seconds and then returned with nothing getting created.

So after my NFS issues behind me (http://forum.proxmox.com/threads/7563-ISO-and-Templates) I decided to move on and setup some image /container storage using our iSCSI OpenFiler storage. I created the iSCSI storage device with no issues, other than the fact that we see the following messages...

Sure, now you tell me :) Anyhow, glad it is resolved and can move forward. THANKS ALL! Have a great Thanksgiving if applicable.

Re: ISO and Templates - SOLVED! Ok, kept digging around as we needed to get past this step. I found the command pvesm nfsscan <server> and ran that which resulted in the error: clnt_create: RPC: Program not registered So, Google being my friend started some searching and came across some...

Can we split this thread somehow? The gcmartin posts while similar do not seem to be the same issue. I will assume the comment: your nfs storage is not active, that seems to be the problem. do you see the ISO on the content tab? was directed at me. NFS is active: # df Filesystem...

Yes, correct. These were uploaded using the web interface which actually worked. Just not able to use them.

# pvesm list storageRep0 mount.nfs: /mnt/pve/storageRep0 is busy or already mounted command '/bin/mount -t nfs 172.16.224.1:/mnt/volgroup0/storagerep/images/ /mnt/pve/storageRep0' failed: exit code 32

Ok, here is the directory structure from an SSH connection showing that we are even running with relaxed file permissions to try and get this working: However, the file display from the web interface shows nothing and does not know about the NFS size: And below are the container and VM...

Nope, no misunderstanding, have production Proxmox servers using both and understand the differences. I have both ISO and gz template files uploaded and in the correct spots, per discussion. The problem is VM (KVM) sees none of the ISO files and containers (OpenVZ) sees none of the template...

Not here! Here is the information, thanks! # pveversion -v pve-manager: 2.0-10 (pve-manager/2.0/7a10f3e6) running kernel: 2.6.32-6-pve proxmox-ve-2.6.32: 2.0-52 pve-kernel-2.6.32-6-pve: 2.6.32-52 lvm2: 2.02.86-1pve1 clvm: 2.02.86-1pve1 corosync-pve: 1.4.1-1 openais-pve: 1.1.4-1 libqb: 0.6.0-1...

Yes, I figured that out after that is where the uploads placed them. HOWEVER, then when we go to either create a container of VM and select that storage location the list has NO items listed even though we see them in the directories. As mentioned we even tried making the files world (other)...

Seeing the updates to storage for containers and such I created a NFS share to hold ISO and Template files that I figured could be used by all of the nodes on the cluster. However, I have not figured out where to actually place files so that they are recognized. The systems do all have the...

How about adding an IP option so that people with multiple NICs can decide which address to setup the cluster on? Also, now is there any easy way to back out of the cluster setup I have on the incorrect IP address so that I can then update the /etc/hosts file and recreate the cluster. Thanks!