lxc-container fährt nicht mehr hoch

E

Erza86

New Member
Oct 18, 2016
10
2
3
38
Hallo,

ich bekomme seit kurzem einen LXC-Container nicht mehr hoch gefahren:

lxc-start 101 20180330104101.251 INFO lxc_start_ui - tools/lxc_start.c:main:280 - using rcfile /var/lib/lxc/101/config
lxc-start 101 20180330104101.252 INFO lxc_lsm - lsm/lsm.c:lsm_init:48 - LSM security driver AppArmor
lxc-start 101 20180330104101.252 INFO lxc_seccomp - seccomp.c:parse_config_v2:435 - processing: .reject_force_umount # comment this to allow umount -f; not recommended.
lxc-start 101 20180330104101.252 INFO lxc_seccomp - seccomp.c:parse_config_v2:610 - Adding native rule for reject_force_umount action 0(kill).
lxc-start 101 20180330104101.252 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:276 - Setting Seccomp rule to reject force umounts.
lxc-start 101 20180330104101.252 INFO lxc_seccomp - seccomp.c:parse_config_v2:614 - Adding compat rule for reject_force_umount action 0(kill).
lxc-start 101 20180330104101.252 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:276 - Setting Seccomp rule to reject force umounts.
lxc-start 101 20180330104101.252 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:276 - Setting Seccomp rule to reject force umounts.
lxc-start 101 20180330104101.252 INFO lxc_seccomp - seccomp.c:parse_config_v2:435 - processing: .[all].
lxc-start 101 20180330104101.252 INFO lxc_seccomp - seccomp.c:parse_config_v2:435 - processing: .kexec_load errno 1.
lxc-start 101 20180330104101.252 INFO lxc_seccomp - seccomp.c:parse_config_v2:610 - Adding native rule for kexec_load action 327681(errno).
lxc-start 101 20180330104101.252 INFO lxc_seccomp - seccomp.c:parse_config_v2:614 - Adding compat rule for kexec_load action 327681(errno).
lxc-start 101 20180330104101.252 INFO lxc_seccomp - seccomp.c:parse_config_v2:435 - processing: .open_by_handle_at errno 1.
lxc-start 101 20180330104101.252 INFO lxc_seccomp - seccomp.c:parse_config_v2:610 - Adding native rule for open_by_handle_at action 327681(errno).
lxc-start 101 20180330104101.252 INFO lxc_seccomp - seccomp.c:parse_config_v2:614 - Adding compat rule for open_by_handle_at action 327681(errno).
lxc-start 101 20180330104101.252 INFO lxc_seccomp - seccomp.c:parse_config_v2:435 - processing: .init_module errno 1.
lxc-start 101 20180330104101.252 INFO lxc_seccomp - seccomp.c:parse_config_v2:610 - Adding native rule for init_module action 327681(errno).
lxc-start 101 20180330104101.252 INFO lxc_seccomp - seccomp.c:parse_config_v2:614 - Adding compat rule for init_module action 327681(errno).
lxc-start 101 20180330104101.252 INFO lxc_seccomp - seccomp.c:parse_config_v2:435 - processing: .finit_module errno 1.
lxc-start 101 20180330104101.252 INFO lxc_seccomp - seccomp.c:parse_config_v2:610 - Adding native rule for finit_module action 327681(errno).
lxc-start 101 20180330104101.252 INFO lxc_seccomp - seccomp.c:parse_config_v2:614 - Adding compat rule for finit_module action 327681(errno).
lxc-start 101 20180330104101.252 INFO lxc_seccomp - seccomp.c:parse_config_v2:435 - processing: .delete_module errno 1.
lxc-start 101 20180330104101.252 INFO lxc_seccomp - seccomp.c:parse_config_v2:610 - Adding native rule for delete_module action 327681(errno).
lxc-start 101 20180330104101.252 INFO lxc_seccomp - seccomp.c:parse_config_v2:614 - Adding compat rule for delete_module action 327681(errno).
lxc-start 101 20180330104101.252 INFO lxc_seccomp - seccomp.c:parse_config_v2:624 - Merging in the compat Seccomp ctx into the main one.
lxc-start 101 20180330104101.252 INFO lxc_conf - conf.c:run_script_argv:457 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "101", config section "lxc".
lxc-start 101 20180330104101.642 DEBUG lxc_start - start.c:setup_signal_fd:301 - Set SIGCHLD handler with file descriptor: 5.
lxc-start 101 20180330104101.643 DEBUG console - console.c:lxc_console_peer_default:459 - using "/dev/tty" as peer tty device
lxc-start 101 20180330104101.643 DEBUG console - console.c:lxc_console_sigwinch_init:151 - process 9543 created signal fd 9 to handle SIGWINCH events
lxc-start 101 20180330104101.643 DEBUG console - console.c:lxc_console_winsz:71 - set winsz dstfd:6 cols:222 rows:47
lxc-start 101 20180330104101.643 INFO lxc_start - start.c:lxc_init:680 - container "101" is initialized
lxc-start 101 20180330104101.643 INFO lxc_conf - conf.c:run_script:507 - Executing script "/usr/share/lxc/lxcnetaddbr" for container "101", config section "net".
lxc-start 101 20180330104101.901 DEBUG lxc_network - network.c:instantiate_veth:219 - Instantiated veth "veth101i0/veth9RX066", index is "24"
lxc-start 101 20180330104101.901 INFO lxc_cgroup - cgroups/cgroup.c:cgroup_init:67 - cgroup driver cgroupfs-ng initing for 101
lxc-start 101 20180330104101.901 ERROR lxc_cgfsng - cgroups/cgfsng.c:create_path_for_hierarchy:1337 - Path "/sys/fs/cgroup/systemd//lxc/101" already existed.
lxc-start 101 20180330104101.901 ERROR lxc_cgfsng - cgroups/cgfsng.c:cgfsng_create:1433 - Failed to create "/sys/fs/cgroup/systemd//lxc/101"
lxc-start 101 20180330104101.901 ERROR lxc_cgfsng - cgroups/cgfsng.c:create_path_for_hierarchy:1337 - Path "/sys/fs/cgroup/systemd//lxc/101-1" already existed.
lxc-start 101 20180330104101.901 ERROR lxc_cgfsng - cgroups/cgfsng.c:cgfsng_create:1433 - Failed to create "/sys/fs/cgroup/systemd//lxc/101-1"
lxc-start 101 20180330104101.901 ERROR lxc_cgfsng - cgroups/cgfsng.c:create_path_for_hierarchy:1337 - Path "/sys/fs/cgroup/systemd//lxc/101-2" already existed.
lxc-start 101 20180330104101.901 ERROR lxc_cgfsng - cgroups/cgfsng.c:cgfsng_create:1433 - Failed to create "/sys/fs/cgroup/systemd//lxc/101-2"
lxc-start 101 20180330104101.901 ERROR lxc_cgfsng - cgroups/cgfsng.c:create_path_for_hierarchy:1337 - Path "/sys/fs/cgroup/systemd//lxc/101-3" already existed.
lxc-start 101 20180330104101.901 ERROR lxc_cgfsng - cgroups/cgfsng.c:cgfsng_create:1433 - Failed to create "/sys/fs/cgroup/systemd//lxc/101-3"
lxc-start 101 20180330104101.901 ERROR lxc_cgfsng - cgroups/cgfsng.c:create_path_for_hierarchy:1337 - Path "/sys/fs/cgroup/systemd//lxc/101-4" already existed.
lxc-start 101 20180330104101.901 ERROR lxc_cgfsng - cgroups/cgfsng.c:cgfsng_create:1433 - Failed to create "/sys/fs/cgroup/systemd//lxc/101-4"
lxc-start 101 20180330104101.901 ERROR lxc_cgfsng - cgroups/cgfsng.c:create_path_for_hierarchy:1337 - Path "/sys/fs/cgroup/systemd//lxc/101-5" already existed.
lxc-start 101 20180330104101.901 ERROR lxc_cgfsng - cgroups/cgfsng.c:cgfsng_create:1433 - Failed to create "/sys/fs/cgroup/systemd//lxc/101-5"
lxc-start 101 20180330104101.901 ERROR lxc_cgfsng - cgroups/cgfsng.c:create_path_for_hierarchy:1337 - Path "/sys/fs/cgroup/systemd//lxc/101-6" already existed.
lxc-start 101 20180330104101.901 ERROR lxc_cgfsng - cgroups/cgfsng.c:cgfsng_create:1433 - Failed to create "/sys/fs/cgroup/systemd//lxc/101-6"
lxc-start 101 20180330104101.901 ERROR lxc_cgfsng - cgroups/cgfsng.c:create_path_for_hierarchy:1337 - Path "/sys/fs/cgroup/systemd//lxc/101-7" already existed.
lxc-start 101 20180330104101.901 ERROR lxc_cgfsng - cgroups/cgfsng.c:cgfsng_create:1433 - Failed to create "/sys/fs/cgroup/systemd//lxc/101-7"
lxc-start 101 20180330104101.901 ERROR lxc_cgfsng - cgroups/cgfsng.c:create_path_for_hierarchy:1337 - Path "/sys/fs/cgroup/systemd//lxc/101-8" already existed.
lxc-start 101 20180330104101.901 ERROR lxc_cgfsng - cgroups/cgfsng.c:cgfsng_create:1433 - Failed to create "/sys/fs/cgroup/systemd//lxc/101-8"
lxc-start 101 20180330104101.901 DEBUG lxc_cgfsng - cgroups/cgfsng.c:filter_and_set_cpus:469 - No isolated cpus detected.
lxc-start 101 20180330104101.901 DEBUG lxc_cgfsng - cgroups/cgfsng.c:handle_cpuset_hierarchy:640 - "cgroup.clone_children" was already set to "1".
lxc-start 101 20180330104101.902 INFO lxc_start - start.c:lxc_spawn:1259 - Cloned CLONE_NEWNS.
lxc-start 101 20180330104101.902 INFO lxc_start - start.c:lxc_spawn:1259 - Cloned CLONE_NEWPID.
lxc-start 101 20180330104101.902 INFO lxc_start - start.c:lxc_spawn:1259 - Cloned CLONE_NEWUTS.
lxc-start 101 20180330104101.902 INFO lxc_start - start.c:lxc_spawn:1259 - Cloned CLONE_NEWIPC.
lxc-start 101 20180330104101.902 INFO lxc_start - start.c:lxc_spawn:1259 - Cloned CLONE_NEWNET.
lxc-start 101 20180330104101.902 DEBUG lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2132 - cgroup 'memory.limit_in_bytes' set to '4294967296'
lxc-start 101 20180330104101.902 DEBUG lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2132 - cgroup 'memory.memsw.limit_in_bytes' set to '6442450944'
lxc-start 101 20180330104101.902 DEBUG lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2132 - cgroup 'cpu.shares' set to '1024'
lxc-start 101 20180330104101.902 DEBUG lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2132 - cgroup 'cpuset.cpus' set to '0,7'
lxc-start 101 20180330104101.902 INFO lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2137 - cgroup has been setup
lxc-start 101 20180330104101.932 DEBUG lxc_network - network.c:lxc_network_move_created_netdev_priv:2450 - Moved network device "veth9RX066"/"eth0" to network namespace of 9614
lxc-start 101 20180330104101.932 DEBUG lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2132 - cgroup 'devices.deny' set to 'a'
lxc-start 101 20180330104101.932 DEBUG lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2132 - cgroup 'devices.allow' set to 'c *:* m'
lxc-start 101 20180330104101.932 DEBUG lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2132 - cgroup 'devices.allow' set to 'b *:* m'
lxc-start 101 20180330104101.932 DEBUG lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2132 - cgroup 'devices.allow' set to 'c 1:3 rwm'
lxc-start 101 20180330104101.932 DEBUG lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2132 - cgroup 'devices.allow' set to 'c 1:5 rwm'
lxc-start 101 20180330104101.932 DEBUG lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2132 - cgroup 'devices.allow' set to 'c 1:7 rwm'
lxc-start 101 20180330104101.932 DEBUG lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2132 - cgroup 'devices.allow' set to 'c 5:0 rwm'
lxc-start 101 20180330104101.932 DEBUG lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2132 - cgroup 'devices.allow' set to 'c 5:1 rwm'
lxc-start 101 20180330104101.932 DEBUG lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2132 - cgroup 'devices.allow' set to 'c 5:2 rwm'
lxc-start 101 20180330104101.932 DEBUG lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2132 - cgroup 'devices.allow' set to 'c 1:8 rwm'
lxc-start 101 20180330104101.932 DEBUG lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2132 - cgroup 'devices.allow' set to 'c 1:9 rwm'
lxc-start 101 20180330104101.932 DEBUG lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2132 - cgroup 'devices.allow' set to 'c 136:* rwm'
lxc-start 101 20180330104101.932 DEBUG lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2132 - cgroup 'devices.allow' set to 'c 10:229 rwm'
lxc-start 101 20180330104101.932 DEBUG lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2132 - cgroup 'devices.allow' set to 'c 254:0 rm'
lxc-start 101 20180330104101.932 DEBUG lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2132 - cgroup 'devices.allow' set to 'c 10:200 rwm'
lxc-start 101 20180330104101.932 DEBUG lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2132 - cgroup 'devices.allow' set to 'c 10:228 rwm'
lxc-start 101 20180330104101.932 DEBUG lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2132 - cgroup 'devices.allow' set to 'c 10:232 rwm'
lxc-start 101 20180330104101.932 INFO lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2137 - cgroup has been setup
lxc-start 101 20180330104101.933 INFO lxc_start - start.c:do_start:925 - Unshared CLONE_NEWCGROUP.
lxc-start 101 20180330104101.933 DEBUG storage - storage/storage.c:storage_query:252 - Detected rootfs type "dir"
lxc-start 101 20180330104101.933 DEBUG lxc_conf - conf.c:lxc_setup_rootfs:1319 - Mounted rootfs "/var/lib/lxc/101/rootfs" onto "/usr/lib/x86_64-linux-gnu/lxc/rootfs" with options "(null)".
lxc-start 101 20180330104101.933 INFO lxc_conf - conf.c:setup_utsname:768 - 'spon' hostname has been setup
lxc-start 101 20180330104101.956 DEBUG lxc_network - network.c:setup_hw_addr:2716 - Mac address "16:FD:ED:B0:BC:7D" on "eth0" has been setup
lxc-start 101 20180330104101.956 DEBUG lxc_network - network.c:lxc_setup_netdev_in_child_namespaces:2974 - Network device "eth0" has been setup
lxc-start 101 20180330104101.956 INFO lxc_network - network.c:lxc_setup_network_in_child_namespaces:3002 - network has been setup
lxc-start 101 20180330104101.956 INFO lxc_conf - conf.c:mount_autodev:1149 - Preparing "/dev"
lxc-start 101 20180330104101.956 INFO lxc_conf - conf.c:mount_autodev:1171 - Mounted tmpfs on "/usr/lib/x86_64-linux-gnu/lxc/rootfs/dev"
lxc-start 101 20180330104101.956 INFO lxc_conf - conf.c:mount_autodev:1188 - Prepared "/dev"
lxc-start 101 20180330104101.956 DEBUG lxc_conf - conf.c:mount_entry:1863 - 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 101 20180330104101.956 DEBUG lxc_conf - conf.c:mount_entry:1884 - Flags for "/sys/fs/fuse/connections" were 4096, required extra flags are 0
lxc-start 101 20180330104101.956 DEBUG lxc_conf - conf.c:mount_entry:1894 - Mountflags already were 4096, skipping remount
lxc-start 101 20180330104101.956 DEBUG lxc_conf - conf.c:mount_entry:1921 - Mounted "/sys/fs/fuse/connections" on "/usr/lib/x86_64-linux-gnu/lxc/rootfs/sys/fs/fuse/connections" with filesystem type "none"
lxc-start 101 20180330104101.956 INFO lxc_conf - conf.c:mount_file_entries:2212 - Set up mount entries
lxc-start 101 20180330104101.956 INFO lxc_conf - conf.c:run_script_argv:457 - Executing script "/usr/share/lxcfs/lxc.mount.hook" for container "101", config section "lxc".
lxc-start 101 20180330104101.966 INFO lxc_conf - conf.c:run_script_argv:457 - Executing script "/usr/share/lxc/hooks/lxc-pve-autodev-hook" for container "101", config section "lxc".
lxc-start 101 20180330104102.658 INFO lxc_conf - conf.c:lxc_fill_autodev:1224 - Populating "/dev"
lxc-start 101 20180330104102.658 DEBUG lxc_conf - conf.c:lxc_fill_autodev:1270 - Created device node "/usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/null"
lxc-start 101 20180330104102.658 DEBUG lxc_conf - conf.c:lxc_fill_autodev:1270 - Created device node "/usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/zero"
lxc-start 101 20180330104102.658 DEBUG lxc_conf - conf.c:lxc_fill_autodev:1270 - Created device node "/usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/full"
lxc-start 101 20180330104102.658 DEBUG lxc_conf - conf.c:lxc_fill_autodev:1270 - Created device node "/usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/urandom"
lxc-start 101 20180330104102.658 DEBUG lxc_conf - conf.c:lxc_fill_autodev:1270 - Created device node "/usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/random"
lxc-start 101 20180330104102.658 DEBUG lxc_conf - conf.c:lxc_fill_autodev:1270 - Created device node "/usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/tty"
lxc-start 101 20180330104102.658 INFO lxc_conf - conf.c:lxc_fill_autodev:1275 - Populated "/dev"
lxc-start 101 20180330104102.658 DEBUG lxc_conf - conf.c:lxc_setup_dev_console:1603 - mounted pts device "/dev/pts/4" onto "/usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/console"
lxc-start 101 20180330104102.659 INFO lxc_utils - utils.c:lxc_mount_proc_if_needed:1758 - I am 1, /proc/self points to "1"
lxc-start 101 20180330104102.879 DEBUG lxc_conf - conf.c:setup_rootfs_pivot_root:1127 - pivot_root syscall to '/usr/lib/x86_64-linux-gnu/lxc/rootfs' successful
lxc-start 101 20180330104102.879 DEBUG lxc_conf - conf.c:setup_pivot_root:1436 - finished pivot root
lxc-start 101 20180330104102.880 DEBUG lxc_conf - conf.c:lxc_setup_devpts:1481 - mount new devpts instance with options "newinstance,ptmxmode=0666,mode=0620,gid=5,max=1024"
lxc-start 101 20180330104102.880 DEBUG lxc_conf - conf.c:lxc_setup_devpts:1501 - created dummy "/dev/ptmx" file as bind mount target
lxc-start 101 20180330104102.880 DEBUG lxc_conf - conf.c:lxc_setup_devpts:1506 - bind mounted "/dev/pts/ptmx" to "/dev/ptmx"
lxc-start 101 20180330104102.881 DEBUG lxc_conf - conf.c:lxc_allocate_ttys:964 - allocated pty "/dev/pts/0" with master fd 11 and slave fd 14
lxc-start 101 20180330104102.881 DEBUG lxc_conf - conf.c:lxc_allocate_ttys:964 - allocated pty "/dev/pts/1" with master fd 15 and slave fd 16
lxc-start 101 20180330104102.881 INFO lxc_conf - conf.c:lxc_allocate_ttys:984 - finished allocating 2 pts devices
lxc-start 101 20180330104102.881 DEBUG lxc_conf - conf.c:lxc_setup_ttys:921 - Bind mounted "/dev/pts/0" onto "/dev/tty1"
lxc-start 101 20180330104102.882 DEBUG lxc_conf - conf.c:lxc_setup_ttys:921 - Bind mounted "/dev/pts/1" onto "/dev/tty2"
lxc-start 101 20180330104102.882 INFO lxc_conf - conf.c:lxc_setup_ttys:930 - Finished setting up 2 /dev/tty<N> device(s)
lxc-start 101 20180330104102.882 INFO lxc_conf - conf.c:setup_personality:1542 - set personality to '0x0'
lxc-start 101 20180330104102.882 DEBUG lxc_conf - conf.c:setup_caps:2368 - drop capability 'mac_admin' (33)
lxc-start 101 20180330104102.882 DEBUG lxc_conf - conf.c:setup_caps:2368 - drop capability 'mac_override' (32)
lxc-start 101 20180330104102.882 DEBUG lxc_conf - conf.c:setup_caps:2368 - drop capability 'sys_time' (25)
lxc-start 101 20180330104102.882 DEBUG lxc_conf - conf.c:setup_caps:2368 - drop capability 'sys_module' (16)
lxc-start 101 20180330104102.882 DEBUG lxc_conf - conf.c:setup_caps:2368 - drop capability 'sys_rawio' (17)
lxc-start 101 20180330104102.882 DEBUG lxc_conf - conf.c:setup_caps:2377 - capabilities have been setup
lxc-start 101 20180330104102.882 NOTICE lxc_conf - conf.c:lxc_setup:3277 - Container "101" is set up
lxc-start 101 20180330104102.882 INFO lxc_apparmor - lsm/apparmor.c:apparmor_process_label_set:238 - changed apparmor profile to lxc-container-default-cgns
lxc-start 101 20180330104102.885 NOTICE lxc_start - start.c:start:1550 - Exec'ing "/sbin/init".
lxc-start 101 20180330104102.886 ERROR lxc_start - start.c:start:1553 - No such file or directory - Failed to exec "/sbin/init".
lxc-start 101 20180330104102.887 ERROR lxc_sync - sync.c:__sync_wait:57 - An error occurred in another process (expected sequence number 7)
lxc-start 101 20180330104102.887 ERROR lxc_start - start.c:__lxc_start:1477 - Failed to spawn container "101".
lxc-start 101 20180330104102.888 WARN lxc_cgfsng - cgroups/cgfsng.c:cgroup_rmdir:1250 - Failed to delete "/sys/fs/cgroup/systemd//lxc/101-9/ns": Device or resource busy
lxc-start 101 20180330104102.888 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1288 - Error destroying /sys/fs/cgroup/systemd//lxc/101-9
lxc-start 101 20180330104102.889 WARN lxc_cgfsng - cgroups/cgfsng.c:cgroup_rmdir:1250 - Failed to delete "/sys/fs/cgroup/cpu//lxc/101-9/ns": Device or resource busy
lxc-start 101 20180330104102.890 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1288 - Error destroying /sys/fs/cgroup/cpu//lxc/101-9
lxc-start 101 20180330104102.892 WARN lxc_cgfsng - cgroups/cgfsng.c:cgroup_rmdir:1250 - Failed to delete "/sys/fs/cgroup/blkio//lxc/101-9/ns": Device or resource busy
lxc-start 101 20180330104102.892 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1288 - Error destroying /sys/fs/cgroup/blkio//lxc/101-9
lxc-start 101 20180330104102.894 WARN lxc_cgfsng - cgroups/cgfsng.c:cgroup_rmdir:1250 - Failed to delete "/sys/fs/cgroup/memory//lxc/101-9/ns": Device or resource busy
lxc-start 101 20180330104102.895 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1288 - Error destroying /sys/fs/cgroup/memory//lxc/101-9
lxc-start 101 20180330104102.896 WARN lxc_cgfsng - cgroups/cgfsng.c:cgroup_rmdir:1250 - Failed to delete "/sys/fs/cgroup/net_cls//lxc/101-9/ns": Device or resource busy
lxc-start 101 20180330104102.896 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1288 - Error destroying /sys/fs/cgroup/net_cls//lxc/101-9
lxc-start 101 20180330104102.896 WARN lxc_cgfsng - cgroups/cgfsng.c:cgroup_rmdir:1250 - Failed to delete "/sys/fs/cgroup/devices//lxc/101-9/ns": Device or resource busy
lxc-start 101 20180330104102.896 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1288 - Error destroying /sys/fs/cgroup/devices//lxc/101-9
lxc-start 101 20180330104102.897 WARN lxc_cgfsng - cgroups/cgfsng.c:cgroup_rmdir:1250 - Failed to delete "/sys/fs/cgroup/rdma//lxc/101-9/ns": Device or resource busy
lxc-start 101 20180330104102.898 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1288 - Error destroying /sys/fs/cgroup/rdma//lxc/101-9
lxc-start 101 20180330104102.898 WARN lxc_cgfsng - cgroups/cgfsng.c:cgroup_rmdir:1250 - Failed to delete "/sys/fs/cgroup/hugetlb//lxc/101-9/ns": Device or resource busy
lxc-start 101 20180330104102.898 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1288 - Error destroying /sys/fs/cgroup/hugetlb//lxc/101-9
lxc-start 101 20180330104102.899 WARN lxc_cgfsng - cgroups/cgfsng.c:cgroup_rmdir:1250 - Failed to delete "/sys/fs/cgroup/pids//lxc/101-9/ns": Device or resource busy
lxc-start 101 20180330104102.899 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1288 - Error destroying /sys/fs/cgroup/pids//lxc/101-9
lxc-start 101 20180330104102.901 WARN lxc_cgfsng - cgroups/cgfsng.c:cgroup_rmdir:1250 - Failed to delete "/sys/fs/cgroup/cpuset//lxc/101-9/ns": Device or resource busy
lxc-start 101 20180330104102.901 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1288 - Error destroying /sys/fs/cgroup/cpuset//lxc/101-9
lxc-start 101 20180330104102.901 WARN lxc_cgfsng - cgroups/cgfsng.c:cgroup_rmdir:1250 - Failed to delete "/sys/fs/cgroup/freezer//lxc/101-9/ns": Device or resource busy
lxc-start 101 20180330104102.902 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1288 - Error destroying /sys/fs/cgroup/freezer//lxc/101-9
lxc-start 101 20180330104102.902 WARN lxc_cgfsng - cgroups/cgfsng.c:cgroup_rmdir:1250 - Failed to delete "/sys/fs/cgroup/perf_event//lxc/101-9/ns": Device or resource busy
lxc-start 101 20180330104102.902 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1288 - Error destroying /sys/fs/cgroup/perf_event//lxc/101-9
lxc-start 101 20180330104102.902 INFO lxc_conf - conf.c:run_script_argv:457 - Executing script "/usr/share/lxcfs/lxc.reboot.hook" for container "101", config section "lxc".
lxc-start 101 20180330104102.591 INFO lxc_conf - conf.c:run_script_argv:457 - Executing script "/usr/share/lxc/hooks/lxc-pve-poststop-hook" for container "101", config section "lxc".
lxc-start 101 20180330104102.834 DEBUG lxc_conf - conf.c:run_buffer:429 - Script /usr/share/lxc/hooks/lxc-pve-poststop-hook 101 lxc post-stop with output: umount: /var/lib/lxc/101/rootfs: target is busy
.
lxc-start 101 20180330104102.834 DEBUG lxc_conf - conf.c:run_buffer:429 - Script /usr/share/lxc/hooks/lxc-pve-poststop-hook 101 lxc post-stop with output: (In some cases useful info about processes that
.
lxc-start 101 20180330104102.834 DEBUG lxc_conf - conf.c:run_buffer:429 - Script /usr/share/lxc/hooks/lxc-pve-poststop-hook 101 lxc post-stop with output: use the device is found by lsof(8) or fuser(1).)
.
lxc-start 101 20180330104102.835 DEBUG lxc_conf - conf.c:run_buffer:429 - Script /usr/share/lxc/hooks/lxc-pve-poststop-hook 101 lxc post-stop with output: command 'umount --recursive /var/lib/lxc/101/rootfs' failed: exit code 32
.
lxc-start 101 20180330104102.840 ERROR lxc_conf - conf.c:run_buffer:438 - Script exited with status 32.
lxc-start 101 20180330104102.840 ERROR lxc_start - start.c:lxc_fini:753 - Failed to run lxc.hook.post-stop for container "101".
lxc-start 101 20180330104102.840 ERROR lxc_start_ui - tools/lxc_start.c:main:371 - The container failed to start.
lxc-start 101 20180330104102.840 ERROR lxc_start_ui - tools/lxc_start.c:main:375 - Additional information can be obtained by setting the --logfile and --logpriority options.

