Search results

I think I will do that. Still, reinstalling a node is kind of normal if you have lot of hosts in a proxmox cluster. It is a punishment to have to rename a host and change its IP just because the cluster refuses to re accept the host with a different SSH certificate. Is there a way to solve it...

Since my cluster is composed by 2 nodes, I could delete the cluster and recreate it from scratch in case of need. Will it work?

Hello I have a problem migrating VM between 2 servers using ProxMox VE 5.1 I have a cluster of 2 nodes. I want to migrate a VM from one node (called pve3) to the other (called pve5). I use the UI, right click, option migrate and I got this message: Task viewer: VM 109 - Migrate (pve3 --->...

I tried to re join and instance after following the guide, but I had to do an extra step:. the solution was to add to /etc/ssh/sshd_config the option MaxAuthTries 50 restart the ssh server, then try again and after the node was added, restore the previous value in MaxAuthTries and restart...

thanks @valeech

LXC 2.1 is not LTS though...

Hello @valeech, This message is a bit old, I found it useful. Could you please share a network config example? I would like to adapt this network configuration for my ceph cluster.

Hello, Do you have a date, or month, or quarter of ProxMox 5.1 release date? Just to organize my work. Regards Pablo

Perhaps it is related to this issue in SystemD? https://github.com/systemd/systemd/issues/3374#issuecomment-288882355

Nevermind. I declared the IPs static and moved on.

Hello I would like to have assigned the IP address of PVE Host by the DHCP server. This is the configuration of /etc/network/interfaces: auto lo iface lo inet loopback # The primary network interface allow-hotplug eno1 iface eno1 inet dhcp post-up echo 1 >...

https://www.greyhole.net/ ?

I understand is not part of the kernel. Please check: https://wiki.archlinux.org/index.php/ZFS In special: So we have "cuts" of kernel+ZFS4L in several flavors: ProxMox's cut, zfsonlinux.org's cut, etc and I do not feel comfortable using patches out of mainline. I try to avoid that kind of...

So if 2 containers try to write to the same file, if container A opens the file and locks it, container B open file operation will fail. Is that correct?

I did not know! Thanks for pointing to it. I created a container on ProxMox 5.0 and it created a .raw file as storage. I will try in my test server later to verify if I did something wrong that did not activate this feature.

Indeed. Because of this we are not using nodatacow. A postgresql subvolume on btrfs with cow and snapshots is what we adopted. For now.

There is not real alternative to btrfs. ZFS in linux is poorly integrated, competes successfully against server services by eating all memory resources and managing it, compared with btrfs, is cumberstone. The worst part is that there are no hopes of better integration. And all the time is that...

Hello @EuroDomenii, I got confused with the names. I am using LXC as described in ProxMox manual. I corrected the original answer. BTRFS is mounted with default options in the server. I am using these options to mount it in the container running the database instance: Mount Point (mp0)...

When Proxmox add support for BTRFS I will happily use it. This is the plan I have in mind: server SDD drives for postgres database running in a LXCLXD container under ProxMox control. The volume is external to the container (no a loop/qcow/etc volume) to improve performance and better recovery...

Excellent. Synology DSM 6.1 supports btrfs volumes and I want to use them to do hot backups using btrfs snapshots from btrfs volumes controlled by PVE5 to btrfs volumes on Synology NAS.