[SOLVED] Nach Upgrade - kein LXC-Container startet mehr (qemu nicht betroffen)

S

SekundenKleber

Member
Mar 17, 2018
7
0
6
58
Hallo zusammen,

Wie im Thread-Titel beschrieben, heute Nachmittag ein Update gemacht und alle LXC-Container starten nicht mehr. Leider liefert Proxmox da echt wenig an Fehlermeldungen, damit man da mal etwas schlau aus diesen würde.

Es läuft:

4.10.15-1-pve

Code: 
root@pve:/home/micro# lxc-start -F -n 101
lxc-start: lxccontainer.c: do_lxcapi_start: 866 Permission denied - Failed to make / rslave at startup
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.

Code: 
root@pve:/home/micro# systemctl status lxc@101.service
â lxc@101.service - LXC Container: 101
   Loaded: loaded (/lib/systemd/system/lxc@.service; disabled; vendor preset: enabled)
  Drop-In: /usr/lib/systemd/system/lxc@.service.d
           ââpve-reboot.conf
   Active: failed (Result: exit-code) since Sat 2018-03-17 15:46:29 CET; 8s ago
     Docs: man:lxc-start
           man:lxc
  Process: 13495 ExecStart=/usr/bin/lxc-start -n 101 (code=exited, status=1/FAILURE)

Mar 17 15:46:24 pve systemd[1]: Starting LXC Container: 101...
Mar 17 15:46:29 pve lxc-start[13495]: lxc-start: tools/lxc_start.c: main: 366 The container failed to start.
Mar 17 15:46:29 pve lxc-start[13495]: lxc-start: tools/lxc_start.c: main: 368 To get more details, run the container in foreground mode.
Mar 17 15:46:29 pve lxc-start[13495]: lxc-start: tools/lxc_start.c: main: 370 Additional information can be obtained by setting the --logfile and --logpriority options.
Mar 17 15:46:29 pve systemd[1]: lxc@101.service: Control process exited, code=exited status=1
Mar 17 15:46:29 pve systemd[1]: Failed to start LXC Container: 101.
Mar 17 15:46:29 pve systemd[1]: lxc@101.service: Unit entered failed state.
Mar 17 15:46:29 pve systemd[1]: lxc@101.service: Failed with result 'exit-code'.

Das logfile meint dann folgendes

Code: 
      lxc-start 20180317124000.247 INFO     lxc_start_ui - tools/lxc_start.c:main:275 - using rcfile /var/lib/lxc/101/config
      lxc-start 20180317124000.248 WARN     lxc_confile - confile.c:config_pivotdir:2022 - lxc.pivotdir is ignored.  It will soon become an error.
      lxc-start 20180317124000.248 ERROR    lxc_container - lxccontainer.c:do_lxcapi_start:866 - Permission denied - Failed to make / rslave at startup
      lxc-start 20180317124000.248 ERROR    lxc_start_ui - tools/lxc_start.c:main:366 - The container failed to start.
      lxc-start 20180317124000.248 ERROR    lxc_start_ui - tools/lxc_start.c:main:370 - Additional information can be obtained by setting the --logfile and --logpriority options.
      lxc-start 20180317125606.261 INFO     lxc_start_ui - tools/lxc_start.c:main:275 - using rcfile /var/lib/lxc/101/config
      lxc-start 20180317125606.261 WARN     lxc_confile - confile.c:config_pivotdir:2022 - lxc.pivotdir is ignored.  It will soon become an error.
      lxc-start 20180317125606.262 ERROR    lxc_container - lxccontainer.c:do_lxcapi_start:866 - Permission denied - Failed to make / rslave at startup
      lxc-start 20180317125606.262 ERROR    lxc_start_ui - tools/lxc_start.c:main:366 - The container failed to start.
      lxc-start 20180317125606.262 ERROR    lxc_start_ui - tools/lxc_start.c:main:370 - Additional information can be obtained by setting the --logfile and --logpriority options.
      lxc-start 20180317125616.694 INFO     lxc_start_ui - tools/lxc_start.c:main:275 - using rcfile /var/lib/lxc/101/config
      lxc-start 20180317125616.695 WARN     lxc_confile - confile.c:config_pivotdir:2022 - lxc.pivotdir is ignored.  It will soon become an error.
      lxc-start 20180317125616.695 ERROR    lxc_container - lxccontainer.c:do_lxcapi_start:866 - Permission denied - Failed to make / rslave at startup
      lxc-start 20180317125616.695 ERROR    lxc_start_ui - tools/lxc_start.c:main:366 - The container failed to start.
      lxc-start 20180317125616.695 ERROR    lxc_start_ui - tools/lxc_start.c:main:370 - Additional information can be obtained by setting the --logfile and --logpriority options.
      lxc-start 20180317125633.209 INFO     lxc_start_ui - tools/lxc_start.c:main:275 - using rcfile /var/lib/lxc/101/config
      lxc-start 20180317125633.210 WARN     lxc_confile - confile.c:config_pivotdir:2022 - lxc.pivotdir is ignored.  It will soon become an error.
      lxc-start 20180317125633.210 ERROR    lxc_container - lxccontainer.c:do_lxcapi_start:866 - Permission denied - Failed to make / rslave at startup
      lxc-start 20180317125633.210 ERROR    lxc_start_ui - tools/lxc_start.c:main:366 - The container failed to start.
      lxc-start 20180317125633.210 ERROR    lxc_start_ui - tools/lxc_start.c:main:370 - Additional information can be obtained by setting the --logfile and --logpriority options.