proxmox-ve: 5.1-42 (running kernel: 4.15.10-1-pve)
pve-manager: 5.1-46 (running version: 5.1-46/ae8241d4)
pve-kernel-4.13: 5.1-43
pve-kernel-4.15: 5.1-2
pve-kernel-4.15.10-1-pve: 4.15.10-2
pve-kernel-4.13.16-1-pve: 4.13.16-43
pve-kernel-4.13.13-6-pve: 4.13.13-42
pve-kernel-4.13.13-5-pve: 4.13.13-38
pve-kernel-4.13.13-4-pve: 4.13.13-35
pve-kernel-4.13.13-3-pve: 4.13.13-34
pve-kernel-4.13.13-2-pve: 4.13.13-33
corosync: 2.4.2-pve3
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: not correctly installed
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-common-perl: 5.0-28
libpve-guest-common-perl: 2.0-14
libpve-http-server-perl: 2.0-8
libpve-storage-perl: 5.0-17
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 2.1.1-3
lxcfs: 2.0.8-2
novnc-pve: 0.6-4
proxmox-widget-toolkit: 1.0-11
pve-cluster: 5.0-20
pve-container: 2.0-19
pve-docs: 5.1-16
pve-firewall: 3.0-5
pve-firmware: 2.0-4
pve-ha-manager: 2.0-5
pve-i18n: 1.0-4
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.9.1-9
pve-xtermjs: 1.0-2
qemu-server: 5.0-22
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3

