Search results

I don't use LXC containers. I think that is the point. From here : https://forum.proxmox.com/threads/how-is-swap-handled-by-lxc.26756/ I understand that SWAP in LXC use SWAP on host. Thus, it can be a swapiness problem, at LXC level. See ...

Thomas@phase : I had the idea of VPN but I fear instability problems. Did you mesh you nodes, or made 6 links in order to not have a central VPN node that is SPOF ? Here at Liberasys I have no cluster for the moment. But I have some bridges behind a Mikrotik VM, it works very well too :-)

No problem with your architecture. Proxmox NFS mounts done with GUI will be under /mnt/pve (but you don't actually care) Idea : mkdir /var/lib/vz/nfs_share_srv1 export /var/lib/vz/nfs_share_srv1 mount it within PVE GUI on srv2 Do the same for server #2 You will have remote space available to do...

With one pfSense per node, they can each have a public IP on one bridge and one private in one other. With your server #2 and #3 switched with the #1 server, you will be able to do what you want. The question after this is how do you obtain public IPs and how are they routed to you servers...

I have no other idea. Maybe try to trace which programs swaps ? One howto found here : https://www.cyberciti.biz/faq/linux-which-process-is-using-swap/

Yes You can use the same principle on every node (one pfSense per node), or use OVS (although I don't know if it will work in your environment). But simpler : create a 4th LAN for private IP VM networks (you could use vlan tagging on this one in order to create several security zones behind...

Put swapiness=1 and reboot swapiness=0 has lead to OOM kills from what I have seen on the web Maybe you have an other side effect ? What disk mode do you use on your VMs (ex : default (no cache)) ?

Zsync will not allow you to migrate between hosts. One solution can be to divide your disk space by 2 on each server. Then install a NFS server that point to the 1st and 2nd space on each server. Then do crossed backups between servers (use space 2 for backups). For live migration, you will have...

vi /etc/aliases newaliases

I cannot precisely help you (I do not use OVS), but enabling ARP proxy on your gateway can help. Be aware of security problems it can generate. For information, I have used shorewall on PVE host with manual ARP proxy configuration. Now I use a mikrotik VM with ARP proxy.

I do not have the answer. For SSH, try to remove SSH server keys and reboot node (works almost in any case/distro). For debian based distro, do : rm /etc/ssh/ssh_host_* dpkg-reconfigure openssh-server The host keys will be regenerated. Anyway, a clone is a byte to byte copy. Do not forget to...

FS loop over an other one always produces IO amplification. Maybe try noatime and nodiratime on the host (if /var/lib/vz is a separated FS) and VM guests (if your VM daemons does not require atime and diratime). Furthermore, try to alginate FS cluster sizes between VM (FS) and host (VM +...

Why would you disarm fencing ? You are supposed to migrate VMs before rebooting a node. For HW watchdogs, be aware that a server has several ones nowadays. Spend some time to master your hardware and configurations of it. For example, here are my notes for a R730, with proxmox 4.1 : Watchdog...

look in /var/lib/vz/template/

Suggestion : wait for the PVE v5 : - migrate from local storage VMs (qemu) - ZFS sync interface And one other : do never use more than 75% of your pool

I don't have this problem. Look at swapiness kernel configuration, and try to play with it ?

Just a remark : if you use your 1st server as switch, then you should not use HA on the cluster (if 1st server is down, all the cluster will go down). And an other : if the pfSense is not in HA, then if the pfSense VM is down, you will not be able to assignate IPs to your servers. In brief : buy...

I may be mistaken, but I always saw errors on SATA buses with atom based "servers" I build at home. I think that unrecoverable errors comes from that. After all, this is a high speed bus, subject to perturbation, and with consumer grade hardware :-) Concerning the endurance, I don't know, this...

I spent several days at my precedent job in order to understand the SSD technology and in order to choose the right disk for the right usage. The disk I use is not a professional one, but there is a good warranty :-) Disk is installed with Proxmox since around 20 days.

Dan : read the manual about minimum node number for HA (cluster concept : quorum), and read about watchdog fencing.