Error when starting a CT

fanumtax123

New Member
Mar 21, 2024
12
0
1
Hello, every time i start the CT i created it pops up a error in log "stopped: startup for container 103 failed".
and in output i get this
run_buffer: 322 Script exited with status 1
lxc_setup: 4437 Failed to run mount hooks
do_start: 1272 Failed to setup container "103"
sync_wait: 34 An error occurred in another process (expected sequence number 4)
__lxc_start: 2107 Failed to spawn container "103"
TASK ERROR: startup for container '103' failed
could anyone please help me?
ty
 
Hi!
could you post the output of the syslog?
 
run_buffer: 322 Script exited with status 1
lxc_setup: 4437 Failed to run mount hooks
do_start: 1272 Failed to setup container "103"
sync_wait: 34 An error occurred in another process (expected sequence number 4)
__lxc_start: 2107 Failed to spawn container "103"
TASK ERROR: startup for container '103' failed
 
run_buffer: 322 Script exited with status 1
lxc_setup: 4437 Failed to run mount hooks
do_start: 1272 Failed to setup container "103"
sync_wait: 34 An error occurred in another process (expected sequence number 4)
__lxc_start: 2107 Failed to spawn container "103"
TASK ERROR: startup for container '103' failed
You already showed the tasklog in the first post.
could you post the output of the syslog?
The syslog can be viewed with journalctl but you'll have to scroll with the arrow key to around the time of the problem to see if there are helpful error messages.
could someone help out please?
Maybe you can get more information by obtaining the debug log for the container start: https://pve.proxmox.com/wiki/Linux_Container#_obtaining_debugging_logs ?
 
Apr 02 04:48:18 praks pvedaemon[9212]: startup for container '103' failed
Apr 02 04:48:18 praks pvedaemon[1386]: <root@pam> end task UPID:praks:000023FC:0004D4A4:660B63E0:vzstart:103:root@pam: startup for container '103' >
Apr 02 04:48:18 praks audit[9266]: AVC apparmor="STATUS" operation="profile_remove" profile="/usr/bin/lxc-start" name="lxc-103_</var/lib/lxc>" pid=>
Apr 02 04:48:18 praks kernel: audit: type=1400 audit(1712022498.794:38): apparmor="STATUS" operation="profile_remove" profile="/usr/bin/lxc-start" >
Apr 02 04:48:18 praks pvedaemon[1385]: unable to get PID for CT 103 (not running?)
Apr 02 04:48:18 praks kernel: vmbr0: port 2(veth103i0) entered disabled state
Apr 02 04:48:18 praks kernel: veth103i0 (unregistering): left allmulticast mode
Apr 02 04:48:18 praks kernel: veth103i0 (unregistering): left promiscuous mode
Apr 02 04:48:18 praks kernel: vmbr0: port 2(veth103i0) entered disabled state
Apr 02 04:48:19 praks kernel: EXT4-fs (dm-9): unmounting filesystem 010ae5d6-c258-4040-b472-b973fef01572.
Apr 02 04:48:19 praks systemd[1]: pve-container@103.service: Main process exited, code=exited, status=1/FAILURE
Apr 02 04:48:19 praks systemd[1]: pve-container@103.service: Failed with result 'exit-code'.
Apr 02 04:49:14 praks pvedaemon[9410]: starting termproxy UPID:praks:000024C2:0004EB16:660B641A:vncshell::root@pam:
Apr 02 04:49:14 praks pvedaemon[1386]: <root@pam> starting task UPID:praks:000024C2:0004EB16:660B641A:vncshell::root@pam:
Apr 02 04:49:14 praks pvedaemon[1385]: <root@pam> successful auth for user 'root@pam'
Apr 02 04:49:14 praks login[9414]: pam_unix(login:session): session opened for user root(uid=0) by (uid=0)
Apr 02 04:49:14 praks dbus-daemon[961]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.se>
Apr 02 04:49:14 praks systemd[1]: Starting modprobe@drm.service - Load Kernel Module drm...
Apr 02 04:49:14 praks systemd[1]: modprobe@drm.service: Deactivated successfully.
Apr 02 04:49:14 praks systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm.
Apr 02 04:49:14 praks systemd[1]: Starting systemd-logind.service - User Login Management...

all i get is this
 