arch: amd64
cmode: console
cores: 2
hostname: spon
memory: 4096
net0: name=eth0,bridge=vmbr0,gw=94.130.220.120,gw6=fe80::1,hwaddr=16:FD:ED:B0:BC:7D,ip=94.130.220.107/32,type=veth
onboot: 1
ostype: debian
rootfs: local:101/vm-101-disk-1.raw,size=50G
startup: order=2
swap: 2048

Ign:1 http://mirror.hetzner.de/debian/packages stretch InRelease
Hit:2 http://mirror.hetzner.de/debian/security stretch/updates InRelease
Hit:3 http://mirror.hetzner.de/debian/packages stretch-updates InRelease
Hit:4 http://mirror.hetzner.de/debian/packages stretch Release
Hit:5 http://download.proxmox.com/debian/pve stretch InRelease
Hit:6 http://security.debian.org/debian-security stretch/updates InRelease
Ign:7 http://ftp.de.debian.org/debian stretch InRelease
Hit:8 http://ftp.de.debian.org/debian stretch-updates InRelease
Hit:9 http://ftp.de.debian.org/debian stretch Release
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.



Ich hoffe mir kann jemand helfen


MfG

Erza86
 
Last edited:
  • Like
Reactions: Dachshound
Steht auch im Hauptthema aber gerne nochmals ohne spoiler:

