hello everyone,
having some kind of issue starting a LXC, I am having trouble analyzing the logs to pinpoint exactly what is happening here ?
Any thoughts ?
Mucho Gracias in advance !
lxc-start -n 103 -F -l DEBUG -o /tmp/lxc-103.log
https://paste.ubuntu.com/p/P8sFVG2jQF/
having some kind of issue starting a LXC, I am having trouble analyzing the logs to pinpoint exactly what is happening here ?
Any thoughts ?
Mucho Gracias in advance !
Code:
root@pve:/#
root@pve:/# pveversion -v
proxmox-ve: 6.0-2 (running kernel: 5.0.18-1-pve)
pve-manager: 6.0-5 (running version: 6.0-5/f8a710d7)
pve-kernel-5.0: 6.0-6
pve-kernel-helper: 6.0-6
pve-kernel-4.15: 5.4-6
pve-kernel-5.0.18-1-pve: 5.0.18-2
pve-kernel-5.0.15-1-pve: 5.0.15-1
pve-kernel-4.15.18-18-pve: 4.15.18-44
pve-kernel-4.15.18-16-pve: 4.15.18-41
pve-kernel-4.15.18-15-pve: 4.15.18-40
pve-kernel-4.15.18-14-pve: 4.15.18-39
pve-kernel-4.15.18-13-pve: 4.15.18-37
pve-kernel-4.15.18-12-pve: 4.15.18-36
pve-kernel-4.15.18-11-pve: 4.15.18-34
ceph-fuse: 12.2.11+dfsg1-2.1
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-3
libpve-guest-common-perl: 3.0-1
libpve-http-server-perl: 3.0-2
libpve-storage-perl: 6.0-7
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-5
pve-docs: 6.0-4
pve-edk2-firmware: 2.20190614-1
pve-firewall: 4.0-6
pve-firmware: 3.0-2
pve-ha-manager: 3.0-2
pve-i18n: 2.0-2
pve-qemu-kvm: 4.0.0-5
pve-xtermjs: 3.13.2-1
qemu-server: 6.0-7
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.1-pve1
root@pve:/#
Code:
root@pve:/# pct config 103
arch: amd64
hostname: plex
memory: 2048
net0: name=eth0,bridge=vmbr0,hwaddr=32:CA:CD:69:5F:91,ip=dhcp,type=veth
onboot: 1
ostype: debian
parent: plex_base
rootfs: zfs-containers:subvol-103-disk-0,size=8G
startup: order=20
swap: 512
root@pve:/#
root@pve:/# cat /etc/pve/lxc/103.conf
arch: amd64
hostname: plex
memory: 2048
net0: name=eth0,bridge=vmbr0,hwaddr=32:CA:CD:69:5F:91,ip=dhcp,type=veth
onboot: 1
ostype: debian
parent: plex_base
rootfs: zfs-containers:subvol-103-disk-0,size=8G
startup: order=20
swap: 512
[plex_base]
arch: amd64
hostname: plex
memory: 2048
net0: name=eth0,bridge=vmbr0,hwaddr=32:CA:CD:69:5F:91,ip=dhcp,type=veth
onboot: 1
ostype: debian
rootfs: zfs-containers:subvol-103-disk-0,size=8G
snaptime: 1560612608
startup: order=20
swap: 512
root@pve:/#
Code:
root@pve:/# systemctl status pve-container@103.service
● pve-container@103.service - PVE LXC Container: 103
Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2019-08-12 11:55:09 CEST; 11min ago
Docs: man:lxc-start
man:lxc
man:pct
Process: 26905 ExecStart=/usr/bin/lxc-start -n 103 (code=exited, status=1/FAILURE)
Aug 12 11:55:07 pve systemd[1]: Starting PVE LXC Container: 103...
Aug 12 11:55:09 pve lxc-start[26905]: lxc-start: 103: lxccontainer.c: wait_on_daemonized_start: 865 Received container state "ABORTING" instead of "RUNNING"
Aug 12 11:55:09 pve lxc-start[26905]: lxc-start: 103: tools/lxc_start.c: main: 330 The container failed to start
Aug 12 11:55:09 pve lxc-start[26905]: lxc-start: 103: tools/lxc_start.c: main: 333 To get more details, run the container in foreground mode
Aug 12 11:55:09 pve lxc-start[26905]: lxc-start: 103: tools/lxc_start.c: main: 336 Additional information can be obtained by setting the --logfile and --logpriority options
Aug 12 11:55:09 pve systemd[1]: pve-container@103.service: Control process exited, code=exited, status=1/FAILURE
Aug 12 11:55:09 pve systemd[1]: pve-container@103.service: Killing process 26918 (3) with signal SIGKILL.
Aug 12 11:55:09 pve systemd[1]: pve-container@103.service: Killing process 26982 (3) with signal SIGKILL.
Aug 12 11:55:09 pve systemd[1]: pve-container@103.service: Failed with result 'exit-code'.
Aug 12 11:55:09 pve systemd[1]: Failed to start PVE LXC Container: 103.
root@pve:/#
Code:
Aug 12 12:07:56 pve systemd[1]: Starting PVE LXC Container: 103...
-- Subject: A start job for unit pve-container@103.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit pve-container@103.service has begun execution.
--
-- The job identifier is 10280.
Aug 12 12:07:57 pve audit[24043]: AVC apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="/usr/bin/lxc-start" name="lxc-103_</var/lib/lxc>
Aug 12 12:07:57 pve systemd-udevd[24029]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Aug 12 12:07:57 pve kernel: audit: type=1400 audit(1565604477.718:34): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="/usr/bin/lxc-st
Aug 12 12:07:57 pve systemd-udevd[24027]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Aug 12 12:07:57 pve systemd-udevd[24029]: Using default interface naming scheme 'v240'.
Aug 12 12:07:57 pve systemd-udevd[24027]: Using default interface naming scheme 'v240'.
Aug 12 12:07:57 pve systemd-udevd[24029]: Could not generate persistent MAC address for veth1CW9CL: No such file or directory
Aug 12 12:07:58 pve kernel: vmbr0: port 6(veth103i0) entered blocking state
Aug 12 12:07:58 pve kernel: vmbr0: port 6(veth103i0) entered disabled state
Aug 12 12:07:58 pve kernel: device veth103i0 entered promiscuous mode
Aug 12 12:07:58 pve kernel: eth0: renamed from veth1CW9CL
Aug 12 12:07:58 pve lxc-start[24021]: lxc-start: 103: lxccontainer.c: wait_on_daemonized_start: 865 Received container state "ABORTING" instead of "RUNNING"
Aug 12 12:07:58 pve lxc-start[24021]: lxc-start: 103: tools/lxc_start.c: main: 330 The container failed to start
Aug 12 12:07:58 pve lxc-start[24021]: lxc-start: 103: tools/lxc_start.c: main: 333 To get more details, run the container in foreground mode
Aug 12 12:07:58 pve lxc-start[24021]: lxc-start: 103: tools/lxc_start.c: main: 336 Additional information can be obtained by setting the --logfile and --logpriority options
Aug 12 12:07:58 pve systemd[1]: pve-container@103.service: Control process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit pve-container@103.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Aug 12 12:07:58 pve systemd[1]: pve-container@103.service: Killing process 24034 (3) with signal SIGKILL.
Aug 12 12:07:58 pve systemd[1]: pve-container@103.service: Killing process 24098 (apparmor_parser) with signal SIGKILL.
Aug 12 12:07:58 pve systemd[1]: pve-container@103.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit pve-container@103.service has entered the 'failed' state with result 'exit-code'.
Aug 12 12:07:58 pve systemd[1]: Failed to start PVE LXC Container: 103.
-- Subject: A start job for unit pve-container@103.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit pve-container@103.service has finished with a failure.
--
-- The job identifier is 10280 and the job result is failed.
Aug 12 12:07:58 pve kernel: vmbr0: port 6(veth103i0) entered disabled state
Aug 12 12:07:58 pve kernel: device veth103i0 left promiscuous mode
Aug 12 12:07:58 pve kernel: vmbr0: port 6(veth103i0) entered disabled state
lxc-start -n 103 -F -l DEBUG -o /tmp/lxc-103.log
https://paste.ubuntu.com/p/P8sFVG2jQF/