Search results

@dcsapak - Hmm, are you saying that the proxy needs to do something special to pass a cookie on? Or could the cookie somehow be tied to a specific IP address or machine? (Is there any chance this cookie behaviour has changed in Proxmox 5.4 vs Proxmox 6.0)? What could I try to diagnose this...

Hi, I am attempting to setup LDAP authentication in Proxmox 6.0. Previously, on Proxmox 5.4 - I had to edit the /etc/pve/domains.cfg file, in order to add the new LDAP realm - as per the Proxmox documentation at https://pve.proxmox.com/wiki/User_Management#pveum_authentication_realms - e.g...

Instead of Cloudflare access, I also tried with Google IAP as well. That simply proxies the connections from a load-balancer sitting within GCP. When I do that, I get an error: Connection error 504: Gateway Timeout In the access.log file, I still see a HTTP 401: 34.83.155.61 - -...

Also - this is the cloudflared (HTTPS proxy) logs at the same time: {"CF-RAY":"5069cb9deae8cec8-LAX","level":"debug","msg":"POST https://localhost:8006/api2/extjs/access/ticket HTTP/1.1","time":"2019-08-15T01:28:29-07:00"} {"CF-RAY":"5069cb9deae8cec8-LAX","level":"debug","msg":"Request Headers...

I've setup a new Proxmox 6.0 cluster with three nodes. Version info is here: root@example-vm01:/var/log/pveproxy# pveversion pve-manager/6.0-5/f8a710d7 (running kernel: 5.0.18-1-pve) I'm using Cloudflared as a proxy to provide SSO in front of Proxmox. This was previously working on a separate...

Also - if I list the OSD hierarchy - they're all class "ssd". root@vwnode1:~# ceph osd crush tree --show-shadow ID CLASS WEIGHT TYPE NAME -2 ssd 4.01990 root default~ssd -4 ssd 1.33997 host vwnode1~ssd 0 ssd 0.10840 osd.0 1 ssd 0.10840 osd.1 2 ssd 0.10840...

Sorry, I'm a bit confused =( To be clear - you're saying that the only way to do this is to use device classes, right? I had tried creating OSDs on the first set of disks, then creating a Ceph Pool. Afterwards, I added OSDs on the other set of disks - but it seems to have simply integrated...

I can confirm this worked. To clarify, ceph auth get client.bootstrap-osd simply prints out the key information, you actually need to redirect it to the correct location (this got me at first, haha): root@vwnode1:~# ceph auth get client.bootstrap-osd > /var/lib/ceph/bootstrap-osd/ceph.keyring...

Hmm, weird - it still doesn't work for me. This is with the Ubuntu 19.04 Server ISO, on Proxmox 6.0 (Beta 1). I tried this ISO: ubuntu-19.04-live-server-amd64.iso (MD5 sum "9a659c92b961ef46f5c0fdc04b9269a6"). Note that I can use Alt + Left, or Alt + Right to switch to a different TTY - but...

I just appear to have hit this issue as well, trying to install a new VM under Proxmox 6.0 (beta 1) with Ubuntu 19.04. Is this a temporary fix, or is this the permanent workaround? It is an issue on Ubuntu's side, or on our side? Can the Default display be made with Ubuntu? UPDATE - Wait, I...

Right - so it will be a new boot of that VM. Curious - is there any method, or scenario under which it could be seamless migrated over, without a restart? Is such a thing possible under Proxmox (or elsewheere)?

Hi, Say I have a Proxmox cluster, with Ceph as the shared storage for VMs. Our VMs are mostly running Windows, and clients access them via RDP. To confirm - migrating a running VM from one node to another should be fairly quick, and the VM stays running for the whole period - so a RDP session...

We have three servers running a 3-node Proxmox/Ceph setup. Each has a single 2.5" SATA for Proxmox, and then a single M.2 NVNe drive and a single Intel Optane PCIe NVMe drive. I'd like to use both NVMe drives for *two* separate Ceph storage pools in Proxmox. (I.e. one composed of the three M.2...

Thank you! I will try this tonight as soon as I get home, I really want to get this working. So basically I just run that one command, and then the ceph-volume command should work as is? Do you think it might make sense to add an option in the Proxmox Ceph GUI to specify the number of OSDs per...

I have just installed Proxmox 6.0 beta on a 3-node cluster. I have setup the cluster, and also setup Ceph Managers/Monitors on each node. I’m now at the stage to create OSDs - I’m using Intel Optane drives, which benefit from multiple OSDs per drive. However, when I try to run the command to...

I had to do this again recently - in case anybody else reads this, using wipefs -a /dev/<devicename> also did the trick. There is more info about the command in this post: https://forum.proxmox.com/threads/recommended-way-of-creating-multiple-osds-per-nvme-disk.52252/

I just tried to install using ZFS on a Samsung M.2 NVMe drive - however, it would not boot into Proxmox VE after installation. It simply took me to a screen, that said “Reboot into firmware interface”. However, when I re-did the installation using ext4 - I was able to boot successfully Does...

Thank you for the detailed answer! I would never have discovered this otherwise. (Maybe I should document it somewhere?) I used the info you provided to search source code - it seems part of the logline is constructed in pve-common/src/PVE/Tools.pm. 1. One question - what is “dtype”? Are the...

Hi, I saw that Debian Buster is coming out in a few days! =) https://lists.debian.org/debian-devel-announce/2019/06/msg00003.html I read that the next version of Proxmox is 6.0 - and it will be based on Debian Buster, and have Ceph Luminous in it. Is there any idea of when Proxmox 6.0 is...

So I’m tailing /var/log/messages. When I start a VM, I see: Jul 3 23:06:17 syd1 pvedaemon[617005]: <root@pam> starting task UPID:syd1:000A4DBA:0112844F:5D1CA849:qmstart:108:root@pam: When I shutdown a VM: Jul 3 23:07:20 syd1 pvedaemon[617005]: <root@pam> starting task...