pveversion -v
proxmox-ve: 5.1-42 (running kernel: 4.15.10-1-pve)
pve-manager: 5.1-46 (running version: 5.1-46/ae8241d4)
pve-kernel-4.13: 5.1-43
pve-kernel-4.15: 5.1-2
pve-kernel-4.15.10-1-pve: 4.15.10-2
pve-kernel-4.13.16-1-pve: 4.13.16-43
pve-kernel-4.13.13-6-pve: 4.13.13-42
pve-kernel-4.13.13-5-pve: 4.13.13-38
pve-kernel-4.13.13-4-pve: 4.13.13-35
pve-kernel-4.13.13-3-pve: 4.13.13-34
pve-kernel-4.13.13-2-pve: 4.13.13-33
corosync: 2.4.2-pve3
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: not correctly installed
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-common-perl: 5.0-28
libpve-guest-common-perl: 2.0-14
libpve-http-server-perl: 2.0-8
libpve-storage-perl: 5.0-17
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 2.1.1-3
lxcfs: 2.0.8-2
novnc-pve: 0.6-4
proxmox-widget-toolkit: 1.0-11
pve-cluster: 5.0-20
pve-container: 2.0-19
pve-docs: 5.1-16
pve-firewall: 3.0-5
pve-firmware: 2.0-4
pve-ha-manager: 2.0-5
pve-i18n: 1.0-4
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.9.1-9
pve-xtermjs: 1.0-2
qemu-server: 5.0-22
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3