run_buffer: 322 Script exited with status 1
lxc_setup: 4437 Failed to run mount hooks
do_start: 1272 Failed to setup container "103"
sync_wait: 34 An error occurred in another process (expected sequence number 4)
__lxc_start: 2107 Failed to spawn container "103"
3221225534]
INFO seccomp - ../src/lxc/seccomp.c:parse_config_v2:807 - Processing "reject_force_umount # comment this to allow umount -f; not recommended"
INFO seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:524 - Set seccomp rule to reject force umounts
INFO seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:524 - Set seccomp rule to reject force umounts
INFO seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:524 - Set seccomp rule to reject force umounts
INFO seccomp - ../src/lxc/seccomp.c:parse_config_v2:807 - Processing "[all]"
INFO seccomp - ../src/lxc/seccomp.c:parse_config_v2:807 - Processing "kexec_load errno 1"
INFO seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:564 - Adding native rule for syscall[246:kexec_load] action[327681:errno] arch[0]
INFO seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:564 - Adding compat rule for syscall[246:kexec_load] action[327681:errno] arch[1073741827]
INFO seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:564 - Adding compat rule for syscall[246:kexec_load] action[327681:errno] arch[1073741886]
INFO seccomp - ../src/lxc/seccomp.c:parse_config_v2:807 - Processing "open_by_handle_at errno 1"
INFO seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:564 - Adding native rule for syscall[304:eek:pen_by_handle_at] action[327681:errno] arch[0]
INFO seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:564 - Adding compat rule for syscall[304:eek:pen_by_handle_at] action[327681:errno] arch[1073741827]
INFO seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:564 - Adding compat rule for syscall[304:eek:pen_by_handle_at] action[327681:errno] arch[1073741886]
INFO seccomp - ../src/lxc/seccomp.c:parse_config_v2:807 - Processing "init_module errno 1"
INFO seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:564 - Adding native rule for syscall[175:init_module] action[327681:errno] arch[0]
INFO seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:564 - Adding compat rule for syscall[175:init_module] action[327681:errno] arch[1073741827]
INFO seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:564 - Adding compat rule for syscall[175:init_module] action[327681:errno] arch[1073741886]
INFO seccomp - ../src/lxc/seccomp.c:parse_config_v2:807 - Processing "finit_module errno 1"
INFO seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:564 - Adding native rule for syscall[313:finit_module] action[327681:errno] arch[0]
INFO seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:564 - Adding compat rule for syscall[313:finit_module] action[327681:errno] arch[1073741827]
INFO seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:564 - Adding compat rule for syscall[313:finit_module] action[327681:errno] arch[1073741886]
INFO seccomp - ../src/lxc/seccomp.c:parse_config_v2:807 - Processing "delete_module errno 1"
INFO seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:564 - Adding native rule for syscall[176:delete_module] action[327681:errno] arch[0]
INFO seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:564 - Adding compat rule for syscall[176:delete_module] action[327681:errno] arch[1073741827]
INFO seccomp - ../src/lxc/seccomp.c:do_resolve_add_rule:564 - Adding compat rule for syscall[176:delete_module] action[327681:errno] arch[1073741886]
INFO seccomp - ../src/lxc/seccomp.c:parse_config_v2:1017 - Merging compat seccomp contexts into main context
INFO start - ../src/lxc/start.c:lxc_init:881 - Container "103" is initialized
INFO cgfsng - ../src/lxc/cgroups/cgfsng.c:cgfsng_monitor_create:1391 - The monitor process uses "lxc.monitor/103" as cgroup
DEBUG storage - ../src/lxc/storage/storage.c:storage_query:231 - Detected rootfs type "dir"
INFO cgfsng - ../src/lxc/cgroups/cgfsng.c:cgfsng_payload_create:1499 - The container process uses "lxc/103/ns" as inner and "lxc/103" as limit cgroup
INFO start - ../src/lxc/start.c:lxc_spawn:1762 - Cloned CLONE_NEWNS
INFO start - ../src/lxc/start.c:lxc_spawn:1762 - Cloned CLONE_NEWPID
INFO start - ../src/lxc/start.c:lxc_spawn:1762 - Cloned CLONE_NEWUTS
INFO start - ../src/lxc/start.c:lxc_spawn:1762 - Cloned CLONE_NEWIPC
INFO start - ../src/lxc/start.c:lxc_spawn:1762 - Cloned CLONE_NEWNET
INFO start - ../src/lxc/start.c:lxc_spawn:1762 - Cloned CLONE_NEWCGROUP
DEBUG start - ../src/lxc/start.c:lxc_try_preserve_namespace:139 - Preserved mnt namespace via fd 18 and stashed path as mnt:/proc/7448/fd/18
DEBUG start - ../src/lxc/start.c:lxc_try_preserve_namespace:139 - Preserved pid namespace via fd 19 and stashed path as pid:/proc/7448/fd/19
DEBUG start - ../src/lxc/start.c:lxc_try_preserve_namespace:139 - Preserved uts namespace via fd 20 and stashed path as uts:/proc/7448/fd/20
DEBUG start - ../src/lxc/start.c:lxc_try_preserve_namespace:139 - Preserved ipc namespace via fd 21 and stashed path as ipc:/proc/7448/fd/21
DEBUG start - ../src/lxc/start.c:lxc_try_preserve_namespace:139 - Preserved net namespace via fd 22 and stashed path as net:/proc/7448/fd/22
DEBUG start - ../src/lxc/start.c:lxc_try_preserve_namespace:139 - Preserved cgroup namespace via fd 23 and stashed path as cgroup:/proc/7448/fd/23
WARN cgfsng - ../src/lxc/cgroups/cgfsng.c:cgfsng_setup_limits_legacy:3155 - Invalid argument - Ignoring legacy cgroup limits on pure cgroup2 system
INFO cgfsng - ../src/lxc/cgroups/cgfsng.c:cgfsng_setup_limits:3251 - Limits for the unified cgroup hierarchy have been setup
INFO conf - ../src/lxc/conf.c:run_script_argv:338 - Executing script "/usr/share/lxc/lxcnetaddbr" for container "103", config section "net"
DEBUG network - ../src/lxc/network.c:netdev_configure_server_veth:852 - Instantiated veth tunnel "veth103i0 <--> vethm9rPSL"
DEBUG conf - ../src/lxc/conf.c:lxc_mount_rootfs:1437 - Mounted rootfs "/var/lib/lxc/103/rootfs" onto "/usr/lib/x86_64-linux-gnu/lxc/rootfs" with options "(null)"
INFO conf - ../src/lxc/conf.c:setup_utsname:876 - Set hostname to "sigma"
DEBUG network - ../src/lxc/network.c:setup_hw_addr:3821 - Mac address "BC:24:11:8E:84:B7" on "eth0" has been setup
DEBUG network - ../src/lxc/network.c:lxc_network_setup_in_child_namespaces_common:3962 - Network device "eth0" has been setup
INFO network - ../src/lxc/network.c:lxc_setup_network_in_child_namespaces:4019 - Finished setting up network devices with caller assigned names
INFO conf - ../src/lxc/conf.c:mount_autodev:1220 - Preparing "/dev"
INFO conf - ../src/lxc/conf.c:mount_autodev:1281 - Prepared "/dev"
DEBUG conf - ../src/lxc/conf.c:lxc_mount_auto_mounts:736 - Invalid argument - Tried to ensure procfs is unmounted
DEBUG conf - ../src/lxc/conf.c:lxc_mount_auto_mounts:759 - Invalid argument - Tried to ensure sysfs is unmounted
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
DEBUG conf - ../src/lxc/conf.c:mount_entry:2464 - Flags for "/sys/fs/fuse/connections" were 4110, required extra flags are 14
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"
DEBUG cgfsng - ../src/lxc/cgroups/cgfsng.c:__cgroupfs_mount:1909 - Mounted cgroup filesystem cgroup2 onto 20((null))
INFO conf - ../src/lxc/conf.c:run_script_argv:338 - Executing script "/usr/share/lxcfs/lxc.mount.hook" for container "103", config section "lxc"
DEBUG conf - ../src/lxc/conf.c:run_buffer:311 - Script exec /usr/share/lxcfs/lxc.mount.hook 103 lxc mount produced output: missing /var/lib/lxcfs/proc/ - lxcfs not running?

ERROR conf - ../src/lxc/conf.c:run_buffer:322 - Script exited with status 1
ERROR conf - ../src/lxc/conf.c:lxc_setup:4437 - Failed to run mount hooks
ERROR start - ../src/lxc/start.c:do_start:1272 - Failed to setup container "103"
ERROR sync - ../src/lxc/sync.c:sync_wait:34 - An error occurred in another process (expected sequence number 4)
DEBUG network - ../src/lxc/network.c:lxc_delete_network:4173 - Deleted network devices
ERROR start - ../src/lxc/start.c:__lxc_start:2107 - Failed to spawn container "103"
WARN start - ../src/lxc/start.c:lxc_abort:1036 - No such process - Failed to send SIGKILL via pidfd 17 for process 7465
startup for container '103' failed
 

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!

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!