惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

C
Check Point Blog
Y
Y Combinator Blog
GbyAI
GbyAI
Microsoft Azure Blog
Microsoft Azure Blog
Martin Fowler
Martin Fowler
博客园_首页
大猫的无限游戏
大猫的无限游戏
美团技术团队
S
SegmentFault 最新的问题
T
The Blog of Author Tim Ferriss
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
MyScale Blog
MyScale Blog
小众软件
小众软件
Vercel News
Vercel News
阮一峰的网络日志
阮一峰的网络日志
N
Netflix TechBlog - Medium
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
量子位
博客园 - 【当耐特】
J
Java Code Geeks
F
Fortinet All Blogs
宝玉的分享
宝玉的分享
Stack Overflow Blog
Stack Overflow Blog
博客园 - 司徒正美

Proxmox Support Forum

[SOLVED] - Github Auth for Mirrors-Kernel Repo? [Automation] Mass migration tool for MS Win11/Server Proxmox GUI hang - not response is it possible to reject or quarantine spam based on conditions I set ? The PVENode task list in PVE9 is partially obscured due to the terminal font being too large. Kubernetes overlay networking breaks when upgrading from PVE 9.1 to PVE 9.2.3 Zentraler Speicher No space left on device Combine datastore and direct file archival to tape Kernel panic VFS: Unable to mount root fs on unknown-block (0,0) sobald ein 7.x Kernel verwendet wird. How to migrate disk of a VM from one ZFS to another Windows Server 2025 fails to boot after PVE 9.2 / Linux 7.0 Kernel upgrade Cannot Install Proxmox on T610 Poweredge with H700 PERC card sdn Config. gateway not reachable How to safely change domain/FQDN? Welche Filterquote erreicht ihr? NFS Share status unknown on 2 of 5 nodes Can't connect to PVE9 consoles [solved] Can't connect to PVE9 consoles [solved] [SOLVED] - Use secondary network for PVE commands Created cluster, one node storage gone BUG: proxmox mail gateway FROM = null bypass spam filtering Moving existing PBS from VMWare workstation to PVE cluster Does eBGP SDN fabric support external peering? Bug: PDM 1.1 not recognizing valid license status Proxmox GUI hang - not response PVE crashes unexpectedly Proxmox Backup Server 4.2 released! Advice ceph-osd crashes with kernel 6.17.2-1-pve on Dell system
About 100% error reporting due to pveproxy.service hooks
invalid@exam · 2026-05-31 · via Proxmox Support Forum

Hello, I performed clean installs using pve8 and pve9 respectively. However, on both pve9 ISOs, the newly installed machines experience errors every time they boot. The error message displayed by pvenode task list is:
│ UPID:pve:00000514:0000071C:6A1B0E8A:aptupdate::root@pam: │ aptupdate │ │ root@pam │ 2026-05-31 00:21:30 │ 2026-05-31 00:22:24 │ ERROR |

The root cause I found is that the line `ExecStartPost=-sh -c '[ ! -e /var/log/pveam.log ] && /usr/bin/pveupdate'` was added to pveproxy.service. I would like to understand why this line was added. Adding this line results in the system executing this command after booting and then consistently reporting an error. I didn't even have time to change the source or fill in the subscription information, and I'm already expected to receive this error?

Will this issue be fixed later, or will it remain a feature without modification?

The content of pveproxy.service in pve8 is:

[Unit]
Description=PVE API Proxy Server
ConditionPathExists=/usr/bin/pveproxy
Wants=pve-cluster.service
Wants=pvedaemon.service
Wants=ssh.service
Wants=pve-storage.target
After=pve-storage.target
After=pve-cluster.service
After=pvedaemon.service
After=ssh.service

[Service]
ExecStartPre=-/usr/bin/pvecm updatecerts --silent
ExecStart=/usr/bin/pveproxy start
ExecStop=/usr/bin/pveproxy stop
ExecReload=/usr/bin/pveproxy restart
PIDFile=/run/pveproxy/pveproxy.pid
Type=forking
Restart=on-failure

[Install]
WantedBy=multi-user.target
The content of pveproxy.service of pve9 is:
[Unit]
Description=PVE API Proxy Server
ConditionPathExists=/usr/bin/pveproxy
Wants=pve-cluster.service
Wants=pvedaemon.service
Wants=ssh.service
Wants=pve-storage.target
After=pve-storage.target
After=pve-cluster.service
After=pvedaemon.service
After=ssh.service

[Service]
ExecStartPre=-/usr/bin/pvecm updatecerts --silent
ExecStart=/usr/bin/pveproxy start
ExecStartPost=-sh -c '[ ! -e /var/log/pveam.log ] && /usr/bin/pveupdate'
ExecStop=/usr/bin/pveproxy stop
ExecReload=/usr/bin/pveproxy restart
PIDFile=/run/pveproxy/pveproxy.pid
Type=forking
Restart=on-failure

[Install]
WantedBy=multi-user.target

Last edited:

I believe that is supposed to update the available packages. PVE also does that on a periodic basis. What happens if you do "apt update" from the command line? What error do you get?

Adjust your repos - and I imagine that error will disappear on reboot.