uname -a:

Linux prox4m1 4.15.10-1-pve #1 SMP PVE 4.15.10-2 (Wed, 21 Mar 2018 10:35:07 +0100) x86_64 GNU/Linux
 
Last edited:
Start man nen 4.13 Kernel. 4.15 ist noch nicht freigegeben. Event. hilft das schon.
 
Es lief davor auch schon nicht auf dem 4.13 Kernel - weshalb ich schon (durch das lesen des Forums) ein hochsetzen des kernels versucht hatte.
 
  • Like
Reactions: fireon
Gab es eine Situation wo du sagen könntest das hätte es event. verursacht, was war davor, wie es noch funktionierte, irgendwelche Anhaltspunkte? Du könntest veruschen die Userwatches in der sysctl.conf zu erhöhen:
Code: 
..
fs.inotify.max_user_watches=1048576
..
 
Da es ja wie gesagt so ist, dass eine VM weiterhin normal hoch und runterfährt und nur die 2.te nicht mehr will - hab ich keine Ahnung woran es liegen könnte.

Den Wert rauf zu schrauben hat nichts gebracht.
 
Hier ist die Fehlermeldung `No such file or directory - Failed to exec "/sbin/init".` interessant.

Mounte mal den container und schau ob da was fehlt bzw falsche symlinks oder so sind. Bei einem Debian container sollte das ein symlink auf /lib/systemd/systemd sein.
Das sollte in etwa so aussehen:

