LXC Startup issue on reboot

B

Bueddy

New Member
Apr 4, 2018
4
0
1
39
Dear all,

I am new to Proxmox and I am running it at my home environment to host several internal services.
My Hardware is a Gigabyte GA-J3455N-D3H with 2x8GB RAM and an MX500 SSD. It ist performing well and starting containers works very well.
I run about 12 LXC Instances and two KVM Instances. All Instances will start at boot automatically, some have a priority to start first.

But once I reboot the Host there is one issue and another strange occurrence.

The issue is, that some containers do not start and I receive a timeout after around 90 second.
Starting the LXC via WebGUI works fine.
During the last Reboot all affected containers have some additional Mount points configured.
Example ist ID 108

The strange occurrence is, that even the containers which start normally during boot took really long to start, around 50 seconds. Starting them manually only took a few seconds.
Example is the Container ID 112.

Does somebody have an Idea why my containers do not start properly and why the automatic start takes so much time?
Hope I habe attached all relevant information below.

Thanks in advance
Manuel

root@proxmox:/var/log# grep 112 syslog
Apr 4 18:05:38 proxmox kernel: [ 0.156112] pci 0000:00:13.0: bridge window [mem 0x91300000-0x913fffff]
Apr 4 18:05:38 proxmox kernel: [ 1.274899] intel_idle: MWAIT substates: 0x11242020
Apr 4 18:05:41 proxmox kernel: [ 11.171122] vmbr0: port 1(enp3s0) entered blocking state
Apr 4 18:05:41 proxmox kernel: [ 11.171125] vmbr0: port 1(enp3s0) entered forwarding state
Apr 4 18:14:15 proxmox pvedaemon[2628]: <root@pam> starting task UPID:proxmox:00002726:0000CD28:5AC4F9D7:vncproxy:112:root@pam:
Apr 4 18:14:15 proxmox pvedaemon[10022]: starting lxc vnc proxy UPID:proxmox:00002726:0000CD28:5AC4F9D7:vncproxy:112:root@pam:
Apr 4 18:14:16 proxmox pvedaemon[2628]: <root@pam> end task UPID:proxmox:00002726:0000CD28:5AC4F9D7:vncproxy:112:root@pam: OK
Apr 4 18:20:24 proxmox pvedaemon[21523]: starting CT 112: UPID:proxmox:00005413:00015D71:5AC4FB48:vzstart:112:root@pam:
Apr 4 18:20:24 proxmox pvedaemon[2629]: <root@pam> starting task UPID:proxmox:00005413:00015D71:5AC4FB48:vzstart:112:root@pam:
Apr 4 18:20:24 proxmox systemd[1]: Starting PVE LXC Container: 112...
Apr 4 18:21:11 proxmox systemd-udevd[25671]: Could not generate persistent MAC address for veth112i0: No such file or directory
Apr 4 18:21:12 proxmox ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port veth112i0
Apr 4 18:21:12 proxmox ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named veth112i0
Apr 4 18:21:12 proxmox ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port fwln112i0
Apr 4 18:21:12 proxmox ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named fwln112i0
Apr 4 18:21:13 proxmox systemd[1]: Started PVE LXC Container: 112.
Apr 4 18:21:13 proxmox pvedaemon[2629]: <root@pam> end task UPID:proxmox:00005413:00015D71:5AC4FB48:vzstart:112:root@pam: OK
Apr 4 19:35:03 proxmox pvedaemon[8699]: shutdown CT 112: UPID:proxmox:000021FB:000832E8:5AC50CC7:vzshutdown:112:root@pam:
Apr 4 19:35:03 proxmox pvedaemon[2629]: <root@pam> starting task UPID:proxmox:000021FB:000832E8:5AC50CC7:vzshutdown:112:root@pam:
Apr 4 19:35:04 proxmox pvedaemon[2628]: unable to get PID for CT 112 (not running?)
Apr 4 19:35:04 proxmox ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port fwln112i0
Apr 4 19:35:04 proxmox ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named fwln112i0
Apr 4 19:35:04 proxmox ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port veth112i0
Apr 4 19:35:04 proxmox ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named veth112i0
Apr 4 19:35:05 proxmox pvestatd[2599]: unable to get PID for CT 112 (not running?)
Apr 4 19:35:05 proxmox pvedaemon[2629]: <root@pam> end task UPID:proxmox:000021FB:000832E8:5AC50CC7:vzshutdown:112:root@pam: OK
Apr 4 19:35:05 proxmox pvestatd[2599]: unable to get PID for CT 112 (not running?)
Apr 4 19:35:09 proxmox pvedaemon[2627]: <root@pam> starting task UPID:proxmox:0000230E:00083579:5AC50CCD:vzstart:112:root@pam:
Apr 4 19:35:09 proxmox pvedaemon[8974]: starting CT 112: UPID:proxmox:0000230E:00083579:5AC50CCD:vzstart:112:root@pam:
Apr 4 19:35:09 proxmox systemd[1]: Starting PVE LXC Container: 112...
Apr 4 19:35:12 proxmox ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port veth112i0
Apr 4 19:35:12 proxmox ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named veth112i0
Apr 4 19:35:12 proxmox ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port fwln112i0
Apr 4 19:35:12 proxmox ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named fwln112i0
Apr 4 19:35:12 proxmox systemd[1]: Started PVE LXC Container: 112.
Apr 4 19:35:12 proxmox pvedaemon[2627]: <root@pam> end task UPID:proxmox:0000230E:00083579:5AC50CCD:vzstart:112:root@pam: OK
Apr 4 19:35:13 proxmox kernel: [ 5382.565147] vmbr0v179: port 2(veth112i0) entered blocking state
Apr 4 19:35:13 proxmox kernel: [ 5382.565152] vmbr0v179: port 2(veth112i0) entered forwarding state

proxmox-ve: 5.1-42 (running kernel: 4.13.13-6-pve)
pve-manager: 5.1-46 (running version: 5.1-46/ae8241d4)
pve-kernel-4.13: 5.1-42
pve-kernel-4.13.13-6-pve: 4.13.13-42
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
openvswitch-switch: 2.7.0-2
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

Apr 4 18:06:43 proxmox pvesh[2706]: Starting CT 108
Apr 4 18:06:43 proxmox pve-guests[3483]: starting CT 108: UPID:proxmox:00000D9B:00001CCA:5AC4F813:vzstart:108:root@pam:
Apr 4 18:06:43 proxmox pve-guests[2721]: <root@pam> starting task UPID:proxmox:00000D9B:00001CCA:5AC4F813:vzstart:108:root@pam:
Apr 4 18:06:43 proxmox systemd[1]: Starting PVE LXC Container: 108...
Apr 4 18:08:13 proxmox systemd[1]: pve-container@108.service: Start operation timed out. Terminating.
Apr 4 18:08:13 proxmox systemd[1]: Failed to start PVE LXC Container: 108.
Apr 4 18:08:13 proxmox systemd[1]: pve-container@108.service: Unit entered failed state.
Apr 4 18:08:13 proxmox systemd[1]: pve-container@108.service: Failed with result 'timeout'.
Apr 4 18:08:13 proxmox pve-guests[3483]: command 'systemctl start pve-container@108' failed: exit code 1
Apr 4 18:08:14 proxmox pvesh[2706]: Starting CT 108 failed: command 'systemctl start pve-container@108' failed: exit code 1
Apr 4 18:08:15 proxmox systemd-udevd[3696]: Could not generate persistent MAC address for veth108i0: No such file or directory
Apr 4 18:08:16 proxmox ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port veth108i0
Apr 4 18:08:16 proxmox ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named veth108i0
Apr 4 18:08:16 proxmox ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port fwln108i0
Apr 4 18:08:16 proxmox ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named fwln108i0
Apr 4 18:08:16 proxmox kernel: [ 165.840647] vmbr0: port 4(veth108i0) entered blocking state
Apr 4 18:08:16 proxmox kernel: [ 165.840733] device veth108i0 entered promiscuous mode
Apr 4 18:08:16 proxmox pvestatd[2599]: unable to get PID for CT 108 (not running?)
Apr 4 18:08:16 proxmox kernel: [ 166.434609] vmbr0: port 4(veth108i0) entered disabled state
Apr 4 18:08:16 proxmox kernel: [ 166.434942] device veth108i0 left promiscuous mode
Apr 4 18:08:16 proxmox kernel: [ 166.434950] vmbr0: port 4(veth108i0) entered disabled state
Apr 4 18:08:17 proxmox ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port fwln108i0
Apr 4 18:08:17 proxmox ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named fwln108i0
Apr 4 18:08:17 proxmox ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port veth108i0
Apr 4 18:08:17 proxmox ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named veth108i0
Apr 4 18:09:00 proxmox kernel: [ 209.869108] EXT4-fs (dm-13): 13 orphan inodes deleted
Apr 4 18:14:35 proxmox pvedaemon[10075]: starting lxc vnc proxy UPID:proxmox:0000275B:0000D4D5:5AC4F9EB:vncproxy:108:root@pam:
Apr 4 18:14:35 proxmox pvedaemon[2627]: <root@pam> starting task UPID:proxmox:0000275B:0000D4D5:5AC4F9EB:vncproxy:108:root@pam:
Apr 4 18:14:35 proxmox pvedaemon[2627]: <root@pam> end task UPID:proxmox:0000275B:0000D4D5:5AC4F9EB:vncproxy:108:root@pam: OK
Apr 4 18:20:14 proxmox pvedaemon[2628]: <root@pam> starting task UPID:proxmox:00004B60:00015961:5AC4FB3E:vzstart:108:root@pam:
Apr 4 18:20:14 proxmox pvedaemon[19296]: starting CT 108: UPID:proxmox:00004B60:00015961:5AC4FB3E:vzstart:108:root@pam:
Apr 4 18:20:14 proxmox systemd[1]: Starting PVE LXC Container: 108...
Apr 4 18:20:16 proxmox ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port veth108i0
Apr 4 18:20:16 proxmox ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named veth108i0
Apr 4 18:20:16 proxmox ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port fwln108i0
Apr 4 18:20:16 proxmox ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named fwln108i0
Apr 4 18:20:17 proxmox systemd[1]: Started PVE LXC Container: 108.
Apr 4 18:20:17 proxmox pvedaemon[2628]: <root@pam> end task UPID:proxmox:00004B60:00015961:5AC4FB3E:vzstart:108:root@pam: OK


arch: amd64
cores: 1
hostname: rsyslog
memory: 256
mp0: LVM-thin:vm-108-disk-2,mp=/syslog,size=1G
nameserver: 192.168.40.2
net0: name=eth0,bridge=vmbr0,gw=192.168.40.1,hwaddr=7E:95:74:BE:F0:B5,ip=192.168.40.12/24,type=veth
onboot: 1
ostype: debian
rootfs: LVM-thin:vm-108-disk-1,size=2G
searchdomain: dtmb
startup: order=3
swap: 128

root@proxmox:~# cat /etc/pve/lxc/112.conf
arch: amd64
cores: 1
hostname: VLAN179
memory: 512
net0: name=eth0,bridge=vmbr0,gw=192.168.179.1,hwaddr=52:54:00:0B:6F:89,ip=192.168.179.250/24,tag=179,type=veth
ostype: debian
rootfs: LVM-thin:vm-112-disk-1,size=2G
swap: 512

auto lo
iface lo inet loopback

iface enp3s0 inet manual

allow-vmbr9999 enp4s0
iface enp4s0 inet manual
ovs_type OVSPort
ovs_bridge vmbr9999

auto vmbr0
iface vmbr0 inet static
address 192.168.40.254
netmask 255.255.255.0
gateway 192.168.40.1
bridge_ports enp3s0
bridge_stp off
bridge_fd 0
#LAN

auto vmbr9999
iface vmbr9999 inet manual
ovs_type OVSBridge
ovs_ports enp4s0
#WAN

auto vmbr1000
iface vmbr1000 inet manual
ovs_type OVSBridge
#DMZ
 
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