Meine Vermutung, apparmor hupt hier herum.
Die Frage, wo liegt das Problem?


Mirko
 
Ach ja, die /etc/pve/lxc/101.conf

Code: 
arch: amd64
cores: 1
cpulimit: 1
hostname: midgard
memory: 1024
nameserver: 127.0.0.1
net0: name=eth0,bridge=vmbr0,gw=192.168.104.10,hwaddr=76:FD:BC:01:F3:48,ip=192.168.104.11/24,type=veth
onboot: 1
ostype: debian
parent: V1
rootfs: local-zfs:subvol-101-disk-1,size=8G
searchdomain: home
startup: order=1,up=10
swap: 1024

[V1]
arch: amd64
cores: 1
hostname: midgard
memory: 2048
nameserver: 127.0.0.1
net0: name=eth0,bridge=vmbr0,gw=192.168.104.10,hwaddr=76:FD:BC:01:F3:48,ip=192.168.104.11/24,type=veth
onboot: 1
ostype: debian
rootfs: local-zfs:subvol-101-disk-1,size=8G
searchdomain: home
snaptime: 1513115193
startup: order=1,up=10
swap: 1024
 
Und noch das hinterher

Code: 
root@pve:/home/micro# pveversion --verbose
proxmox-ve: 5.0-15 (running kernel: 4.10.15-1-pve)
pve-manager: 5.0-23 (running version: 5.0-23/af4267bf)
pve-kernel-4.10.15-1-pve: 4.10.15-15
libpve-http-server-perl: 2.0-5
lvm2: 2.02.168-pve2
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-10
qemu-server: 5.0-12
pve-firmware: 2.0-2
libpve-common-perl: 5.0-16
libpve-guest-common-perl: 2.0-11
libpve-access-control: 5.0-5
libpve-storage-perl: 5.0-12
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.0-6
pve-qemu-kvm: 2.9.0-2
pve-container: 2.0-14
pve-firewall: 3.0-1
pve-ha-manager: 2.0-2
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.8-3
lxcfs: 2.0.7-pve2
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.9-pve16~bpo90
 
Das ist eine alte version (early 5.0) - aktuell ist 5.1. Da ist wohl das update schief gelaufen. Vermute mal, Du hast keine Subscription, und das pve-no-subscription repository nicht konfiguriert (das braucht Du). Siehe auch

https://pve.proxmox.com/wiki/Package_Repositories
 
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