[SOLVED] lxc starten nicht mehr die beim Upgrade 5.4 > 6.0 liefen ...

utiltiy

New Member
Jun 13, 2018
11
0
1
50
Hallo,

ich hab beim Upgrade von 5.4 nach 6.0 ein paar lxc nicht runter gefahren, diese liefen beim Upgrade noch. Nach dem nötigen Reboot laufen diese nicht mehr, sie lassen sich nicht starten...
lxc wo beim Upgrade "aus" waren laufen, genauso wie die VM's.

Kann ich mein Problem irgendwie beheben?

Meine Installation:
Code:
pveversion --verbose
proxmox-ve: 6.0-2 (running kernel: 5.0.15-1-pve)
pve-manager: 6.0-4 (running version: 6.0-4/2a719255)
pve-kernel-5.0: 6.0-5
pve-kernel-helper: 6.0-5
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph: 14.2.1-pve2
ceph-fuse: 14.2.1-pve2
corosync: 3.0.2-pve2
criu: 3.11-3
glusterfs-client: 5.5-3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.10-pve1
libpve-access-control: 6.0-2
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-2
libpve-guest-common-perl: 3.0-1
libpve-http-server-perl: 3.0-2
libpve-storage-perl: 6.0-5
libqb0: 1.0.5-1
lvm2: 2.03.02-pve3
lxc-pve: 3.1.0-61
lxcfs: 3.0.3-pve60
novnc-pve: 1.0.0-60
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.0-5
pve-cluster: 6.0-4
pve-container: 3.0-3
pve-docs: 6.0-4
pve-edk2-firmware: 2.20190614-1
pve-firewall: 4.0-5
pve-firmware: 3.0-2
pve-ha-manager: 3.0-2
pve-i18n: 2.0-2
pve-qemu-kvm: 4.0.0-3
pve-xtermjs: 3.13.2-1
qemu-server: 6.0-5
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.1-pve1

Syslog:
Code:
Jul 18 00:51:52 pve pct[98642]: <root@pam> starting task UPID:pve:00018153:00167B04:5D2FA688:vzstart:100:root@pam:

Jul 18 00:51:52 pve pct[98643]: starting CT 100: UPID:pve:00018153:00167B04:5D2FA688:vzstart:100:root@pam:
Jul 18 00:51:52 pve systemd[1]: Starting PVE LXC Container: 100...
Jul 18 00:51:52 pve kernel: [14733.591376] EXT4-fs (dm-31): mounted filesystem with ordered data mode. Opts: (null)
Jul 18 00:51:52 pve lxc-start[98645]: lxc-start: 100: lxccontainer.c: wait_on_daemonized_start: 856 No such file or directory - Failed to receive the container state
Jul 18 00:51:52 pve lxc-start[98645]: lxc-start: 100: tools/lxc_start.c: main: 330 The container failed to start
Jul 18 00:51:52 pve lxc-start[98645]: lxc-start: 100: tools/lxc_start.c: main: 333 To get more details, run the container in foreground mode
Jul 18 00:51:52 pve lxc-start[98645]: lxc-start: 100: tools/lxc_start.c: main: 336 Additional information can be obtained by setting the --logfile and --logpriority options
Jul 18 00:51:52 pve systemd[1]: pve-container@100.service: Control process exited, code=exited, status=1/FAILURE
Jul 18 00:51:52 pve systemd[1]: pve-container@100.service: Failed with result 'exit-code'.
Jul 18 00:51:52 pve systemd[1]: Failed to start PVE LXC Container: 100.
Jul 18 00:51:52 pve pvedaemon[92459]: unable to get PID for CT 100 (not running?)
Jul 18 00:51:52 pve pct[98643]: command 'systemctl start pve-container@100' failed: exit code 1
Jul 18 00:51:52 pve pct[98642]: <root@pam> end task UPID:pve:00018153:00167B04:5D2FA688:vzstart:100:root@pam: command 'systemctl start pve-container@100' failed: exit code 1
 

mira

Proxmox Staff Member
Staff member
Aug 1, 2018
438
39
28
Bitte starte den Container mit 'lxc-start -n 100 -l DEBUG -F -o /tmp/ct100.log' und poste anschließend das Log.
 

utiltiy

New Member
Jun 13, 2018
11
0
1
50
Ich hab den 101 genommen...

