Hello,
i´ve a strange error. After a resize of an container (changing memory and cpu) it won't start.
I got the following errors:
Proxmox Gui:
Debugging:
After migration to another host:
After migration to the 3th. host:
Strange is: in the last log, I wasn't able to start the container until I tried a boot within the gui. As you can see I always got the error: "No container config specified"
What is to do?
Storage is a NFS on a QNAP.
Best regards
i´ve a strange error. After a resize of an container (changing memory and cpu) it won't start.
I got the following errors:
Proxmox Gui:
Code:
()
Task viewer: CT 250 - Start
OutputStatus
Stop
Job for pve-container@250.service failed because the control process exited with error code.
See "systemctl status pve-container@250.service" and "journalctl -xe" for details.
TASK ERROR: command 'systemctl start pve-container@250' failed: exit code 1Debugging:
Code:
~# lxc-start -n 250 -F -l DEBUG -o /tmp/lxc-ID.log
lxc-start: 250: cgroups/cgfsng.c: create_path_for_hierarchy: 1752 Path "/sys/fs/ cgroup/hugetlb//lxc/250" already existed.
lxc-start: 250: cgroups/cgfsng.c: cgfsng_create: 1862 Failed to create cgroup "/ sys/fs/cgroup/hugetlb//lxc/250"
lxc-start: 250: cgroups/cgfsng.c: create_path_for_hierarchy: 1752 Path "/sys/fs/ cgroup/hugetlb//lxc/250-1" already existed.
lxc-start: 250: cgroups/cgfsng.c: cgfsng_create: 1862 Failed to create cgroup "/ sys/fs/cgroup/hugetlb//lxc/250-1"
lxc-start: 250: cgroups/cgfsng.c: create_path_for_hierarchy: 1752 Path "/sys/fs/ cgroup/hugetlb//lxc/250-2" already existed.
lxc-start: 250: cgroups/cgfsng.c: cgfsng_create: 1862 Failed to create cgroup "/ sys/fs/cgroup/hugetlb//lxc/250-2"
lxc-start: 250: conf.c: lxc_setup_ttys: 877 No such file or directory - Failed t o create "/dev/lxc/tty1"
lxc-start: 250: conf.c: lxc_create_ttys: 1065 Failed to setup ttys
lxc-start: 250: start.c: do_start: 1198 Failed to setup container "250"
lxc-start: 250: sync.c: __sync_wait: 57 An error occurred in another process (ex pected sequence number 5)
lxc-start: 250: start.c: __lxc_start: 1883 Failed to spawn container "250"
The container failed to start.
Additional information can be obtained by setting the --logfile and --logpriorit y options.After migration to another host:
Code:
lxc-start -n 250 -F -l DEBUG -o /tmp/lxc-ID.log
lxc-start: 250: conf.c: lxc_setup_ttys: 877 No such file or directory - Failed to create "/dev/lxc/tty1"
lxc-start: 250: conf.c: lxc_create_ttys: 1065 Failed to setup ttys
lxc-start: 250: start.c: do_start: 1198 Failed to setup container "250"
lxc-start: 250: sync.c: __sync_wait: 57 An error occurred in another process (expected sequence number 5)
lxc-start: 250: start.c: __lxc_start: 1883 Failed to spawn container "250"
The container failed to start.
Additional information can be obtained by setting the --logfile and --logpriority options.After migration to the 3th. host:
Code:
root@host:~# lxc-start -n 250 -F -l DEBUG -o /tmp/lxc-ID.log
No container config specified
root@host:~# lxc-start -n 250 -F -l DEBUG -o /tmp/lxc-ID.log
No container config specified
root@host:~# lxc-start -n 250 -F -l DEBUG -o /tmp/lxc-ID.log
No container config specified
root@host:~# lxc-start -n 250 -F -l DEBUG -o /tmp/lxc-ID.log
No container config specified
root@host:~# lxc-start -n 250 -F -l DEBUG -o /tmp/lxc-ID.log
lxc-start: 250: cgroups/cgfsng.c: create_path_for_hierarchy: 1752 Path "/sys/fs/cgroup/hugetlb//lxc/250" already existed.
lxc-start: 250: cgroups/cgfsng.c: cgfsng_create: 1862 Failed to create cgroup "/sys/fs/cgroup/hugetlb//lxc/250"
lxc-start: 250: conf.c: lxc_setup_ttys: 877 No such file or directory - Failed to create "/dev/lxc/tty1"
lxc-start: 250: conf.c: lxc_create_ttys: 1065 Failed to setup ttys
lxc-start: 250: start.c: do_start: 1198 Failed to setup container "250"
lxc-start: 250: sync.c: __sync_wait: 57 An error occurred in another process (expected sequence number 5)
lxc-start: 250: start.c: __lxc_start: 1883 Failed to spawn container "250"
The container failed to start.
Additional information can be obtained by setting the --logfile and --logpriority options.Strange is: in the last log, I wasn't able to start the container until I tried a boot within the gui. As you can see I always got the error: "No container config specified"
What is to do?
Storage is a NFS on a QNAP.
Best regards
Code:
pveversion -v
proxmox-ve: 5.2-2 (running kernel: 4.15.17-3-pve)
pve-manager: 5.2-3 (running version: 5.2-3/785ba980)
pve-kernel-4.15: 5.2-3
pve-kernel-4.15.17-3-pve: 4.15.17-13
pve-kernel-4.4.98-3-pve: 4.4.98-103
pve-kernel-4.4.83-1-pve: 4.4.83-96
pve-kernel-4.4.76-1-pve: 4.4.76-94
pve-kernel-4.4.67-1-pve: 4.4.67-92
pve-kernel-4.4.62-1-pve: 4.4.62-88
pve-kernel-4.4.35-1-pve: 4.4.35-77
corosync: 2.4.2-pve5
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-apiclient-perl: 2.0-4
libpve-common-perl: 5.0-34
libpve-guest-common-perl: 2.0-17
libpve-http-server-perl: 2.0-9
libpve-storage-perl: 5.0-23
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.0-3
lxcfs: 3.0.0-1
novnc-pve: 1.0.0-1
proxmox-widget-toolkit: 1.0-19
pve-cluster: 5.0-27
pve-container: 2.0-23
pve-docs: 5.2-4
pve-firewall: 3.0-12
pve-firmware: 2.0-4
pve-ha-manager: 2.0-5
pve-i18n: 1.0-6
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.1-5
pve-xtermjs: 1.0-5
qemu-server: 5.0-29
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.9-pve1~bpo9