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.
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 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"...
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...
Hi,
I'd like to put an executable file in /etc/pve to share it easily with the other nodes of the cluster (An init.d script used as a HA resource), but I can't chmod +x :
chmod: changing permissions of `/etc/pve/myscript': Function not implemented
That's frustrating because the OpenVZ action...
Thank you for the reply Dietmar.
I figured out why I don't see the files on the other nodes. /etc/pve/openvz is a symlink to /etc/pve/nodes/<nodename>/openvz. I created the script on the node1 and I can see them on the node2 in /etc/pve/nodes/node1/openvz, but since /etc/pve/openvz on node2...
Hi,
I've added global actions scripts (/etc/vz/conf/vps.mount and /etc/vz/conf/vps.umount) on one of the nodes of my cluster but they don't seem to be replicated on the other nodes. Since /etc/vz/conf is symlinked to /etc/pve/openvz I thought this would be automatically replicated.
On the...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.