Search results

Check your kernel version. I had one node that failed to grab the kernel update and therefore couldn't mount zfs volumes with the new libs. Correct should be 4.13.4-1-pve #1 SMP PVE 4.13.4-25 or higher.

Perhaps an invalid authentication realm has been selected. The login dialog has User Name: Password: Realm: The third item needs to be "Linux Pam standard authentication" to use the same accounts that you use for ssh.

I had one node that failed to pull in the new kernel. Since I use zfs that caused a real problem. I think the same is happening here.

I found the original that I used. You might try reading this https://forum.proxmox.com/threads/api-debug-vagrant-proxmox-and-lxc-400-bad-request.26891/#post-135848 . You are right. There is no longer a log_request function.

I vaguely recall fighting a similar battle trying to get kvm vms setup with vagrant. I was not successful due to time constraints. I did run across a helpful tip to increase the verbosity of what was being logged on the forums. (sorry I can't find it nor do I remember who provided this) Here...

My only complaint is that "live migration" needs "with-local-disks" as an option. I have a "shared nothing" environment with zfs as the storage target. Thank you very much, I have already purchased the lifetime subscription.

Authentication messages is what I was referring to. Using an IP address lets out the possibility of dns issues, no ssl lets out tls issues, and port 389 being open lets out acl issues. Maybe create a test user to let out AD strangeness?

You will find basically the same info in messages, syslog, and kern.log. Perhaps it would be more meaningful to describe your setup in more detail. Are you using a dns name for the AD server or an IP address? Are you using ssl? The default port? A nmap scan from the proxmox server to your...

The Nuc is a fully functioning node member. I use that node to store backups and do testing. When I perform upgrades it goes first. If quorum is all you are after I would probably opt for the Odroid.

I am using an Intel NUC something like this https://www.amazon.com/Intel-BOXNUC5i3RYH-drive-option-barebone/dp/B01DG1SEES/ref=sr_1_3?ie=UTF8&qid=1501810718&sr=8-3&keywords=NUC+i3-5010U

You always have the option of using apt-cacher or spacewalk for managing your packages. Then you can inspect to your hearts content before deploying to production. Edited to change apt-cache to apt-cacher

What is the output of pct list ?

I have one that is a few years old (i3-5010U) that gave me no issues when upgrading. I use it as my backup server / cheap and deep storage. It also makes a great place to test automation and API stuff.

@guletz SSSD handles the authentication portion which is already handled by Proxmox built in functions. You need to also create the user name and give them a role or assign them to groups which have roles associated ie the Authorization portion.

GRE tunnels are implemented via openvswitch (ovs) there is another thread running on this forum that should be most informative to you https://forum.proxmox.com/threads/openvswitch-with-vlan-firewall-problems.35084/

Proxmox has an API and that has the functionality you are looking for. It shouldn't be a difficult task in your favorite scripting language. https://pve.proxmox.com/wiki/Proxmox_VE_API

local-lvm is indeed separate. Since I use zfs I wasn't aware of the lvm-thin containers being re-created on the other node. Setup the samba mount in fstab of node2 and it will be available on both machines.

As you said, the advantage is managing both machines from one interface. With minimal effort you can move virtual machines from one to the other. The gotchas are when you add the node to the cluster it must have no vms on it. Tearing the cluster down later is trivial and shouldn't concern you.

You don't need the third, it is just recommended. You can change the expected quorom votes to one via pvecm expected 1 You can pseudo live migrate with such a setup by setting up storage that is available via nfs on both machines and marking them shared. The trick is move the disk first and...

Here is a snippet that grabs mount point and percentage. Adjust as you need to. df -h | grep -v Used | awk '{ print $1" " $5 "\t" }'