Code: 
~ # pct mount 101
mounted CT 101 in '/var/lib/lxc/101/rootfs'
~ # cd /var/lib/lxc/101/rootfs
/var/lib/lxc/101/rootfs # ls -ld /sbin /sbin/init
drwxr-xr-x 2 root root 4096 Mar 28 14:08 sbin
lrwxrwxrwx 1 root root   20 Feb 20 17:11 sbin/init -> /lib/systemd/systemd

Außerdem scheinen die fehlstarte cgroup ordner zrückgelassen zu haben.
Sobald das Hauptproblem gelöst ist wäre es gut diese aufzuräumen und danach den container sauber neuzustarten:
Code: 
~ # cd /sys/fs/cgroup
/sys/fs/cgroup # find */lxc/101 -depth -type d -exec rmdir -v '{}' \;
/sys/fs/cgroup # find */lxc/101-* -depth -type d -exec rmdir -v '{}' \;
(Alternativ rebooten ;-) )
 
Code: 
root@prox4m1 ~ # pct mount 101
mounted CT 101 in '/var/lib/lxc/101/rootfs'
root@prox4m1 ~ # cd /var/lib/lxc/101/rootfs
root@prox4m1 /var/lib/lxc/101/rootfs # ls -ld /sbin /sbin/init
drwxr-xr-x 2 root root 12288 Mar 29 20:31 /sbin
lrwxrwxrwx 1 root root    20 Mar 23 13:55 /sbin/init -> /lib/systemd/systemd

