permission denied invalid pve ticket 401.

gonzalo.garcia.ncp

New Member
Sep 5, 2023
21
1
3
Hi!

I have just configured a cluster, and when attempting to query the other node from the main node, which serves as the cluster, I encounter the error 'permission denied invalid pve ticket 401.'
1705595511392.png


Could you assist me?

Thanks,
Regards
 
Just use the search function, the topic is not new. Often it is simply due to a lack of time synchronization.
 
I'm having this problem too when trying to join additional nodes to a standalone cluster, using Datacenter -> Cluster -> Join Cluster.

The time is in sync.
The nodes can ping and SSH each other via both hostname and IP address.
I tried many times tidying up and rejoining the node, even reinstalled the new node a few times.

Code:
# ssh proxmox-big date; date
Mon Mar 18 08:32:30 AM GMT 2024
Mon Mar 18 08:32:30 AM GMT 2024

One error I can see on the joiner node is:

Code:
Mar 18 08:37:47 proxmox-sm pveproxy[5901]: /etc/pve/local/pve-ssl.pem: failed to use local certificate chain (cert_file or cert) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 2009.
Mar 18 08:37:47 proxmox-sm pveproxy[5902]: /etc/pve/local/pve-ssl.pem: failed to use local certificate chain (cert_file or cert) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 2009.

On the main cluster I'm getting this:

Code:
Mar 18 08:38:57 dell-5070 pmxcfs[26599]: [main] notice: resolved node name 'dell-5070' to '192.168.1.2' for default node IP address
Mar 18 08:38:57 dell-5070 pmxcfs[26599]: [main] notice: resolved node name 'dell-5070' to '192.168.1.2' for default node IP address
Mar 18 08:38:57 dell-5070 pmxcfs[26599]: [main] notice: unable to acquire pmxcfs lock - trying again
Mar 18 08:38:57 dell-5070 pmxcfs[26599]: [main] notice: unable to acquire pmxcfs lock - trying again
Mar 18 08:39:07 dell-5070 pmxcfs[26599]: [main] crit: unable to acquire pmxcfs lock: Resource temporarily unavailable
Mar 18 08:39:07 dell-5070 pmxcfs[26599]: [main] crit: unable to acquire pmxcfs lock: Resource temporarily unavailable
Mar 18 08:39:07 dell-5070 pmxcfs[26599]: [main] notice: exit proxmox configuration filesystem (-1)
Mar 18 08:39:07 dell-5070 pmxcfs[26599]: [main] notice: exit proxmox configuration filesystem (-1)
Mar 18 08:39:07 dell-5070 systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Mar 18 08:39:07 dell-5070 systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Mar 18 08:39:07 dell-5070 systemd[1]: Failed to start pve-cluster.service - The Proxmox VE cluster filesystem.
Mar 18 08:39:08 dell-5070 systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 107.
Mar 18 08:39:08 dell-5070 systemd[1]: Stopped pve-cluster.service - The Proxmox VE cluster filesystem.
Mar 18 08:39:08 dell-5070 systemd[1]: Starting pve-cluster.service - The Proxmox VE cluster filesystem...

I ran out of ideas, any help would be appreciated.
 
I am having a similar issue, with a 3 node cluster. Everything was fine for months, and now I’m unable to get all nodes together.

3 nodes we’ll call 11, 12, 13:
- 11 & 13 can cluster
- 12 & 13 can cluster
- 11 & 12 fail to cluster

When joining 11 & 12, I get:
- an invalid pve ticket
- lose web gui access
- hangs on `pvecm updatecerts [-f]` via ssh

This happens on a brand new install of proxmox on all 3 nodes.
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!