W whateveruser New Member Jul 6, 2025 11 2 3 Jul 25, 2025 #1 Can't find much about this error on Google Also weird, unless it's not something that proxmox does by itself, at the times I did not login at all on the server
Can't find much about this error on Google Also weird, unless it's not something that proxmox does by itself, at the times I did not login at all on the server
Impact Renowned Member Sep 12, 2022 910 361 73 Jul 25, 2025 #2 root is the user and pam is the realm. This is an automated task triggered by the pve-daily-update timer which calls pveupdate. As for the real problem, double click the task and show what it says. I'd also check apt update manually. Last edited: Jul 25, 2025 Reactions: Johannes S
root is the user and pam is the realm. This is an automated task triggered by the pve-daily-update timer which calls pveupdate. As for the real problem, double click the task and show what it says. I'd also check apt update manually.
bbgeek17 Distinguished Member Nov 20, 2020 5,793 2,012 228 Blockbridge www.blockbridge.com Jul 25, 2025 #3 Here is a bit more info : https://en.wikipedia.org/wiki/Linux_PAM In PVE context, PAM is the native OS user/authentication, i.e. one-to-one user relationship between logging into PVE and OS. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox Reactions: Johannes S
Here is a bit more info : https://en.wikipedia.org/wiki/Linux_PAM In PVE context, PAM is the native OS user/authentication, i.e. one-to-one user relationship between logging into PVE and OS. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox