[SOLVED] Debian 10.X LXC systemctl problem

[SpinningRust]

Hello everyone,

quiet some time ago i have encountered a very weird problem with Debian 10 LXC containers.
Every time i create a new LXC container, systemctl commands do not seem to work very well. What i mean by that:

systemctl restart ssh or nginx or whatever else does not give me any feedback or error; until about 10 minutes later.

as you can see in the attached screenshot, systemctl status works fine and immediately, the systemctl restart however took about 10 minutes. If i do this in a ubuntu 20.X LXC container, everything works fine and responsive as expected. I'm running PVE 6.3-3.

As i have no idea on how to start troubleshooting this, i would be very grateful for any hints.

Thanks in advance,

John

 

[oguz]

hi,

can you post the container configuration (pct config CTID) and your pveversion -v output here?

 

[SpinningRust]

hi,

can you post the container configuration (pct config CTID) and your pveversion -v output here?

Hi oguz,

thanks for the reply.



The output of pveversion -v:

proxmox-ve: 6.3-1 (running kernel: 5.4.78-2-pve)
pve-manager: 6.3-3 (running version: 6.3-3/eee5f901)
pve-kernel-5.4: 6.3-3
pve-kernel-helper: 6.3-3
pve-kernel-5.3: 6.1-6
pve-kernel-5.0: 6.0-11
pve-kernel-5.4.78-2-pve: 5.4.78-2
pve-kernel-5.4.78-1-pve: 5.4.78-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
pve-kernel-5.4.65-1-pve: 5.4.65-1
pve-kernel-5.4.60-1-pve: 5.4.60-2
pve-kernel-5.4.55-1-pve: 5.4.55-1
pve-kernel-5.4.44-2-pve: 5.4.44-2
pve-kernel-5.4.44-1-pve: 5.4.44-1
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph-fuse: 14.2.16-pve1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 3.0.0-1+pve3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.7
libproxmox-backup-qemu0: 1.0.2-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.3-2
libpve-guest-common-perl: 3.1-4
libpve-http-server-perl: 3.1-1
libpve-storage-perl: 6.3-4
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.6-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-3
pve-cluster: 6.2-1
pve-container: 3.3-2
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.1.0-8
pve-xtermjs: 4.7.0-3
pve-zsync: 2.0-4
qemu-server: 6.3-3
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.5-pve1

and the LXC CT config:

arch: amd64
cores: 1
hostname: delete
memory: 512
net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=46:EA:E1:C9:DA:51,ip=dhcp,ip6=dhcp,type=veth
ostype: debian
rootfs: local-zfs:subvol-103-disk-0,size=8G
swap: 512
unprivileged: 1

 

[oguz]

could you try to disable ipv6 dhcp and set it to static? (you can leave the address empty)

 

[SpinningRust]

could you try to disable ipv6 dhcp and set it to static? (you can leave the address empty)

I just tried that and am baffled.
For some reason, this seemed to have fixed this.
Do you have an idea why that is? It works with the same IPv6 configuration in Ubuntu and worked some time ago in Debian 10 as well, that’s why I’m so confused.

 

[oguz]

Do you have an idea why that is? It works with the same IPv6 configuration in Ubuntu and worked some time ago in Debian 10 as well, that’s why I’m so confused.

systemd is waiting for dhcp client to time out, so it considers network-related service as not started

 

[SpinningRust]

systemd is waiting for dhcp client to time out, so it considers network-related service as not started

well that makes kinda sense...

thanks for clearing that up, i'll mark the thread as solved

 

[Friarchuck]

Was having this same issue and this resolved it for me too. Thank you!

 

[gruiz]

In my case, I forgot to fill in the gateway in the proxmox network device settings for the container.