Hab auch die Ordner schon einmal aufgeräumt und auch 2 mal rebootet.

Führte zu keinem Erfolg.

Ich habe inzwischen für meinen Kunden eine neue VM erstellt.

Ich danke trotzdem allen für ihre Bemühungen.
 
Sinnvollerweise hab ich beim `ls` den `/` for `sbin/init` dazugeschrieben was natürlich falsch ist und den symlink vom host statt dem container zeigt. (also eigtl hätte es nach dem `cd` dann `ls -ld sbin sbin/init` (ohne den vorangestellten slashes) heißen müssen).
 
Das Ergebnis bleibt dennoch das gleiche:

Code: 
root@prox4m1 /var/lib/lxc/101/rootfs # ls -ld sbin sbin/init
drwxr-xr-x 2 root root 4096 Mar 29 18:20 sbin
lrwxrwxrwx 1 root root   20 Mar 23 13:55 sbin/init -> /lib/systemd/systemd
 
Gibt es - und funktioniert - /lib/systemd/systemd im container? Der Fehler-ausgabe von lxc nach müsste entweder das file nicht existieren - oder IIRC wenn der linker ein library nicht findet gibt es den fehler auch:
Code: 
# chroot --userspec=nobody /var/lib/lxc/101/rootfs /lib/systemd/systemd --help
bzw. wenn dann der fehler kommt aber das file existiert
Code: 
# chroot --userspec=nobody /var/lib/lxc/101/rootfs ldd /lib/systemd/systemd

Ansonsten müsste im setup code von lxc irgendwas schief gegangen sein und der Fehler nicht ordentlich erkannt :/
 
Das bekomme ich:

Code: 
root@prox4m1 /lib/systemd # chroot --userspec=nobody /var/lib/lxc/101/rootfs /lib/systemd/systemd --help
chroot: failed to run command ‘/lib/systemd/systemd’: No such file or directory
root@prox4m1 /lib/systemd # chroot --userspec=nobody /var/lib/lxc/101/rootfs ldd /lib/systemd/systemd
chroot: failed to run command ‘ldd’: Permission denied
 
Habe das gleiche Problem. Hatte über die GUI ein update gemacht, und dann ging die LXC nicht mehr. Nach den ändern auf die 4.15 ging in Container, wieder, doch der andere bleibt stumm.

Code: 
      lxc-start 108 20180408171928.493 INFO     lxc_start_ui - tools/lxc_start.c:main:280 - using rcfile /var/lib/lxc/108/config
      lxc-start 108 20180408171928.493 INFO     lxc_lsm - lsm/lsm.c:lsm_init:48 - LSM security driver AppArmor
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:435 - processing: .reject_force_umount  # comment this to allow umount -f;  not recommended.
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:610 - Adding native rule for reject_force_umount action 0(kill).
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:do_resolve_add_rule:276 - Setting Seccomp rule to reject force umounts.
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:614 - Adding compat rule for reject_force_umount action 0(kill).
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:do_resolve_add_rule:276 - Setting Seccomp rule to reject force umounts.
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:do_resolve_add_rule:276 - Setting Seccomp rule to reject force umounts.
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:435 - processing: .[all].
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:435 - processing: .kexec_load errno 1.
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:610 - Adding native rule for kexec_load action 327681(errno).
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:614 - Adding compat rule for kexec_load action 327681(errno).
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:435 - processing: .open_by_handle_at errno 1.
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:610 - Adding native rule for open_by_handle_at action 327681(errno).
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:614 - Adding compat rule for open_by_handle_at action 327681(errno).
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:435 - processing: .init_module errno 1.
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:610 - Adding native rule for init_module action 327681(errno).
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:614 - Adding compat rule for init_module action 327681(errno).
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:435 - processing: .finit_module errno 1.
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:610 - Adding native rule for finit_module action 327681(errno).
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:614 - Adding compat rule for finit_module action 327681(errno).
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:435 - processing: .delete_module errno 1.
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:610 - Adding native rule for delete_module action 327681(errno).
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:614 - Adding compat rule for delete_module action 327681(errno).
      lxc-start 108 20180408171928.493 INFO     lxc_seccomp - seccomp.c:parse_config_v2:624 - Merging in the compat Seccomp ctx into the main one.
      lxc-start 108 20180408171928.493 INFO     lxc_conf - conf.c:run_script_argv:457 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "108", config section "lxc".
      lxc-start 108 20180408171928.885 DEBUG    lxc_conf - conf.c:run_buffer:429 - Script /usr/share/lxc/hooks/lxc-pve-prestart-hook 108 lxc pre-start with output: mount: /dev/mapper/ssd1--vg-vm--108--disk--1 is already mounted or /var/lib/lxc/108/rootfs busy
.
      lxc-start 108 20180408171928.885 DEBUG    lxc_conf - conf.c:run_buffer:429 - Script /usr/share/lxc/hooks/lxc-pve-prestart-hook 108 lxc pre-start with output:        /dev/mapper/ssd1--vg-vm--108--disk--1 is already mounted on /var/lib/lxc/108/rootfs
