Search results

Hello, I would like to know if there is simple way to stick to 4.2 release ? I need to upgrade one of my cluster node and would like to avoid having one of the nodes in 4.3 and all others in 4.2 Furthermore, I never upgrade my server just after a new release. Thanks for your answer.

No, It is not possible that I am checking the wrong file.

I have written a 12G file using dd and /dev/urandom and the size of my qcow2 image hasn't move a bit ?! I am really perplex : where are the data stored ? what if my data get bigger than my storage ? How can a virtualized file system be bigger than the image which is supposed to contain...

So all in all I should be safe with my Qcow2 being 10G and my KVM thinking It is 67G ? I am testing It with /dev/urandom Will also read the pointer !

dd if=/dev/zero of=10G2 bs=1M count=10000 Yes zeroes !

Hello, I am trying to figure out how things are working when related to disk size and disk image and real disk size. I have an NFS shared storage with 10T of disk space. This storage is a FreeNAS ZFS storage and is available on all nodes of my cluster (shared using NFS). The size of the...

Ok - I can confirm this : We have upgrade a second node to latest stable : 4.2-18/158720b9 And we were able to migrate our nodes ! Definitively a version issue ! Thx !!

Hello, I am jumping on this thread because we have the exact same problem. We have a shared NFS storage and a three node cluster. Two nodes (production) are running version : 4.2-15/6669ad2c The last node (where the server is deployed is running latest : 4.2-18/158720b9 I am trying to...

Hello, We have setup a three nodes cluster that's up and running. All nodes are using local ZFS storage (a bit annoying because PVE expects datasets to have the exact same name - which is not the case in our install). We also have 2 NFS servers (based on FreeNAS) : 1 used as a ZFS backup...

I have yet found another reply which is the good and right answer : Filesystem and mount points shall have the same naming ! So this won't work : root@proxmonster:/md/data# zfs list NAME USED AVAIL REFER MOUNTPOINT monster 384M 3.17T 192K /md monster/data...

I think I have more or less found the error. If I create my lxc container by hand, I can create It ok with this command (where I have specified "volume=") : pct create 117 /md/templates/template/cache/centos-6-default_20160205_amd64.tar.xz \ -description LXC -rootfs volume=/md/data,size=8G...

System has been fully re-installed. This solved the issue… quite annoying though to be forced to re-install system to solve such issues.

I have the same error. Fresh install setup in cluster (2 nodes for the time being). I have deleted the zpool completely and re-created It… no luck still the same error (looks like a bug). root@proxmonster:/home/gregober# pvesm status local dir 1 48712192 1013120...

root@proxmaster:/etc/pve/priv# pvecm expect 1 root@proxmaster:/etc/pve/priv# pvecm add 192.168.210.10 -force root@192.168.210.10's password: unable to copy ssh ID: bash: line 2: .ssh/authorized_keys: No such file or directory No luck with pvecm add I still can't seem to copy anything… sort of...

This will certainly help, but my problem is also clearly related to this bug : https://forum.proxmox.com/threads/pve-ssl-key-not-installed-with-new-installation.27845/ /etc/pve/priv is not created by default on my second cluster node… This is most probably the reason why we have these errors...

No I can't do that (= from proxmaster to proxmonster). The opposite is working though (= from proxmonster to proxmaster). root@proxmonster:/home/gregober# pvecm add 192.168.210.11 -force can't create shared ssh key database '/etc/pve/priv/authorized_keys' cluster not ready - no quorum? unable...

On the master node .members looks like this : { "nodename": "proxmaster", "version": 4, "cluster": { "name": "pmox-osnet", "version": 2, "nodes": 2, "quorate": 0 }, "nodelist": { "proxmonster": { "id": 2, "online": 0}, "proxmaster": { "id": 1, "online": 1, "ip": "192.168.210.11"} } }...

I have already made a backup of this section on the main node. I will do It on the third node. I don't have the second node up and running. Ok - will try to do that - but I would rather try to have cluster working. Do you think It is safe to move on with this cluster config knowing that we...

Hello, I have couple of questions related to the PVE Cluster. First question : I am trying to setup a Proxmox VE cluster. I have three nodes, but two of them already have been configured and are now in production. I would like to know if It is safe to try to configure the cluster in...

It is not a qemu server but an LXC container : root@proxmini:/home/gregober# cat /etc/pve/lxc/110.conf #server%3A in production #service%3A mail server and antispam # #eth0 %3A 2xx.xx1.1x2.9 #eth1 %3A 192.168.210.26 (newmail.osnet.lan) #eth2 %3A 192.168.220.26 arch: amd64...