[SOLVED] Service pvedaemon fails > I cannot access to the GUI on password error

[stsinc]

Hi,
I am keeping my 5 nodes updated at the latest version.
Suddenly, without anything having changed whatsoever, I cannot access the GUI of my usual Proxmox entrypoint on a "Login failed" error. Yet I am absolutely positive about the password (which I input all the time and which is saved into a password database).

As I am still able to access the the computer via SSH, I did a `systemctl status pvedaemon pvestatd pveproxy spiceproxy` and found that all services worked fine.

How can I help you understand what has so suddenly gone wrong?

Best,
Stephen

 

[stsinc]

However, when I access another node (not the one I generally us to connect to the GUI) I have several issues relating to authorizations:

pvedaemon.service - PVE API Daemon
     Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2022-01-05 17:59:16 EST; 2h 59min ago
    Process: 987 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS)
   Main PID: 1018 (pvedaemon)
      Tasks: 4 (limit: 28642)
     Memory: 150.1M
        CPU: 1.547s
     CGroup: /system.slice/pvedaemon.service
             ├─1018 pvedaemon
             ├─1019 pvedaemon worker
             ├─1020 pvedaemon worker
             └─1021 pvedaemon worker

Jan 05 17:59:16 i75 pvedaemon[1018]: starting 3 worker(s)
Jan 05 17:59:16 i75 pvedaemon[1018]: worker 1019 started
Jan 05 17:59:16 i75 pvedaemon[1018]: worker 1020 started
Jan 05 17:59:16 i75 pvedaemon[1018]: worker 1021 started
Jan 05 17:59:16 i75 systemd[1]: Started PVE API Daemon.
Jan 05 18:11:30 i75 pvedaemon[1020]: authentication failure; rhost=::ffff:192.168.1.5 user=root@pam msg=cfs-lock 'file-priv_tfa_cfg' error: got lock request timeout
Jan 05 18:12:38 i75 IPCC.xs[1019]: pam_unix(proxmox-ve-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=  user=root
Jan 05 18:12:38 i75 IPCC.xs[1021]: pam_unix(proxmox-ve-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=  user=root
Jan 05 18:12:41 i75 pvedaemon[1019]: authentication failure; rhost=::ffff:192.168.1.5 user=root@pam msg=Authentication failure
Jan 05 18:12:41 i75 pvedaemon[1021]: authentication failure; rhost=::ffff:192.168.1.5 user=root@pam msg=Authentication failure

● pvestatd.service - PVE Status Daemon
     Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2022-01-05 17:59:16 EST; 2h 59min ago
    Process: 971 ExecStart=/usr/bin/pvestatd start (code=exited, status=0/SUCCESS)
   Main PID: 992 (pvestatd)
      Tasks: 1 (limit: 28642)
     Memory: 122.9M
        CPU: 1min 17.272s
     CGroup: /system.slice/pvestatd.service
             └─992 pvestatd

Jan 05 19:56:34 i75 pvestatd[992]: status update time (120.400 seconds)
Jan 05 19:58:34 i75 pvestatd[992]: status update time (120.407 seconds)
Jan 05 20:00:35 i75 pvestatd[992]: status update time (120.413 seconds)
Jan 05 20:02:35 i75 pvestatd[992]: status update time (120.413 seconds)
Jan 05 20:04:35 i75 pvestatd[992]: status update time (120.414 seconds)
Jan 05 20:06:36 i75 pvestatd[992]: status update time (120.445 seconds)
Jan 05 20:08:21 i75 pvestatd[992]: status update time (104.806 seconds)
Jan 05 20:50:12 i75 pvestatd[992]: authkey rotation error: cfs-lock 'authkey' error: got lock request timeout
Jan 05 20:50:12 i75 pvestatd[992]: status update time (361.097 seconds)
Jan 05 20:50:14 i75 pvestatd[992]: auth key new enough, skipping rotation

● pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2022-01-05 17:59:17 EST; 2h 59min ago
    Process: 1023 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
    Process: 1025 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
   Main PID: 1027 (pveproxy)
      Tasks: 4 (limit: 28642)
     Memory: 187.7M
        CPU: 2.304s
     CGroup: /system.slice/pveproxy.service
             ├─1027 pveproxy
             ├─1028 pveproxy worker
             ├─1029 pveproxy worker
             └─1030 pveproxy worker

Jan 05 17:59:16 i75 systemd[1]: Starting PVE API Proxy Server...
Jan 05 17:59:17 i75 pveproxy[1027]: starting server
Jan 05 17:59:17 i75 pveproxy[1027]: starting 3 worker(s)
Jan 05 17:59:17 i75 pveproxy[1027]: worker 1028 started
Jan 05 17:59:17 i75 pveproxy[1027]: worker 1029 started
Jan 05 17:59:17 i75 pveproxy[1027]: worker 1030 started
Jan 05 17:59:17 i75 systemd[1]: Started PVE API Proxy Server.
Jan 05 18:12:08 i75 pveproxy[1030]: proxy detected vanished client connection

 

[stsinc]

And actually this error is present on all other nodes:

authkey rotation error: cfs-lock 'authkey' error: got lock request timeout

 

[stsinc]

Eventually, things came into order -- sort of:

1. I shut down ALL devices on the network
2. I turned them on very progressively, watching on an external Android app if they were added to Proxmox's network
3. And eventually they were all there and the password worked again.

BUT, now that I can access the GUI and see all containers and VMs, none of them is allowing me to access the console - here is the error I get from the GUI:

TASK ERROR: command '/usr/bin/termproxy 5900 --path /vms/100 --perm VM.Console -- /usr/bin/dtach -A /var/run/dtach/vzctlconsole100 -r winch -z lxc-console -n 100 -e -1' failed: exit code 1

 

[stsinc]

The reason was external to Proxmox: I switched to full SSL and the console does notg seem to behave well with added security.

 

[PedroGraca]

I'm having the same problem, I can login via ssh but I can't access the GUI, can someone help me please?

 

[PedroGraca]

It started from a locked VM on GUI, I've tried the qm unlock 104 but then received an error from a temp file, on the next day I didn't have access to GUI, it shows login error...