Search results

Hi, Here is my current configuration: 2 x 480Go SSD - RAID 1 /dev/md1 (20Go) mounted on "/" for debian/proxmox install /dev/md5 (460Go) -> /dev/mapper/pve-data (LVM) mounted on /var/lib/vz for containers 2 x 4To HDD - RAID 1 /dev/md2 (4To) -> /dev/mapper/vg1-dataslow (LVM) mounted on...

All my nodes are up and running but maybe that a configuration problem is avoiding the cluster to be "ok". I read here that it's way easier when nodes are in the same subnet. My nodes are OVH dedicated servers and have public IPs on different subnets. Maybe that I have to deal with OVH VLAN...

Thank you dietmar, your replies are always relevent and very quick! As I am a beginner with proxmox (managing a cluster created by another person which is no longer with me), I don't know anythink about the Proxmox cluster quorum so I'll read some docs about it.

Hi, I would like to change some settings in some /etc/pve/* files on my physical Proxmox hosts but I'm not able to create or modify files in this directory : # touch /etc/pve/test.file touch: impossible de faire un touch « /etc/pve/test.file »: Périphérique ou ressource occupé # mount | grep...

Thank you very much tom and dietmar! I replaced the last byte of my gateway address with .254 and it worked :)

Hi, I recently installed Proxmox 4 on a dedicated OVH server and then created a container like this: pct create 200 /var/lib/vz/template/cache/debian-8.0-standard_8.4-1_amd64.tar.gz -rootfs 25 -hostname myhost.mydomain.com -memory 1024 -nameserver 213.186.33.99 -net0...

15min response, this is called super rapid power :) Thank you t.lamprecht, that's the info I was missing.

Hi, I created a new virtual machine (myvm1.mydomain.com) on a new physical proxmox 4 host (myhost.mydomain.com). As I have a wildcard certificate for my domain (*.mydomain.com), I replaced /etc/pve/local/pve-ssl.pem with my wildcard certificate. I then tried to start a VM and got this error...

Hi, I installed a new proxmox 4 physical host and tried to deploy the same /etc/pve/storage Unfortunately, I have the exact same problem on this host. The local storage is shown in "pvesm status" and nfs storages are just absent... What further test could I do? Thanks

Nothing special related to pve or storage concerns...

I edited my previous posts with adding "code" tags (and re-ran commands to copy/paste whitespaces). Each line is preceeded by 8 spaces except the top block line of each block.

Here is the result: # pvesh get /storage 200 OK [ { "content" : "iso,rootdir,vztmpl,images", "digest" : "21548bc295f8e3bbd14da50ebb26a93705725b64", "maxfiles" : 0, "path" : "/var/lib/vz", "priority" : 0, "storage" : "local", "type" : "dir" } ] Thanks for your help

Yes, the two files have exactly the same content (same md5sum). The Proxmox 4 server which doesn't want to mount the nfs storages is not in a cluster. I don't know if it could be relevent to say that but I know that a collegue tried to créate a cluster with this host as first node and didn't...

Hi dietmar, thanks for the quick reply. Unfortunately, only the local storage is listed: # pvesm status local dir 1 436037240 46937656 366943504 11.84%

Hi everyone, I am running several Proxmox 2 and 3 hosts and a Proxmox 4 host. All of them declare a local storage and 2 nfs storages in /etc/pve/storage.cfg like this : # cat /etc/pve/storage.cfg nfs: share-online path /mnt/pve/share-online server server1.domain.com export /srv/vzshare...

Hi everyone, In Proxmox 3 (and before), detecting that we were in a Proxmox host was easy by issuing commands like "ls /proc/vz/version" (which only reside in hosts and not in guests). Is there a simple way like this to know if we are on a Proxmox 4 (LXC) host without using some tools like...