Recent content by Smanux

I've added i915.fastboot=1 drm.edid_firmware=edid/1280x1024.bin to the GRUB_CMDLINE_LINUX variable in /etc/default/grub (modifying GRUB_CMDLINE_LINUX_DEFAULT had no effect on /boot/grub/grub.cfg) and it works! Thank you very much for the help.

I get: ~# proxmox-boot-tool status Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace.. E: /etc/kernel/proxmox-boot-uuids does not exist. and: ~# cat /etc/kernel/cmdline i915.fastboot=1 drm.edid_firmware=edid/1280x1024.bin

It's a dedicated server, with an access through IPMI. I've double checked the cmdline file, executed the update-initramfs/pve-efiboot-tool commands and rebooted twice, the EDID message is still there.

I'm facing the same issue on an OVH server with a Xeon E-2274G CPU, and unfortunately the edit2 workaround has no effect.

Thank you for the quick fix. I agree better support for unicast would be great, I struggled a bit to get the cluster to work.

It looks like this commit is responsible for the regression with my configuration: https://git.proxmox.com/?p=pve-access-control.git;a=commitdiff;h=e842fec5 Reverting the change fixes the issue. I guess Proxmox has its own parser for the Corosync configuration and it needs an update? Also...

Thank you for the hint. I'll give it a try the next time I reinstall the cluster. It's a bit odd that an element in the corosync configuration causes the authentication to fail though (well, maybe @pve but not @pam at least).

Here is the corosync configuration: logging { debug: on logfile: /var/log/corosync/corosync.log timestamp: on to_logfile: yes to_syslog: yes } nodelist { node { name: node1 nodeid: 3 quorum_votes: 1 ring0_addr: node1 } node { name: node2 nodeid: 2...

Here is the output with -v : * Trying 127.0.0.1... * TCP_NODELAY set * Connected to localhost (127.0.0.1) port 8006 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH * successfully set certificate verify...

I ran this command: curl -k -d "username=jdoe@pve&password=secret" https://localhost:8006/api2/json/access/ticket On a node with libpve-access-control 5.1-1 I get this: {"data":null} and on a node with libpve-access-control 5.0-8 I get: { "data": { "CSRFPreventionToken"...

The passwords only have ASCII characters ([0-9a-zA-Z] and punctuation characters).

I tried creating a new @pve account and I'm still unable to log in on the nodes with libpve-access-control 5.1-1.

My user.cfg file looks like this: user:jdoe@pve:1:0:John:Doe:jdoe@example.com::: user:root@pam:1:0:::admin@example.com::: acl:1:/:jdoe@pve:Administrator:

I confirm that downgrading libpve-access-control to 5.0-8 solves the issue (the .deb can be downloaded here: http://download.proxmox.com/debian/pve/dists/stretch/pve-no-subscription/binary-amd64/). Thanks a lot!

Hi, I have a 3 nodes cluster with Proxmox 5.2 that has been running fine for 9 months and for some reason I'm now unable to log into the manager. I keep getting the message "Login failed. Please try again" when using the root password and the PAM realm on any node. I'm sure the...