misc issues with desktop installed on pve system

R

RobFantini

Famous Member
May 24, 2012
2,084
116
133
Boston,Mass
reboot an lxc failed:
Code: 
:# pct start 34201
run_apparmor_parser: 906 Failed to run apparmor_parser on "/var/lib/lxc/34201/apparmor/lxc-34201_<-var-lib-lxc>": apparmor_parser: Unable to replace "lxc-34201_</var/lib/lxc>".  Profile doesn't conform to protocol
apparmor_prepare: 1078 Failed to load generated AppArmor profile
lxc_init: 877 Failed to initialize LSM
__lxc_start: 2039 Failed to initialize container "34201"
startup for container '34201' failed

Code: 
# cat /etc/pve/lxc/34201.conf
arch: amd64
cores: 2
features: nesting=1
hostname: sonarr-536
memory: 1024
nameserver: 172.30.24.34
net0: name=eth0,bridge=vmbr0,gw=172.30.24.2,hwaddr=BC:24:11:B5:69:41,ip=172.30.24.14/24,type=veth
onboot: 1
ostype: debian
protection: 1
rootfs: lxc2:subvol-34201-disk-0,size=8G
searchdomain: fantinibakery.com
swap: 512
lxc.mount.entry: /ht  ht  none bind,create=dir,optional 0 0
lxc.mount.entry: /tv  tv  none bind,create=dir,optional 0 0

I'm working on the issue. any suggestions on the path to a solution?
 
and another lxc
Code: 
run_apparmor_parser: 906 Failed to run apparmor_parser on "/var/lib/lxc/34101/apparmor/lxc-34101_<-var-lib-lxc>": apparmor_parser: Unable to replace "lxc-34101_</var/lib/lxc>".  Profile doesn't conform to protocol
apparmor_prepare: 1078 Failed to load generated AppArmor profile
lxc_init: 877 Failed to initialize LSM
__lxc_start: 2039 Failed to initialize container "34101"
TASK ERROR: startup for container '34101' failed


:# cat /etc/pve/lxc/34101.conf
#8/5/2024 moved dhcp server from unifi to here. ONA is used to control
arch: amd64
cores: 8
features: nesting=1
hostname: dhcp-andover
memory: 4096
nameserver: 172.30.24.34
net0: name=eth0,bridge=vmbr0,firewall=1,gw=172.30.24.2,hwaddr=BC:24:11:CC:51:3C,ip=172.30.24.3/24,type=veth
onboot: 1
ostype: debian
protection: 1
rootfs: lxc2:subvol-34101-disk-0,size=8G
searchdomain: fantinibakery.com
startup: order=1,up=5,down=5
swap: 2048

Code: 
# pveversion -v
proxmox-ve: 9.0.0 (running kernel: 6.14.11-2-pve)
pve-manager: 9.0.10 (running version: 9.0.10/deb1ca707ec72a89)
proxmox-kernel-helper: 9.0.4
pve-kernel-5.15: 7.4-3
proxmox-kernel-6.14.11-2-pve-signed: 6.14.11-2
proxmox-kernel-6.14: 6.14.11-2
proxmox-kernel-6.14.8-2-pve-signed: 6.14.8-2
proxmox-kernel-6.8.12-13-pve-signed: 6.8.12-13
proxmox-kernel-6.8: 6.8.12-13
pve-kernel-5.15.107-2-pve: 5.15.107-2
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 19.2.3-pve1
corosync: 3.1.9-pve2
criu: 4.1.1-1
dnsmasq: 2.91-1
frr-pythontools: 10.3.1-1+pve4
ifupdown2: 3.3.0-1+pmx10
intel-microcode: 3.20250512.1
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.0
libproxmox-backup-qemu0: 2.0.1
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.0.3
libpve-apiclient-perl: 3.4.0
libpve-cluster-api-perl: 9.0.6
libpve-cluster-perl: 9.0.6
libpve-common-perl: 9.0.10
libpve-guest-common-perl: 6.0.2
libpve-http-server-perl: 6.0.4
libpve-network-perl: 1.1.8
libpve-rs-perl: 0.10.10
libpve-storage-perl: 9.0.13
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2+pmx1
lxc-pve: 6.0.5-1
lxcfs: 6.0.4-pve1
novnc-pve: 1.6.0-3
proxmox-backup-client: 4.0.14-1
proxmox-backup-file-restore: 4.0.14-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.1.2
proxmox-kernel-helper: 9.0.4
proxmox-mail-forward: 1.0.2
proxmox-mini-journalreader: 1.6
proxmox-offline-mirror-helper: 0.7.1
proxmox-widget-toolkit: 5.0.5
pve-cluster: 9.0.6
pve-container: 6.0.12
pve-docs: 9.0.8
pve-edk2-firmware: 4.2025.02-4
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.3
pve-firmware: 3.16-4
pve-ha-manager: 5.0.4
pve-i18n: 3.6.0
pve-qemu-kvm: 10.0.2-4
pve-xtermjs: 5.5.0-2
pve-zsync: 2.4.0
qemu-server: 9.0.22
smartmontools: 7.4-pve1
spiceterm: 3.4.1
swtpm: 0.8.0+pve2
vncterm: 1.9.1
zfsutils-linux: 2.3.4-pve1
 
now from cli this one starts:
Code: 
pct start 34101

and this too:

Code: 
pct start  34201


I do not know why those start now and not before from cli.
 
