Grey Question Mark, after CIFS share offline

Still, another problem:
Allthough I am able to access the terminal via the PVE UI of other nodes, I am not able to login directly to node 3 and node 4.
1728572444893.png

but both nodes are shown green now in the ui of node 1 and node 2.
But also the system tab can't be shown (communication failure (0) )

Maybe another service needs to be restarted?
 
here a part of some more logs.
it is repeated in that way...
Code:
Oct 11 10:00:57 p-virt-sw-3 pveproxy[1821979]: proxy detected vanished client connection
Oct 11 10:00:59 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:00:59 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:01:04 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:01:04 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:01:09 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:01:09 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:01:14 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:01:14 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:01:19 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:01:19 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:01:24 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:01:24 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:01:29 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:01:29 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:01:31 p-virt-sw-3 pmxcfs[3294]: [status] notice: received log
Oct 11 10:01:34 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:01:34 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:01:39 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:01:39 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:01:44 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:01:44 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:01:49 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:01:49 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:01:54 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:01:54 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:01:59 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:01:59 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:02:01 p-virt-sw-3 pveproxy[1816718]: proxy detected vanished client connection
Oct 11 10:02:04 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:02:04 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:02:09 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:02:09 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:02:14 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:02:14 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:02:19 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:02:19 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:02:24 p-virt-sw-3 pmxcfs[3294]: [status] notice: received log
Oct 11 10:02:24 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:02:24 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:02:29 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:02:29 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:02:31 p-virt-sw-3 pveproxy[1821979]: proxy detected vanished client connection
Oct 11 10:02:34 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:02:34 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:02:39 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:02:39 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:02:44 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:02:44 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:02:49 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:02:49 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:02:54 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:02:54 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:02:59 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:02:59 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:03:04 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:03:04 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:03:09 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:03:09 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:03:14 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:03:14 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:03:19 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:03:19 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:03:24 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:03:24 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:03:29 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:03:29 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:03:34 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:03:34 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:03:36 p-virt-sw-3 pveproxy[1813610]: proxy detected vanished client connection
Oct 11 10:03:39 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:03:39 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:03:44 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:03:44 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:03:49 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:03:49 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:03:54 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:03:54 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:03:59 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:03:59 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:04:04 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:04:04 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:04:06 p-virt-sw-3 pveproxy[1816718]: proxy detected vanished client connection
Oct 11 10:04:09 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:04:09 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:04:14 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:04:14 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:04:19 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:04:19 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:04:24 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:04:24 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:04:29 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:04:29 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:04:34 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:04:34 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:04:39 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:04:39 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:04:44 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:04:44 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:04:49 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:04:49 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:04:54 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:04:54 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:04:59 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:04:59 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:05:04 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:05:04 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:05:09 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:05:09 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:05:10 p-virt-sw-3 pveproxy[1816718]: proxy detected vanished client connection
Oct 11 10:05:14 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:05:14 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:05:19 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:05:19 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349
Oct 11 10:05:24 p-virt-sw-3 qmeventd[2953]: error parsing vmid for 23349: no matching qemu.slice cgroup entry
Oct 11 10:05:24 p-virt-sw-3 qmeventd[2953]: could not get vmid from pid 23349

[/QUOTE]
 
to sum it up:
on 2 of 4 nodes the following problems appear:
1.) direct login on the web ui fails with an error: "Login failed. Please try again"
2.) cluster remote access works and it all green. Selecting one VM only configuration data shows up but the live data (CPU load, remote console, ...) ist just loading endlessly.
 
Hi,

Thank you for sharing more syslog!

Have you tried to restart pveproxy service? `systemctl restart pveproxy`

Have you tried to log in from a different/private browser as well? If the private login works you may have to clean the cache. If not, try to update the certificate using `pvecm updatecerts --force` command.
 

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!