[SOLVED] Can't start LXC-Container Sloww

D

djsami

Renowned Member
Aug 24, 2009
193
5
83
Hello

It opens very slowly, I don't understand why 100 pieces, for example, it takes 3 to 4 hours to open


Code: 
proxmox-ve: 6.4-1 (running kernel: 5.4.106-1-pve)
pve-manager: 6.4-6 (running version: 6.4-6/be2fa32c)
pve-kernel-5.4: 6.4-2
pve-kernel-helper: 6.4-2
pve-kernel-5.4.114-1-pve: 5.4.114-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
pve-kernel-5.4.101-1-pve: 5.4.101-1
pve-kernel-5.4.98-1-pve: 5.4.98-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.2-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.1.0
libproxmox-backup-qemu0: 1.0.3-1
libpve-access-control: 6.4-1
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.4-3
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.2-2
libpve-storage-perl: 6.4-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.1.6-2
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.5-4
pve-cluster: 6.4-1
pve-container: 3.3-5
pve-docs: 6.4-2
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.2-3
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-6
pve-xtermjs: 4.7.0-3
qemu-server: 6.4-2
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.4-pve1

Code: 
root@server3:/tmp# lxc-start -n 106 -F -l DEBUG -o /tmp/lxc-106.log

lxc-start: 106: utils.c: __safe_mount_beneath_at: 1106 Function not implemented - Failed to open 54(dev)

                                                                                                        lxc-start: 106: utils.c: __safe_mount_beneath_at: 1106 Function not implemented - Failed to open 57(full)

                                                                                                                                                                                                                 lxc-start: 106: utils.c: __safe_mount_beneath_at: 1106 Function not implemented - Failed to open 57(null)

                                 lxc-start: 106: utils.c: __safe_mount_beneath_at: 1106 Function not implemented - Failed to open 57(random)

                                                                                                                                            lxc-start: 106: utils.c: __safe_mount_beneath_at: 1106 Function not implemented - Failed to open 57(tty)

                                                                                                                                                                                                                                                    lxc-start: 106: utils.c: __safe_mount_beneath_at: 1106 Function not implemented - Failed to open 57(urandom)

                                                                       lxc-start: 106: utils.c: __safe_mount_beneath_at: 1106 Function not implemented - Failed to open 57(zero)

                                                                                                                                                                                systemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN)

Detected virtualization lxc.

Detected architecture x86-64.



Welcome to CentOS Linux 7 (Core)!



Set hostname to <195.85.70.5>.

Failed to read AF_UNIX datagram queue length, ignoring: No such file or directory

Failed to install release agent, ignoring: No such file or directory

Cannot add dependency job for unit display-manager.service, ignoring: Unit not found.

[  OK  ] Created slice Root Slice.

[  OK  ] Listening on Journal Socket.

[  OK  ] Reached target Local Encrypted Volumes.

Failed to reset devices.list on /system.slice: Operation not permitted

[  OK  ] Created slice System Slice.

[  OK  ] Listening on Delayed Shutdown Socket.

Failed to reset devices.list on /system.slice/dev-mqueue.mount: Operation not permitted

         Mounting POSIX Message Queue File System...

Failed to reset devices.list on /system.slice/system-container\x2dgetty.slice: Operation not permitted

[  OK  ] Created slice system-container\x2dgetty.slice.

[  OK  ] Started Dispatch Password Requests to Console Directory Watch.

Failed to reset devices.list on /system.slice/system-selinux\x2dpolicy\x2dmigrate\x2dlocal\x2dchanges.slice: Operation not permitted

[  OK  ] Created slice system-selinux\x2dpolicy\x2dmigrate\x2dlocal\x2dchanges.slice.

[  OK  ] Reached target Swap.

Failed to reset devices.list on /system.slice/rhel-domainname.service: Operation not permitted

         Starting Read and set NIS domainname from /etc/sysconfig/network...

Failed to reset devices.list on /system.slice/dev-hugepages.mount: Operation not permitted

         Mounting Huge Pages File System...

Failed to reset devices.list on /system.slice/systemd-tmpfiles-setup-dev.service: Operation not permitted

         Starting Create Static Device Nodes in /dev...

Failed to reset devices.list on /system.slice/rhel-readonly.service: Operation not permitted

         Starting Configure read-only root support...

[  OK  ] Reached target Remote File Systems.

[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.

MESSAGE=Failed to check directory /sys/kernel/debug: Permission denied

Failed to reset devices.list on /system.slice/sys-kernel-debug.mount: Operation not permitted

         Mounting Debug File System...

[  OK  ] Started Forward Password Requests to Wall Directory Watch.

[  OK  ] Reached target Paths.

Failed to reset devices.list on /system.slice/systemd-journald.service: Operation not permitted

         Starting Journal Service...

Failed to reset devices.list on /system.slice/sys-kernel-config.mount: Operation not permitted

         Mounting Configuration File System...

Failed to reset devices.list on /user.slice: Operation not permitted

[  OK  ] Created slice User and Session Slice.

[  OK  ] Reached target Slices.

Failed to reset devices.list on /system.slice/dev-zero.mount: Operation not permitted

Failed to reset devices.list on /system.slice/dev-full.mount: Operation not permitted

Failed to reset devices.list on /system.slice/proc-diskstats.mount: Operation not permitted

Failed to reset devices.list on /system.slice/dev-tty2.mount: Operation not permitted

Failed to reset devices.list on /system.slice/-.mount: Operation not permitted

Failed to reset devices.list on /system.slice/sys-devices-virtual-net.mount: Operation not permitted

Failed to reset devices.list on /system.slice/proc-sys-net.mount: Operation not permitted

Failed to reset devices.list on /system.slice/proc-stat.mount: Operation not permitted

Failed to reset devices.list on /system.slice/proc-sys-kernel-random-boot_id.mount: Operation not permitted

Failed to reset devices.list on /system.slice/dev-ptmx.mount: Operation not permitted

Failed to reset devices.list on /system.slice/sys-fs-fuse-connections.mount: Operation not permitted

Failed to reset devices.list on /system.slice/proc-cpuinfo.mount: Operation not permitted

Failed to reset devices.list on /system.slice/proc-meminfo.mount: Operation not permitted

Failed to reset devices.list on /system.slice/dev-random.mount: Operation not permitted

Failed to reset devices.list on /system.slice/proc-swaps.mount: Operation not permitted

Failed to reset devices.list on /system.slice/sys-devices-system-cpu-online.mount: Operation not permitted

Failed to reset devices.list on /system.slice/proc-sysrq\x2dtrigger.mount: Operation not permitted

Failed to reset devices.list on /system.slice/dev-null.mount: Operation not permitted

Failed to reset devices.list on /system.slice/proc-uptime.mount: Operation not permitted

Failed to reset devices.list on /system.slice/proc-loadavg.mount: Operation not permitted

Failed to reset devices.list on /system.slice/dev-urandom.mount: Operation not permitted

Failed to reset devices.list on /system.slice/dev-tty.mount: Operation not permitted

Failed to reset devices.list on /system.slice/dev-tty1.mount: Operation not permitted

[  OK  ] Mounted POSIX Message Queue File System.

sys-kernel-debug.mount mount process exited, code=exited status=32

[FAILED] Failed to mount Debug File System.

See 'systemctl status sys-kernel-debug.mount' for details.

Unit sys-kernel-debug.mount entered failed state.

sys-kernel-config.mount mount process exited, code=exited status=32

[FAILED] Failed to mount Configuration File System.

See 'systemctl status sys-kernel-config.mount' for details.

Unit sys-kernel-config.mount entered failed state.

dev-hugepages.mount mount process exited, code=exited status=32

[FAILED] Failed to mount Huge Pages File System.

See 'systemctl status dev-hugepages.mount' for details.

Unit dev-hugepages.mount entered failed state.

[  OK  ] Started Journal Service.

         Starting Flush Journal to Persistent Storage...

[  OK  ] Started Read and set NIS domainname from /etc/sysconfig/network.

[  OK  ] Started Create Static Device Nodes in /dev.

[  OK  ] Reached target Local File Systems (Pre).

[  OK  ] Started Configure read-only root support.

[  OK  ] Reached target Local File Systems.

         Starting Load/Save Random Seed...

[  OK  ] Started Flush Journal to Persistent Storage.

         Starting Create Volatile Files and Directories...

[  OK  ] Started Load/Save Random Seed.

[  OK  ] Started Create Volatile Files and Directories.

         Starting Update UTMP about System Boot/Shutdown...

[  OK  ] Started Update UTMP about System Boot/Shutdown.

[  OK  ] Reached target System Initialization.

[  OK  ] Listening on D-Bus System Message Bus Socket.

[  OK  ] Started Daily Cleanup of Temporary Directories.

[  OK  ] Reached target Timers.

         Starting Repair CP Socket.

[  OK  ] Listening on Repair CP Socket.

[  OK  ] Reached target Sockets.

[  OK  ] Reached target Basic System.

         Starting Permit User Sessions...

[  OK  ] Started D-Bus System Message Bus.

         Starting Generate rndc key for BIND (DNS)...

         Starting Login Service...

         Starting LSB: Bring up/down networking...

[  OK  ] Started Permit User Sessions.

[  OK  ] Started Command Scheduler.

[  OK  ] Started Console Getty.

[  OK  ] Started Container Getty on /dev/tty1.

[  OK  ] Started Container Getty on /dev/tty2.

[  OK  ] Reached target Login Prompts.

[  OK  ] Started Login Service.

[  OK  ] Started Generate rndc key for BIND (DNS).

[  OK  ] Started LSB: Bring up/down networking.

[  OK  ] Reached target Network.

         Starting Startup script for Plesk control panel server...

         Starting OpenSSH server daemon...

[  OK  ] Started Plesk mail filter service for Postfix.

         Starting MariaDB 10.5.9 database server...

         Starting Postfix Mail Transport Agent...

         Starting The PHP 7.3.28 FastCGI Process Manager...

         Starting Berkeley Internet Name Domain (DNS)...

         Starting Startup script for Panel sw-engine...

         Starting Xinetd A Powerful Replacement For Inetd...

[  OK  ] Reached target Network is Online.

         Starting System Logging Service...

[  OK  ] Started Dovecot IMAP/POP3 email server.

[  OK  ] Started System Logging Service.

[  OK  ] Started OpenSSH server daemon.

[  OK  ] Started Startup script for Plesk control panel server.

[  OK  ] Started The PHP 7.3.28 FastCGI Process Manager.

[  OK  ] Started Berkeley Internet Name Domain (DNS).

[  OK  ] Reached target Host and Network Name Lookups.

         Starting The Apache HTTP Server...

[  OK  ] Started Startup script for Panel sw-engine.



CentOS Linux 7 (Core)

Kernel 5.4.106-1-pve on an x86_64



195 login:


I can't find what's wrong[/ICODE]
 
Last edited:
hi,

it seems you didn't post the log (which is generated when you run this command lxc-start -n 106 -F -l DEBUG -o /tmp/lxc-106.log the file /tmp/lxc-106.log is what is needed).


two things:

* you've upgraded the kernel without reboot, please reboot your host first (pve-kernel running 5.4.106-1-pve but pve-kernel-5.4.114-1-pve is installed.

* after rebooting, start the container with pct start CTID --debug and post the output on the screen here (in [code] tags. this is the same as that missing log from earlier)

EDIT: please also post the container configuration pct config CTID
 
Last edited:
  • Like
Reactions: djsami
oguz said:
hi,

it seems you didn't post the log (which is generated when you run this command lxc-start -n 106 -F -l DEBUG -o /tmp/lxc-106.log the file /tmp/lxc-106.log is what is needed).


two things:

* you've upgraded the kernel without reboot, please reboot your host first (pve-kernel running 5.4.106-1-pve but pve-kernel-5.4.114-1-pve is installed.

* after rebooting, start the container with pct start CTID --debug and post the output on the screen here (in [code] tags. this is the same as that missing log from earlier)

EDIT: please also post the container configuration pct config CTID
Click to expand...


Code: 
proxmox-ve: 6.4-1 (running kernel: 5.4.114-1-pve)
pve-manager: 6.4-6 (running version: 6.4-6/be2fa32c)
pve-kernel-5.4: 6.4-2
pve-kernel-helper: 6.4-2
pve-kernel-5.4.114-1-pve: 5.4.114-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
pve-kernel-5.4.101-1-pve: 5.4.101-1
pve-kernel-5.4.98-1-pve: 5.4.98-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.2-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.1.0
libproxmox-backup-qemu0: 1.0.3-1
libpve-access-control: 6.4-1
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.4-3
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.2-2
libpve-storage-perl: 6.4-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.1.6-2
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.5-4
pve-cluster: 6.4-1
pve-container: 3.3-5
pve-docs: 6.4-2
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.2-3
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-6
pve-xtermjs: 4.7.0-3
qemu-server: 6.4-2
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.4-pve1

Code: 
root@server3:/tmp# pct config 106
arch: amd64
cores: 1
hostname: 195.85.70.5
memory: 2048
nameserver: 8.8.4.4 8.8.8.8
net0: name=eth0,bridge=vmbr0,gw=195.85.70.1,hwaddr=DA:19:79:F0:A7:5D,ip=195.85.70.5/24,ip6=auto,type=veth
onboot: 0
ostype: centos
rootfs: NVMe-Disk:vm-106-disk-0,size=20G
swap: 2048
unprivileged: 1
root@server3:/tmp#


Thansk.
 

Attachments

Last edited:
djsami said:
It opens very slowly, I don't understand why 100 pieces, for example, it takes 3 to 4 hours to open
Click to expand...
maybe networking takes long to setup?

this line in the config:
Code: 
net0: name=eth0,bridge=vmbr0,gw=195.85.70.1,hwaddr=DA:19:79:F0:A7:5D,ip=195.85.70.5/24,ip6=auto,type=veth

can you try deleting the part ip6=auto, (or in Network tab of container settings, set the IPv6 to static and leave it with empty values)

afterwards restart the container with pct reboot CTID and see if problem persists.
 
  • Like
Reactions: djsami
oguz said:
maybe networking takes long to setup?

this line in the config:
Code: 
net0: name=eth0,bridge=vmbr0,gw=195.85.70.1,hwaddr=DA:19:79:F0:A7:5D,ip=195.85.70.5/24,ip6=auto,type=veth

can you try deleting the part ip6=auto, (or in Network tab of container settings, set the IPv6 to static and leave it with empty values)

afterwards restart the container with pct reboot CTID and see if problem persists.
Click to expand...


Code: 
arch: amd64
cores: 1
hostname: 195.85.70.5
memory: 2048
nameserver: 8.8.4.4 8.8.8.8
net0: name=eth0,bridge=vmbr0,gw=195.85.70.1,hwaddr=DA:19:79:F0:A7:5D,ip=195.85.70.5/24,type=veth
onboot: 0
ostype: centos
rootfs: NVMe-Disk:vm-106-disk-0,size=20G
swap: 2048
unprivileged: 1

???
 
djsami said:
Code: 
arch: amd64
cores: 1
hostname: 195.85.70.5
memory: 2048
nameserver: 8.8.4.4 8.8.8.8
net0: name=eth0,bridge=vmbr0,gw=195.85.70.1,hwaddr=DA:19:79:F0:A7:5D,ip=195.85.70.5/24,type=veth
onboot: 0
ostype: centos
rootfs: NVMe-Disk:vm-106-disk-0,size=20G
swap: 2048
unprivileged: 1

???
Click to expand...
yes looks okay, you can reboot the container and see if it makes a difference
 
  • Like
Reactions: djsami
oguz said:
yes looks okay, you can reboot the container and see if it makes a difference
Click to expand...
yes 8 10 seconds started to open

thansk.

/etc/pve/nodes/server3/lxc

notpedd ++ ,ip6=auto ctrl +h remove ?

I say okay if I do
 
this happens because you don't have IPv6 network setup (dhcp server etc.), and your container is waiting for network config.

djsami said:
yes 8 10 seconds started to open

thansk.
Click to expand...
great. please mark the thread [SOLVED] (top right "Edit Thread" and then select the Prefix) so others know what to expect :)

djsami said:
/etc/pve/nodes/server3/lxc

notpedd ++ ,ip6=auto ctrl +h remove ?

I say okay if I do
Click to expand...
that would remove it from all the containers, but if you do this incorrectly then you might cause issue on your containers (if you edit incorrect). so i wouldn't recommend mass-editing the configurations like that.

you can also do this change through the GUI as i pointed out before
 
  • Like
Reactions: djsami
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