I think the above may be related to having debian desktop installed on the pve system. lxc start / stop work okay now from gui and cli.

now there is another issue.

for vzdump backup of a kvm which is stopped , this error occurs, and the backup is not created . this show 1 ok and 2 fails:
Code: 
 34221: 2025-10-17 04:35:05 INFO: status = running
34221: 2025-10-17 04:35:05 INFO: VM Name: rsnapshot-andover
34221: 2025-10-17 04:35:05 INFO: include disk 'scsi0' 'kvm2:vm-34221-disk-0' 12G
34221: 2025-10-17 04:35:05 INFO: include disk 'scsi1' 'kvm2:vm-34221-disk-1' 3000G
34221: 2025-10-17 04:35:05 INFO: backup mode: snapshot
34221: 2025-10-17 04:35:05 INFO: ionice priority: 7
34221: 2025-10-17 04:35:05 INFO: creating vzdump archive '/backups/pve34-vz/dump/vzdump-qemu-34221-2025_10_17-04_35_05.vma.zst'
34221: 2025-10-17 04:35:05 INFO: started backup task 'ca8b4329-64d6-4465-847d-802d47d14cc9'
34221: 2025-10-17 04:35:05 INFO: resuming VM again
34221: 2025-10-17 04:35:08 INFO:   0% (1.4 GiB of 2.9 TiB) in 3s, read: 482.1 MiB/s, write: 462.2 MiB/s
34221: 2025-10-17 04:36:36 INFO:   1% (30.3 GiB of 2.9 TiB) in 1m 31s, read: 336.2 MiB/s, write: 328.8 MiB/s
...
34221: 2025-10-17 05:47:04 INFO: 100% (2.9 TiB of 2.9 TiB) in 1h 11m 59s, read: 941.5 MiB/s, write: 180.9 MiB/s
34221: 2025-10-17 05:47:04 INFO: backup is sparse: 1.71 TiB (58%) total zero data
34221: 2025-10-17 05:47:04 INFO: transferred 2.94 TiB in 4319 seconds (714.1 MiB/s)
34221: 2025-10-17 05:47:04 INFO: archive file size: 924.63GB
34221: 2025-10-17 05:47:04 INFO: adding notes to backup
34221: 2025-10-17 05:47:04 INFO: prune older backups with retention: keep-last=1
34221: 2025-10-17 05:47:04 INFO: removing backup 'vzdump:backup/vzdump-qemu-34221-2025_10_16-04_34_19.vma.zst'
34221: 2025-10-17 05:47:04 INFO: pruned 1 backup(s) not covered by keep-retention policy
34221: 2025-10-17 05:47:04 INFO: Finished Backup of VM 34221 (01:11:59)


### 2 fails:
99216: 2025-10-17 05:51:07 INFO: Starting Backup of VM 99216 (qemu)
99216: 2025-10-17 05:51:07 INFO: status = stopped
99216: 2025-10-17 05:51:07 INFO: backup mode: stop
99216: 2025-10-17 05:51:07 INFO: ionice priority: 7
99216: 2025-10-17 05:51:07 INFO: VM Name: imap-2021-01-22
99216: 2025-10-17 05:51:07 INFO: include disk 'scsi0' 'kvm2:vm-99216-disk-0' 8G
99216: 2025-10-17 05:51:07 INFO: include disk 'scsi2' 'kvm2:vm-99216-disk-1' 500G
99216: 2025-10-17 05:51:08 INFO: creating vzdump archive '/backups/pve34-vz/dump/vzdump-qemu-99216-2025_10_17-05_51_07.vma.zst'
99216: 2025-10-17 05:51:08 INFO: starting kvm to execute backup task
99216: 2025-10-17 05:51:08 ERROR: start failed: org.freedesktop.DBus.Error.Disconnected: Connection is closed
99216: 2025-10-17 05:51:08 INFO: aborting backup job
99216: 2025-10-17 05:51:08 ERROR: VM 99216 not running
99216: 2025-10-17 05:51:08 ERROR: Backup of VM 99216 failed - start failed: org.freedesktop.DBus.Error.Disconnected: Connection is closed

99500: 2025-10-17 05:51:08 INFO: Starting Backup of VM 99500 (qemu)
99500: 2025-10-17 05:51:08 INFO: status = stopped
99500: 2025-10-17 05:51:08 INFO: backup mode: stop
99500: 2025-10-17 05:51:08 INFO: ionice priority: 7
99500: 2025-10-17 05:51:08 INFO: VM Name: emails-2021-01-22
99500: 2025-10-17 05:51:08 INFO: include disk 'scsi0' 'kvm2:vm-99500-disk-0' 182G
99500: 2025-10-17 05:51:08 INFO: creating vzdump archive '/backups/pve34-vz/dump/vzdump-qemu-99500-2025_10_17-05_51_08.vma.zst'
99500: 2025-10-17 05:51:08 INFO: starting kvm to execute backup task
99500: 2025-10-17 05:51:08 ERROR: start failed: org.freedesktop.DBus.Error.Disconnected: Connection is closed
99500: 2025-10-17 05:51:08 INFO: aborting backup job
99500: 2025-10-17 05:51:08 ERROR: VM 99500 not running
99500: 2025-10-17 05:51:08 ERROR: Backup of VM 99500 failed - start failed: org.freedesktop.DBus.Error.Disconnected: Connection is closed
 
You must log in or register to reply here.
Top Bottom