[SOLVED] Failed to run lxc.hook.pre-start

Just like andrei-z, I don't understand why the updates broke lxc containers, but installing binutils fixed this issue. If someone here knows why this happened and/or why binutils was the solution, I'd be curious to know.
 
I had the same problem, the solution has (apparently) worked. However, now I can no longer reach my web pages (HTTP ERROR 500) :(
 
Just recording in case anyone else has this happen.

I got the same error in the UI, then I ran this:
Bash: 
lxc-start -n 178 -F -lDEBUG -o lxc-178.log
Inspected the log and saw a "disk quota exceeded" message, aka the provisioned disk was full. I expanded the attached root storage and it started right up.
 
saures said:
Okay, here it is again:

Code: 
lxc-start -n 101 -F -lDEBUG -o lxc-101.log
storage does not support content type 'none'
unable to detect OS distribution
lxc-start: conf.c: run_buffer: 405 Script exited with status 2.
lxc-start: start.c: lxc_init: 450 Failed to run lxc.hook.pre-start for container "101".
lxc-start: start.c: __lxc_start: 1321 Failed to initialize container "101".
lxc-start: tools/lxc_start.c: main: 366 The container failed to start.
lxc-start: tools/lxc_start.c: main: 370 Additional information can be obtained by setting the --logfile and --logpriority options.
Click to expand...
try to run pct fsck 101 then start the VM machine
the problem is in the storage
 
Last edited:
hello group I am trying to restore a backup of a proxmox v5.2.1 container in another v7.4 but I get the following error when starting

run_buffer: 322 Script exited with status 1
lxc_init: 844 Failed to run lxc.hook.pre-start for container "102"
__lxc_start: 2027 Failed to initialize container "102"
TASK ERROR: startup for container '102' failed

look for the possible error and this was the result

lxc-start -n 102 -F -lDEBUG -o lxc-102.log
lxc-start: 102: ../src/lxc/conf.c: run_buffer: 322 Script exited with status 1
lxc-start: 102: ../src/lxc/start.c: lxc_init: 844 Failed to run lxc.hook.pre-start for container "102"
lxc-start: 102: ../src/lxc/start.c: __lxc_start: 2027 Failed to initialize container "102"
lxc-start: 102: ../src/lxc/tools/lxc_start.c: main: 306 The container failed to start
lxc-start: 102: ../src/lxc/tools/lxc_start.c: main: 311 Additional information can be obtained by setting the --logfile and --logpriority options

Any help in advance would be appreciated.
 
proxnew said:
hello group I am trying to restore a backup of a proxmox v5.2.1 container in another v7.4 but I get the following error when starting

run_buffer: 322 Script exited with status 1
lxc_init: 844 Failed to run lxc.hook.pre-start for container "102"
__lxc_start: 2027 Failed to initialize container "102"
TASK ERROR: startup for container '102' failed

look for the possible error and this was the result

lxc-start -n 102 -F -lDEBUG -o lxc-102.log
lxc-start: 102: ../src/lxc/conf.c: run_buffer: 322 Script exited with status 1
lxc-start: 102: ../src/lxc/start.c: lxc_init: 844 Failed to run lxc.hook.pre-start for container "102"
lxc-start: 102: ../src/lxc/start.c: __lxc_start: 2027 Failed to initialize container "102"
lxc-start: 102: ../src/lxc/tools/lxc_start.c: main: 306 The container failed to start
lxc-start: 102: ../src/lxc/tools/lxc_start.c: main: 311 Additional information can be obtained by setting the --logfile and --logpriority options

Any help in advance would be appreciated.
Click to expand...
cat lxc-102.log
lxc-start 102 20230718160052.865 INFO lsm - ../src/lxc/lsm/lsm.c:lsm_init_static:38 - Initialized LSM security driver AppArmor
lxc-start 102 20230718160052.865 INFO conf - ../src/lxc/conf.c:run_script_argv:338 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "102", config section "lxc"
lxc-start 102 20230718160053.468 DEBUG conf - ../src/lxc/conf.c:run_buffer:311 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 102 lxc pre-start produced output: unable to open file '/etc/systemd/network/eno1.network.tmp.40043' - No such file or directory

lxc-start 102 20230718160053.470 DEBUG conf - ../src/lxc/conf.c:run_buffer:311 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 102 lxc pre-start produced output: error in setup task PVE::LXC::Setup::pre_start_hook

lxc-start 102 20230718160053.479 ERROR conf - ../src/lxc/conf.c:run_buffer:322 - Script exited with status 1
lxc-start 102 20230718160053.479 ERROR start - ../src/lxc/start.c:lxc_init:844 - Failed to run lxc.hook.pre-start for container "102"
lxc-start 102 20230718160053.479 ERROR start - ../src/lxc/start.c:__lxc_start:2027 - Failed to initialize container "102"
lxc-start 102 20230718160053.479 INFO conf - ../src/lxc/conf.c:run_script_argv:338 - Executing script "/usr/share/lxc/hooks/lxc-pve-poststop-hook" for container "102", config section "lxc"
lxc-start 102 20230718160053.977 INFO conf - ../src/lxc/conf.c:run_script_argv:338 - Executing script "/usr/share/lxcfs/lxc.reboot.hook" for container "102", config section "lxc"
lxc-start 102 20230718160054.478 ERROR lxc_start - ../src/lxc/tools/lxc_start.c:main:306 - The container failed to start
lxc-start 102 20230718160054.478 ERROR lxc_start - ../src/lxc/tools/lxc_start.c:main:311 - Additional information can be obtained by setting the --logfile and --logpriority options
lxc-start 102 20230718170435.633 INFO lsm - ../src/lxc/lsm/lsm.c:lsm_init_static:38 - Initialized LSM security driver AppArmor
lxc-start 102 20230718170435.633 INFO conf - ../src/lxc/conf.c:run_script_argv:338 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "102", config section "lxc"
lxc-start 102 20230718170436.327 DEBUG conf - ../src/lxc/conf.c:run_buffer:311 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 102 lxc pre-start produced output: unable to open file '/etc/systemd/network/enp2s0.network.tmp.49903' - No such file or directory

lxc-start 102 20230718170436.328 DEBUG conf - ../src/lxc/conf.c:run_buffer:311 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 102 lxc pre-start produced output: error in setup task PVE::LXC::Setup::pre_start_hook

lxc-start 102 20230718170436.337 ERROR conf - ../src/lxc/conf.c:run_buffer:322 - Script exited with status 1
lxc-start 102 20230718170436.337 ERROR start - ../src/lxc/start.c:lxc_init:844 - Failed to run lxc.hook.pre-start for container "102"
lxc-start 102 20230718170436.337 ERROR start - ../src/lxc/start.c:__lxc_start:2027 - Failed to initialize container "102"
lxc-start 102 20230718170436.338 INFO conf - ../src/lxc/conf.c:run_script_argv:338 - Executing script "/usr/share/lxc/hooks/lxc-pve-poststop-hook" for container "102", config section "lxc"
lxc-start 102 20230718170436.794 INFO conf - ../src/lxc/conf.c:run_script_argv:338 - Executing script "/usr/share/lxcfs/lxc.reboot.hook" for container "102", config section "lxc"
lxc-start 102 20230718170437.295 ERROR lxc_start - ../src/lxc/tools/lxc_start.c:main:306 - The container failed to start
lxc-start 102 20230718170437.295 ERROR lxc_start - ../src/lxc/tools/lxc_start.c:main:311 - Additional information can be obtained by setting the --logfile and --logpriority options
 
please post the container config as well..
 
fabian said:
please post the container config as well..
Click to expand...
pct config 102
arch: i386
cpulimit: 2
cpuunits: 1024
hostname: proxy.grm.inder.gob.cu
memory: 1625
nameserver: 192.168.37.1 172.16.65.2 172.16.64.1
net0: name=eno1,bridge=vmbr0,gw=192.168.10.2,hwaddr=D6:C7:35:A1:F0:50,ip=192.168.10.7/26,type=veth
net1: name=enp2s0,bridge=vmbr1,gw=192.168.37.1,hwaddr=C2:01:E0:5B:8E:14,ip=192.168.37.7/24,type=veth
onboot: 1
ostype: ubuntu
rootfs: local-lvm:vm-102-disk-0,size=25G
searchdomain: grm.eicma.cu
swap: 4040
 
okay. it seems like the container is detected as modern (>= 17.10) Ubuntu, which means the network settings you make in PVE will be transferred to the container via systemd-networkd, and that fails.. can you check if the /etc/systemd/network directory exists in the container? (e.g., via "pct mount")?
 
Grunchy said:
Somehow I've got "disk quota exceeded" on my LXC-100.

I tried the first solution, no effect:
# apt install binutils
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
binutils is already the newest version (2.35.2-2).
0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.

Next I tried the debug:
# lxc-start -n 100 -F -lDEBUG -o lxc-100.log
lxc-start: 100: ../src/lxc/conf.c: run_buffer: 322 Script exited with status 1
lxc-start: 100: ../src/lxc/start.c: lxc_init: 844 Failed to run lxc.hook.pre-start for container "100"
lxc-start: 100: ../src/lxc/start.c: __lxc_start: 2027 Failed to initialize container "100"
lxc-start: 100: ../src/lxc/tools/lxc_start.c: main: 306 The container failed to start
lxc-start: 100: ../src/lxc/tools/lxc_start.c: main: 311 Additional information can be obtained by setting the --logfile and --logpriority options

Looking into that log:
# cat lxc-100.log
lxc-start 100 20230908174311.459 INFO lsm - ../src/lxc/lsm/lsm.c:lsm_init_static:38 - Initialized LSM security driver AppArmor
lxc-start 100 20230908174311.459 INFO conf - ../src/lxc/conf.c:run_script_argv:338 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "100", config section "lxc"
lxc-start 100 20230908174312.266 DEBUG conf - ../src/lxc/conf.c:run_buffer:311 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 100 lxc pre-start produced output: unable to open file '/fastboot.tmp.2692' - Disk quota exceeded

lxc-start 100 20230908174312.268 DEBUG conf - ../src/lxc/conf.c:run_buffer:311 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 100 lxc pre-start produced output: error in setup task PVE::LXC::Setup::pre_start_hook

lxc-start 100 20230908174312.282 ERROR conf - ../src/lxc/conf.c:run_buffer:322 - Script exited with status 1
lxc-start 100 20230908174312.282 ERROR start - ../src/lxc/start.c:lxc_init:844 - Failed to run lxc.hook.pre-start for container "100"
lxc-start 100 20230908174312.282 ERROR start - ../src/lxc/start.c:__lxc_start:2027 - Failed to initialize container "100"
lxc-start 100 20230908174312.283 INFO conf - ../src/lxc/conf.c:run_script_argv:338 - Executing script "/usr/share/lxc/hooks/lxc-pve-poststop-hook" for container "100", config section "lxc"
lxc-start 100 20230908174313.821 INFO conf - ../src/lxc/conf.c:run_script_argv:338 - Executing script "/usr/share/lxcfs/lxc.reboot.hook" for container "100", config section "lxc"
lxc-start 100 20230908174313.584 ERROR lxc_start - ../src/lxc/tools/lxc_start.c:main:306 - The container failed to start
lxc-start 100 20230908174313.584 ERROR lxc_start - ../src/lxc/tools/lxc_start.c:main:311 - Additional information can be obtained by setting the --logfile and --logpriority options

From Proxmox VE 7.4-16 dashboard I have this information:

PVE Node/Disks:
/dev/sda Type = SSD, Usage = partitions, Size = 120.03 GB, GPT = Yes, Model = Kingston SSD
/dev/sda1 Type = partition, Usage = BIOS boot, size = 1.03 MB, GPT = Yes
/dev/sda2 Type = partition, Usage = EFI, size = 1.07 GB, GPT = Yes
/dev/sda3 Type = partition, Usage = LVM, size=118.96 GB, GPT = Yes
/dev/sdb Type = Hard Disk, Usage = partitions, Size = 3.00 TB, GPT = Yes, Model = HGST
/dev/sdb1 Type = partition, Usage = ZFS, Size = 3.00 TB, GPT = Yes
/dev/sdb9 Type = partition, Usage = ZFS reserved, Size = 8.39 MB, GPT = Yes

PVE Node/Disks/LVM:
Name = pve, Number of LVs = 3, Assigned to LVs = 88%, Size = 118.95 GB, Free = 14.76 GB <-- yellow
Name = /dev/sda3, Assigned to LVs = 88%, Size = 118.95 GB, Free = 14.76 GB <-- yellow

PVE Node/Disks/LVM Thin:
Name = data, Volume Group = pve, Usage = 0%, Size = 53.28 GB, Used = 0B, Metadata Usage = 2%, Metadata Size = 1.07 GB, Metadata Used 17.07 MB

PVE Node/Disks/ZFS:
Name = ZFS, Size = 2.99 TB, Free = 2.83 TB, Allocated 161.18 GB, Fragmentation = 0%, Health = Online
Click to expand...
please open a new thread!
 
had a similar issue- power went out. container wouldnt start

making a backup and restoring it fixed my issue.
 
My problem was disk usage inside container, I had to clean up. In my case I use container id 100, change for your needs:
  • mount container:
    Code: 
    pct mount 100
  • inspect and delete files inside container, eg compressed logfiles if not needed any more:
    Code: 
    cd /var/lib/lxc/100/rootfs/ && rm var/log/*gz
  • umount container:
    Code: 
    pct unmount 100
  • start container:
    Code: 
    pct start 100
This solved my issue ...
 
Still happens
Code: 
pveversion -v
proxmox-ve: 8.1.0 (running kernel: 6.5.11-7-pve)
pve-manager: 8.1.3 (running version: 8.1.3/b46aac3b42da5d15)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.5: 6.5.11-7
proxmox-kernel-6.5.11-7-pve-signed: 6.5.11-7
ceph-fuse: 16.2.11+ds-2
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown: residual config
ifupdown2: 3.2.0-1+pmx7
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.1
libpve-access-control: 8.0.7
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.1.0
libpve-guest-common-perl: 5.0.6
libpve-http-server-perl: 5.0.5
libpve-network-perl: 0.9.5
libpve-rs-perl: 0.8.7
libpve-storage-perl: 8.0.5
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve4
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.1.2-1
proxmox-backup-file-restore: 3.1.2-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.2
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.3
proxmox-widget-toolkit: 4.1.3
pve-cluster: 8.0.5
pve-container: 5.0.8
pve-docs: 8.1.3
pve-edk2-firmware: not correctly installed
pve-firewall: 5.0.3
pve-firmware: 3.9-1
pve-ha-manager: 4.0.3
pve-i18n: 3.1.4
pve-qemu-kvm: 8.1.2-4
pve-xtermjs: 5.3.0-2
qemu-server: 8.0.10
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.2-pve1

A simple container (ID 50013) cannot be started all of a sudden.
Single tiny, disk on zfs pool storage.
This happened suddenly after a while of not using it.

Created another (ID 50014) just like it with "exact" same config and starts.
The 50014 does not start with disk of 50013.


Proxmox itself is on zfs and so are the LXC and VM disks.
Pools report no errors.
Is there any form of way to check virtual disk's health?
... as part of proxmox lifecycle, startup, shudown, etc.
 
Last edited:
are there any errors in the task or system log?
 
Hi everyone!
I have a similar problem.
Suddenly my LXC no longer wants to start. It ran smoothly for over a year.

Here's the config:
Code: 
## DebMatic LXC
### Debian 12 (bookworm)
arch: amd64
cores: 4
hostname: debmatic
memory: 4096
nameserver: 192.168.122.1
net0: name=eth0,bridge=vmbr0,gw=192.168.122.1,hwaddr=12:6F:95:FB:13:B5,ip=192.168.122.30/24,tag=122,type=veth
onboot: 0
ostype: debian
rootfs: local-lvm:vm-201-disk-0,size=8G
startup: order=2,up=180,down=15
swap: 512
lxc.apparmor.profile: unconfined
lxc.hook.mount: /usr/share/debmatic/bin/lxc-start-hook.sh
lxc.cgroup2.devices.allow: a
lxc.cgroup2.devices.deny: c 29:0 m
lxc.cgroup2.devices.deny: c 189:131 m
lxc.cgroup2.devices.deny: c 226:0 m
lxc.cgroup2.devices.deny: c 226:128 m
lxc.cgroup2.devices.deny: c 189:1 m
lxc.cgroup2.devices.deny: c 189:2 m
lxc.cgroup2.devices.deny: c 189:5 m
lxc.cgroup2.devices.deny: c 189:6 m
lxc.cgroup2.devices.allow: c 189:4 rwm
lxc.mount.entry: /dev/bus/usb/001/005 dev/bus/usb none bind,optional,create=file
and here is the log when I start the container like this:
lxc-start -n 201 -F -lDEBUG -o lxc-201.log
Code: 
lxc-start 201 20240209152027.102 INFO     lsm - ../src/lxc/lsm/lsm.c:lsm_init_static:38 - Initialized LSM security driver AppArmor
lxc-start 201 20240209152027.104 INFO     conf - ../src/lxc/conf.c:run_script_argv:338 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "201", config section "lxc"
lxc-start 201 20240209152027.465 DEBUG    seccomp - ../src/lxc/seccomp.c:parse_config_v2:656 - Host native arch is [3221225534]
lxc-start 201 20240209152027.465 INFO     seccomp - ../src/lxc/seccomp.c:parse_config_v2:807 - Processing "reject_force_umount  # comment this to allow umount -f;  not recommended"
lxc-start 201 20240209152027.465 INFO     seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:524 - Set seccomp rule to reject force umounts
lxc-start 201 20240209152027.465 INFO     seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:524 - Set seccomp rule to reject force umounts
lxc-start 201 20240209152027.465 INFO     seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:524 - Set seccomp rule to reject force umounts
lxc-start 201 20240209152027.465 INFO     seccomp - ../src/lxc/seccomp.c:parse_config_v2:807 - Processing "[all]"
lxc-start 201 20240209152027.465 INFO     seccomp - ../src/lxc/seccomp.c:parse_config_v2:807 - Processing "kexec_load errno 1"
lxc-start 201 20240209152027.465 INFO     seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:564 - Adding native rule for syscall[246:kexec_load] action[327681:errno] arch[0]
lxc-start 201 20240209152027.465 INFO     seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:564 - Adding compat rule for syscall[246:kexec_load] action[327681:errno] arch[1073741827]
lxc-start 201 20240209152027.465 INFO     seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:564 - Adding compat rule for syscall[246:kexec_load] action[327681:errno] arch[1073741886]
lxc-start 201 20240209152027.465 INFO     seccomp - ../src/lxc/seccomp.c:parse_config_v2:807 - Processing "open_by_handle_at errno 1"
lxc-start 201 20240209152027.465 INFO     seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:564 - Adding native rule for syscall[304:open_by_handle_at] action[327681:errno] arch[0]
lxc-start 201 20240209152027.465 INFO     seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:564 - Adding compat rule for syscall[304:open_by_handle_at] action[327681:errno] arch[1073741827]
lxc-start 201 20240209152027.465 INFO     seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:564 - Adding compat rule for syscall[304:open_by_handle_at] action[327681:errno] arch[1073741886]
lxc-start 201 20240209152027.465 INFO     seccomp - ../src/lxc/seccomp.c:parse_config_v2:807 - Processing "init_module errno 1"
lxc-start 201 20240209152027.465 INFO     seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:564 - Adding native rule for syscall[175:init_module] action[327681:errno] arch[0]
lxc-start 201 20240209152027.465 INFO     seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:564 - Adding compat rule for syscall[175:init_module] action[327681:errno] arch[1073741827]
lxc-start 201 20240209152027.465 INFO     seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:564 - Adding compat rule for syscall[175:init_module] action[327681:errno] arch[1073741886]
lxc-start 201 20240209152027.465 INFO     seccomp - ../src/lxc/seccomp.c:parse_config_v2:807 - Processing "finit_module errno 1"
lxc-start 201 20240209152027.465 INFO     seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:564 - Adding native rule for syscall[313:finit_module] action[327681:errno] arch[0]
lxc-start 201 20240209152027.465 INFO     seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:564 - Adding compat rule for syscall[313:finit_module] action[327681:errno] arch[1073741827]
lxc-start 201 20240209152027.465 INFO     seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:564 - Adding compat rule for syscall[313:finit_module] action[327681:errno] arch[1073741886]
lxc-start 201 20240209152027.465 INFO     seccomp - ../src/lxc/seccomp.c:parse_config_v2:807 - Processing "delete_module errno 1"
lxc-start 201 20240209152027.465 INFO     seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:564 - Adding native rule for syscall[176:delete_module] action[327681:errno] arch[0]
lxc-start 201 20240209152027.465 INFO     seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:564 - Adding compat rule for syscall[176:delete_module] action[327681:errno] arch[1073741827]
lxc-start 201 20240209152027.465 INFO     seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:564 - Adding compat rule for syscall[176:delete_module] action[327681:errno] arch[1073741886]
lxc-start 201 20240209152027.465 INFO     seccomp - ../src/lxc/seccomp.c:parse_config_v2:1017 - Merging compat seccomp contexts into main context
lxc-start 201 20240209152027.465 INFO     start - ../src/lxc/start.c:lxc_init:881 - Container "201" is initialized
lxc-start 201 20240209152027.465 INFO     cgfsng - ../src/lxc/cgroups/cgfsng.c:cgfsng_monitor_create:1391 - The monitor process uses "lxc.monitor/201" as cgroup
lxc-start 201 20240209152027.503 DEBUG    storage - ../src/lxc/storage/storage.c:storage_query:231 - Detected rootfs type "dir"
lxc-start 201 20240209152027.503 INFO     cgfsng - ../src/lxc/cgroups/cgfsng.c:cgfsng_payload_create:1499 - The container process uses "lxc/201/ns" as inner and "lxc/201" as limit cgroup
lxc-start 201 20240209152027.503 INFO     start - ../src/lxc/start.c:lxc_spawn:1762 - Cloned CLONE_NEWNS
lxc-start 201 20240209152027.503 INFO     start - ../src/lxc/start.c:lxc_spawn:1762 - Cloned CLONE_NEWPID
lxc-start 201 20240209152027.503 INFO     start - ../src/lxc/start.c:lxc_spawn:1762 - Cloned CLONE_NEWUTS
lxc-start 201 20240209152027.503 INFO     start - ../src/lxc/start.c:lxc_spawn:1762 - Cloned CLONE_NEWIPC
lxc-start 201 20240209152027.503 INFO     start - ../src/lxc/start.c:lxc_spawn:1762 - Cloned CLONE_NEWNET
lxc-start 201 20240209152027.503 INFO     start - ../src/lxc/start.c:lxc_spawn:1762 - Cloned CLONE_NEWCGROUP
lxc-start 201 20240209152027.504 DEBUG    start - ../src/lxc/start.c:lxc_try_preserve_namespace:139 - Preserved mnt namespace via fd 18 and stashed path as mnt:/proc/19931/fd/18
lxc-start 201 20240209152027.504 DEBUG    start - ../src/lxc/start.c:lxc_try_preserve_namespace:139 - Preserved pid namespace via fd 19 and stashed path as pid:/proc/19931/fd/19
lxc-start 201 20240209152027.504 DEBUG    start - ../src/lxc/start.c:lxc_try_preserve_namespace:139 - Preserved uts namespace via fd 20 and stashed path as uts:/proc/19931/fd/20
lxc-start 201 20240209152027.504 DEBUG    start - ../src/lxc/start.c:lxc_try_preserve_namespace:139 - Preserved ipc namespace via fd 21 and stashed path as ipc:/proc/19931/fd/21
lxc-start 201 20240209152027.504 DEBUG    start - ../src/lxc/start.c:lxc_try_preserve_namespace:139 - Preserved net namespace via fd 22 and stashed path as net:/proc/19931/fd/22
lxc-start 201 20240209152027.504 DEBUG    start - ../src/lxc/start.c:lxc_try_preserve_namespace:139 - Preserved cgroup namespace via fd 23 and stashed path as cgroup:/proc/19931/fd/23
lxc-start 201 20240209152027.504 WARN     cgfsng - ../src/lxc/cgroups/cgfsng.c:cgfsng_setup_limits_legacy:3155 - Invalid argument - Ignoring legacy cgroup limits on pure cgroup2 system
lxc-start 201 20240209152027.504 INFO     cgfsng - ../src/lxc/cgroups/cgfsng.c:cgfsng_setup_limits:3251 - Limits for the unified cgroup hierarchy have been setup
lxc-start 201 20240209152027.507 INFO     conf - ../src/lxc/conf.c:run_script_argv:338 - Executing script "/usr/share/lxc/lxcnetaddbr" for container "201", config section "net"
lxc-start 201 20240209152027.950 DEBUG    network - ../src/lxc/network.c:netdev_configure_server_veth:852 - Instantiated veth tunnel "veth201i0 <--> vetheurTwv"
lxc-start 201 20240209152027.950 DEBUG    conf - ../src/lxc/conf.c:lxc_mount_rootfs:1437 - Mounted rootfs "/var/lib/lxc/201/rootfs" onto "/usr/lib/x86_64-linux-gnu/lxc/rootfs" with options "(null)"
lxc-start 201 20240209152027.950 INFO     conf - ../src/lxc/conf.c:setup_utsname:876 - Set hostname to "debmatic"
lxc-start 201 20240209152027.979 DEBUG    network - ../src/lxc/network.c:setup_hw_addr:3821 - Mac address "12:6F:95:FB:13:B5" on "eth0" has been setup
lxc-start 201 20240209152027.979 DEBUG    network - ../src/lxc/network.c:lxc_network_setup_in_child_namespaces_common:3962 - Network device "eth0" has been setup
lxc-start 201 20240209152027.979 INFO     network - ../src/lxc/network.c:lxc_setup_network_in_child_namespaces:4019 - Finished setting up network devices with caller assigned names
lxc-start 201 20240209152027.979 INFO     conf - ../src/lxc/conf.c:mount_autodev:1220 - Preparing "/dev"
lxc-start 201 20240209152027.980 INFO     conf - ../src/lxc/conf.c:mount_autodev:1281 - Prepared "/dev"
lxc-start 201 20240209152027.980 DEBUG    conf - ../src/lxc/conf.c:lxc_mount_auto_mounts:736 - Invalid argument - Tried to ensure procfs is unmounted
lxc-start 201 20240209152027.980 DEBUG    conf - ../src/lxc/conf.c:lxc_mount_auto_mounts:759 - Invalid argument - Tried to ensure sysfs is unmounted
lxc-start 201 20240209152027.980 DEBUG    conf - ../src/lxc/conf.c:mount_entry:2445 - Remounting "/sys/fs/fuse/connections" on "/usr/lib/x86_64-linux-gnu/lxc/rootfs/sys/fs/fuse/connections" to respect bind or remount options
lxc-start 201 20240209152027.980 DEBUG    conf - ../src/lxc/conf.c:mount_entry:2464 - Flags for "/sys/fs/fuse/connections" were 4110, required extra flags are 14
lxc-start 201 20240209152027.980 DEBUG    conf - ../src/lxc/conf.c:mount_entry:2508 - Mounted "/sys/fs/fuse/connections" on "/usr/lib/x86_64-linux-gnu/lxc/rootfs/sys/fs/fuse/connections" with filesystem type "none"
lxc-start 201 20240209152027.981 DEBUG    conf - ../src/lxc/conf.c:mount_entry:2445 - Remounting "/dev/bus/usb/001/005" on "/usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/bus/usb" to respect bind or remount options
lxc-start 201 20240209152027.981 DEBUG    conf - ../src/lxc/conf.c:mount_entry:2464 - Flags for "/dev/bus/usb/001/005" were 4098, required extra flags are 2
lxc-start 201 20240209152027.981 DEBUG    conf - ../src/lxc/conf.c:mount_entry:2508 - Mounted "/dev/bus/usb/001/005" on "/usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/bus/usb" with filesystem type "none"
lxc-start 201 20240209152027.981 DEBUG    cgfsng - ../src/lxc/cgroups/cgfsng.c:__cgroupfs_mount:1909 - Mounted cgroup filesystem cgroup2 onto 20((null))
lxc-start 201 20240209152027.981 INFO     conf - ../src/lxc/conf.c:run_script_argv:338 - Executing script "/usr/share/lxcfs/lxc.mount.hook" for container "201", config section "lxc"
lxc-start 201 20240209152027.994 INFO     conf - ../src/lxc/conf.c:run_script_argv:338 - Executing script "/usr/share/debmatic/bin/lxc-start-hook.sh" for container "201", config section "lxc"
lxc-start 201 20240209152027.995 DEBUG    conf - ../src/lxc/conf.c:run_buffer:311 - Script exec /usr/share/debmatic/bin/lxc-start-hook.sh 201 lxc mount produced output: sh: 1: exec: /usr/share/debmatic/bin/lxc-start-hook.sh: not found

lxc-start 201 20240209152027.995 ERROR    conf - ../src/lxc/conf.c:run_buffer:322 - Script exited with status 127
lxc-start 201 20240209152027.995 ERROR    conf - ../src/lxc/conf.c:lxc_setup:4437 - Failed to run mount hooks
lxc-start 201 20240209152027.995 ERROR    start - ../src/lxc/start.c:do_start:1272 - Failed to setup container "201"
lxc-start 201 20240209152027.995 ERROR    sync - ../src/lxc/sync.c:sync_wait:34 - An error occurred in another process (expected sequence number 4)
lxc-start 201 20240209152027.995 DEBUG    network - ../src/lxc/network.c:lxc_delete_network:4173 - Deleted network devices
lxc-start 201 20240209152027.995 ERROR    start - ../src/lxc/start.c:__lxc_start:2107 - Failed to spawn container "201"
lxc-start 201 20240209152027.995 WARN     start - ../src/lxc/start.c:lxc_abort:1036 - No such process - Failed to send SIGKILL via pidfd 17 for process 19943
lxc-start 201 20240209152028.318 INFO     conf - ../src/lxc/conf.c:run_script_argv:338 - Executing script "/usr/share/lxc/hooks/lxc-pve-poststop-hook" for container "201", config section "lxc"
lxc-start 201 20240209152028.446 DEBUG    conf - ../src/lxc/conf.c:run_buffer:311 - Script exec /usr/share/lxc/hooks/lxc-pve-poststop-hook 201 lxc post-stop produced output: umount: /var/lib/lxc/.pve-staged-mounts/mp0: not mounted.

lxc-start 201 20240209152028.446 DEBUG    conf - ../src/lxc/conf.c:run_buffer:311 - Script exec /usr/share/lxc/hooks/lxc-pve-poststop-hook 201 lxc post-stop produced output: command 'umount -- /var/lib/lxc/.pve-staged-mounts/mp0' failed: exit code 32

lxc-start 201 20240209152028.478 INFO     conf - ../src/lxc/conf.c:run_script_argv:338 - Executing script "/usr/share/lxcfs/lxc.reboot.hook" for container "201", config section "lxc"
lxc-start 201 20240209152028.979 ERROR    lxc_start - ../src/lxc/tools/lxc_start.c:main:306 - The container failed to start
lxc-start 201 20240209152028.979 ERROR    lxc_start - ../src/lxc/tools/lxc_start.c:main:311 - Additional information can be obtained by setting the --logfile and --logpriority options

and here my sysinfo
Code: 
pve-manager/8.1.4/ec5affc9e41f1d79 (running kernel: 6.5.11-8-pve)
root@pve:~# pveversion -v
proxmox-ve: 8.1.0 (running kernel: 6.5.11-8-pve)
pve-manager: 8.1.4 (running version: 8.1.4/ec5affc9e41f1d79)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.5: 6.5.11-8
proxmox-kernel-6.5.11-8-pve-signed: 6.5.11-8
proxmox-kernel-6.5.11-7-pve-signed: 6.5.11-7
ceph-fuse: 16.2.11+ds-2
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx8
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.0.7
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.1.0
libpve-guest-common-perl: 5.0.6
libpve-http-server-perl: 5.0.5
libpve-network-perl: 0.9.5
libpve-rs-perl: 0.8.8
libpve-storage-perl: 8.0.5
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve4
novnc-pve: 1.4.0-3
openvswitch-switch: 3.1.0-2
proxmox-backup-client: 3.1.4-1
proxmox-backup-file-restore: 3.1.4-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.4
proxmox-widget-toolkit: 4.1.3
pve-cluster: 8.0.5
pve-container: 5.0.8
pve-docs: 8.1.3
pve-edk2-firmware: 4.2023.08-3
pve-firewall: 5.0.3
pve-firmware: 3.9-1
pve-ha-manager: 4.0.3
pve-i18n: 3.2.0
pve-qemu-kvm: 8.1.5-2
pve-xtermjs: 5.3.0-3
qemu-server: 8.0.10
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.2-pve1

I hope someone can help me.
Sorry for the bad English.

greeting
Johnny
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back