.
      lxc-start 108 20180408171928.885 DEBUG    lxc_conf - conf.c:run_buffer:429 - Script /usr/share/lxc/hooks/lxc-pve-prestart-hook 108 lxc pre-start with output: command 'mount /dev/dm-15 /var/lib/lxc/108/rootfs//' failed: exit code 32
.
      lxc-start 108 20180408171928.894 ERROR    lxc_conf - conf.c:run_buffer:438 - Script exited with status 32.
      lxc-start 108 20180408171928.894 ERROR    lxc_start - start.c:lxc_init:651 - Failed to run lxc.hook.pre-start for container "108".
      lxc-start 108 20180408171928.894 ERROR    lxc_start - start.c:__lxc_start:1444 - Failed to initialize container "108".
      lxc-start 108 20180408171928.894 ERROR    lxc_start_ui - tools/lxc_start.c:main:371 - The container failed to start.
      lxc-start 108 20180408171928.894 ERROR    lxc_start_ui - tools/lxc_start.c:main:375 - Additional information can be obtained by setting the --logfile and --logpriority options.

Code: 
proxmox-ve: 5.1-42 (running kernel: 4.15.10-1-pve)
pve-manager: 5.1-46 (running version: 5.1-46/ae8241d4)
pve-kernel-4.13: 5.1-43
pve-kernel-4.15: 5.1-2
pve-kernel-4.15.10-1-pve: 4.15.10-2
pve-kernel-4.13.16-1-pve: 4.13.16-43
pve-kernel-4.13.13-2-pve: 4.13.13-33
corosync: 2.4.2-pve3
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-common-perl: 5.0-28
libpve-guest-common-perl: 2.0-14
libpve-http-server-perl: 2.0-8
libpve-storage-perl: 5.0-17
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 2.1.1-3
lxcfs: 2.0.8-2
novnc-pve: 0.6-4
proxmox-widget-toolkit: 1.0-11
pve-cluster: 5.0-20
pve-container: 2.0-19
pve-docs: 5.1-16
pve-firewall: 3.0-5
pve-firmware: 2.0-4
pve-ha-manager: 2.0-5
pve-i18n: 1.0-4
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.9.1-9
pve-xtermjs: 1.0-2
qemu-server: 5.0-22
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.6-pve1~bpo9

Der Container 107 ging nach dem hochstufen auf 4.15. Der 108 bleibt stumm.

Code: 
#PiHole
arch: amd64
cores: 1
hostname: Mown
lock: mounted
memory: 256
net0: name=eth0,bridge=vmbr0,hwaddr=32:82:F2:17:4C:37,ip=dhcp,type=veth
onboot: 1
ostype: debian
rootfs: VM-Image-ssd1-thin:vm-108-disk-1,size=8G
swap: 256

Code: 
#SFTP Norbert, Sebastian
arch: amd64
cores: 1
hostname: TrinTragula
memory: 256
net0: name=eth0,bridge=vmbr0,hwaddr=7A:A0:76:2F:D9:75,ip=dhcp,type=veth
onboot: 1
ostype: debian
rootfs: herzog:vm-107-disk-1,size=2T
swap: 512

Code: 
  --- Logical volume ---
  LV Path                /dev/ssd1-vg/vm-108-disk-1
  LV Name                vm-108-disk-1
  VG Name                ssd1-vg
  LV UUID                K7vxBo-EajJ-z6xH-63JE-kiKq-FKFI-BqTuiV
  LV Write Access        read/write
  LV Creation host, time arthur, 2018-02-23 18:42:23 +0100
  LV Pool name           ssd-thin
  LV Status              available
  # open                 1
  LV Size                8.00 GiB
  Mapped size            99.59%
  Current LE             2048
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:15
 
  --- Logical volume ---
  LV Path                /dev/ironwolf10tb_1/vm-107-disk-1
  LV Name                vm-107-disk-1
  VG Name                ironwolf10tb_1
  LV UUID                XbnQDx-gk5y-t0eq-iFzX-fP0a-ND9L-r7JjIz
  LV Write Access        read/write
  LV Creation host, time arthur, 2018-01-29 21:19:24 +0100
  LV Pool name           herzog
  LV Status              available
  # open                 1
  LV Size                2.00 TiB
  Mapped size            39.15%
  Current LE             524288
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:20

Code: 
Hit:1 http://security.debian.org stretch/updates InRelease
Ign:2 http://ftp.de.debian.org/debian stretch InRelease
Hit:3 http://ftp.de.debian.org/debian stretch Release
Hit:5 https://enterprise.proxmox.com/debian/pve stretch InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Code: 
proxmox-ve: 5.1-42 (running kernel: 4.15.10-1-pve)
pve-manager: 5.1-46 (running version: 5.1-46/ae8241d4)
pve-kernel-4.13: 5.1-43
pve-kernel-4.15: 5.1-2
pve-kernel-4.15.10-1-pve: 4.15.10-2
pve-kernel-4.13.16-1-pve: 4.13.16-43
pve-kernel-4.13.13-2-pve: 4.13.13-33
corosync: 2.4.2-pve3
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-common-perl: 5.0-28
libpve-guest-common-perl: 2.0-14
libpve-http-server-perl: 2.0-8
libpve-storage-perl: 5.0-17
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 2.1.1-3
lxcfs: 2.0.8-2
novnc-pve: 0.6-4
proxmox-widget-toolkit: 1.0-11
pve-cluster: 5.0-20
pve-container: 2.0-19
pve-docs: 5.1-16
pve-firewall: 3.0-5
pve-firmware: 2.0-4
pve-ha-manager: 2.0-5
pve-i18n: 1.0-4
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.9.1-9
pve-xtermjs: 1.0-2
qemu-server: 5.0-22
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.6-pve1~bpo9
 
Last edited:
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