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

推荐订阅源

H
Hackread – Cybersecurity News, Data Breaches, AI and More
U
Unit 42
Vercel News
Vercel News
Martin Fowler
Martin Fowler
云风的 BLOG
云风的 BLOG
爱范儿
爱范儿
MongoDB | Blog
MongoDB | Blog
J
Java Code Geeks
F
Fortinet All Blogs
MyScale Blog
MyScale Blog
C
Check Point Blog
N
Netflix TechBlog - Medium
Microsoft Azure Blog
Microsoft Azure Blog
aimingoo的专栏
aimingoo的专栏
博客园_首页
WordPress大学
WordPress大学
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
IT之家
IT之家
Last Week in AI
Last Week in AI
罗磊的独立博客
大猫的无限游戏
大猫的无限游戏
Jina AI
Jina AI
V
Visual Studio 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. About 100% error reporting due to pveproxy.service hooks 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
LCX not starting after upgrading PVe from 9.1.x to 9.2.2 ...
invalid@exam · 2026-06-12 · via Proxmox Support Forum

Have you checked dmesg as it says?

Sorry I forgot to post this part. I am not sure what part is of interest. I think this line might show the error?

Code:

[Jun12 13:24] audit: type=1400 audit(1781263485.458:15832): apparmor="DENIED" operation="getattr" class="posix_mqueue" profile="/usr/bin/lxc-st>
[  +0.051371] audit: type=1400 audit(1781263485.510:15833): apparmor="DENIED" operation="getattr" class="posix_mqueue" profile="/usr/bin/lxc-st>
[  +0.064925] EXT4-fs (dm-6): mounted filesystem 2fe804d6-8a10-4df5-b260-b496f8a968ed r/w with ordered data mode. Quota mode: none.
[  +0.233953] audit: type=1400 audit(1781263485.808:15834): apparmor="STATUS" operation="profile_load" profile="/usr/bin/lxc-start" name="lxc-5>
[  +0.494820] vmbr0: port 2(veth501i0) entered blocking state
[  +0.000006] vmbr0: port 2(veth501i0) entered disabled state
[  +0.000027] veth501i0: entered allmulticast mode
[  +0.000052] veth501i0: entered promiscuous mode
[  +0.036034] eth0: renamed from vethojCVBk
[  +0.125635] audit: type=1400 audit(1781263486.465:15835): apparmor="STATUS" operation="profile_remove" profile="/usr/bin/lxc-start" name="lxc>
[  +0.021103] vmbr0: port 2(veth501i0) entered disabled state
[  +0.000210] veth501i0 (unregistering): left allmulticast mode
[  +0.000004] veth501i0 (unregistering): left promiscuous mode
[  +0.000004] vmbr0: port 2(veth501i0) entered disabled state
[  +0.421669] EXT4-fs (dm-6): unmounting filesystem 2fe804d6-8a10-4df5-b260-b496f8a968ed.
[Jun12 13:26] audit: type=1400 audit(1781263597.426:15836): apparmor="DENIED" operation="getattr" class="posix_mqueue" profile="/usr/bin/lxc-st>
[  +0.055083] audit: type=1400 audit(1781263597.481:15837): apparmor="DENIED" operation="getattr" class="posix_mqueue" profile="/usr/bin/lxc-st>
[  +0.075805] EXT4-fs (dm-6): mounted filesystem 2fe804d6-8a10-4df5-b260-b496f8a968ed r/w with ordered data mode. Quota mode: none.
[  +0.218860] audit: type=1400 audit(1781263597.776:15838): apparmor="STATUS" operation="profile_load" profile="/usr/bin/lxc-start" name="lxc-5>
[  +0.496341] vmbr0: port 2(veth501i0) entered blocking state
[  +0.000007] vmbr0: port 2(veth501i0) entered disabled state
[  +0.000028] veth501i0: entered allmulticast mode
[  +0.000057] veth501i0: entered promiscuous mode
[  +0.040510] eth0: renamed from veth8dD3mA
[  +0.123692] audit: type=1400 audit(1781263598.437:15839): apparmor="STATUS" operation="profile_remove" profile="/usr/bin/lxc-start" name="lxc>
[  +0.021143] vmbr0: port 2(veth501i0) entered disabled state
[  +0.000212] veth501i0 (unregistering): left allmulticast mode
[  +0.000003] veth501i0 (unregistering): left promiscuous mode
[  +0.000003] vmbr0: port 2(veth501i0) entered disabled state
[  +0.435085] EXT4-fs (dm-6): unmounting filesystem 2fe804d6-8a10-4df5-b260-b496f8a968ed.

Last edited:

Does apt -U dist-upgrade go through without warnings/errors? What's systemctl --failed say? Does it behave/look different after a reboot of the node?