Code:
lxc-start 101 20190718124257.161 INFO     lsm - lsm/lsm.c:lsm_init:50 - LSM security driver AppArmor
lxc-start 101 20190718124257.167 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "reject_force_umount  # comment this to allow umount -f;  not recommended"
lxc-start 101 20190718124257.168 INFO     seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start 101 20190718124257.168 INFO     seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for reject_force_umount action 0(kill)
lxc-start 101 20190718124257.169 INFO     seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start 101 20190718124257.169 INFO     seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for reject_force_umount action 0(kill)
lxc-start 101 20190718124257.170 INFO     seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start 101 20190718124257.170 INFO     seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for reject_force_umount action 0(kill)
lxc-start 101 20190718124257.170 INFO     seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start 101 20190718124257.171 INFO     seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for reject_force_umount action 0(kill)
lxc-start 101 20190718124257.171 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "[all]"
lxc-start 101 20190718124257.171 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "kexec_load errno 1"
lxc-start 101 20190718124257.172 INFO     seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for kexec_load action 327681(errno)
lxc-start 101 20190718124257.172 INFO     seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for kexec_load action 327681(errno)
lxc-start 101 20190718124257.172 INFO     seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for kexec_load action 327681(errno)
lxc-start 101 20190718124257.173 INFO     seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for kexec_load action 327681(errno)
lxc-start 101 20190718124257.173 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "open_by_handle_at errno 1"
lxc-start 101 20190718124257.173 INFO     seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for open_by_handle_at action 327681(errno)
lxc-start 101 20190718124257.174 INFO     seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for open_by_handle_at action 327681(errno)
lxc-start 101 20190718124257.174 INFO     seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for open_by_handle_at action 327681(errno)
lxc-start 101 20190718124257.174 INFO     seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for open_by_handle_at action 327681(errno)
lxc-start 101 20190718124257.175 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "init_module errno 1"
lxc-start 101 20190718124257.175 INFO     seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for init_module action 327681(errno)
lxc-start 101 20190718124257.175 INFO     seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for init_module action 327681(errno)
lxc-start 101 20190718124257.176 INFO     seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for init_module action 327681(errno)
lxc-start 101 20190718124257.176 INFO     seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for init_module action 327681(errno)
lxc-start 101 20190718124257.176 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "finit_module errno 1"
lxc-start 101 20190718124257.177 INFO     seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for finit_module action 327681(errno)
lxc-start 101 20190718124257.177 INFO     seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for finit_module action 327681(errno)
lxc-start 101 20190718124257.178 INFO     seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for finit_module action 327681(errno)
lxc-start 101 20190718124257.178 INFO     seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for finit_module action 327681(errno)
lxc-start 101 20190718124257.178 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "delete_module errno 1"
lxc-start 101 20190718124257.178 INFO     seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for delete_module action 327681(errno)
lxc-start 101 20190718124257.179 INFO     seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for delete_module action 327681(errno)
lxc-start 101 20190718124257.179 INFO     seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for delete_module action 327681(errno)
lxc-start 101 20190718124257.179 INFO     seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for delete_module action 327681(errno)
lxc-start 101 20190718124257.180 INFO     seccomp - seccomp.c:parse_config_v2:970 - Merging compat seccomp contexts into main context
lxc-start 101 20190718124257.183 INFO     conf - conf.c:run_script_argv:356 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "101", config section "lxc"
lxc-start 101 20190718124257.393 DEBUG    conf - conf.c:run_buffer:326 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 101 lxc pre-start with output: unable to parse version info 'bullseye/sid'

lxc-start 101 20190718124257.401 ERROR    conf - conf.c:run_buffer:335 - Script exited with status 25
lxc-start 101 20190718124257.401 ERROR    start - start.c:lxc_init:861 - Failed to run lxc.hook.pre-start for container "101"
lxc-start 101 20190718124257.401 ERROR    start - start.c:__lxc_start:1944 - Failed to initialize container "101"
lxc-start 101 20190718124257.401 ERROR    lxc_start - tools/lxc_start.c:main:330 - The container failed to start
lxc-start 101 20190718124257.401 ERROR    lxc_start - tools/lxc_start.c:main:336 - Additional information can be obtained by setting the --logfile and --logpriority options
 

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
14,068
495
103
Kann ich mein Problem irgendwie beheben?
Auf keinen Fall helfen doppelte Postings im deutschen und englischen Forum, bitte in Zukunft nur in einem posten.
 

mira

Proxmox Staff Member
Staff member
Aug 1, 2018
438
39
28
Es scheint so als hätte sich seit dem letzten Start der Container die version geändert. 'bullseye/sid' wird derzeit noch nicht von uns unterstützt im Code, daher kommt das Problem. Werde mir das mal ansehen.
 

utiltiy

New Member
Jun 13, 2018
11
0
1
50
Wenn ich den Container mounte, die /etc/debian_version ändere von "bullseye" zu "buster" starten sie wieder.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE 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 your own in 60 seconds.

Buy now!