Failed to start container after reboot

R

rinaldojonathan

Active Member
Nov 28, 2016
5
0
41
27
I've also tried to reboot the host, with no success.

root@s98242:~# lxc-start -lDEBUG -o log100 -F -n 100
input too long - aborting
error in setup task PVE::LXC::Setup::pre_start_hook
lxc-start: conf.c: run_buffer: 347 Script exited with status 1
lxc-start: start.c: lxc_init: 465 failed to run pre-start hooks for container '100'.
lxc-start: start.c: __lxc_start: 1313 failed to initialize the container
lxc-start: tools/lxc_start.c: main: 344 The container failed to start.
lxc-start: tools/lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options.

I've tried everything I could imagine, including backing it up and restoring back, chrooting it and exit, and no success.
2 containers are dead with exact same pre_start_hook. But one other container created with exact same template still working!
 
The error message indicates that a config file is too large (>32K). How large are you container config files?

# ls -l /etc/pve/lxc/
 
dietmar said:
The error message indicates that a config file is too large (>32K). How large are you container config files?

# ls -l /etc/pve/lxc/
Click to expand...
root@s98242:/etc/pve/lxc# ls -l /etc/pve/lxc/
total 2
-rw-r--r-- 1 root www-data 278 Nov 27 21:56 100.conf
-rw-r--r-- 1 root www-data 248 Nov 27 22:03 101.conf
-rw-r--r-- 1 root www-data 254 Nov 23 23:31 102.conf
-rw-r--r-- 1 root www-data 228 Nov 27 23:28 200.conf

:(
 
just to add, ID 200 were created to test if I can boot if I moved the disk image from 100 to 200.

it didn't work.

100.conf :
arch: amd64
cpulimit: 20
cpuunits: 1024
hostname: s1-db
memory: 20480
mp0: /mnt/cache,mp=/mnt/cache
net0: name=eth0,bridge=vmbr1,gw=198.204.224.153,hwaddr=92:B5:ED:F1:CB:0C,ip=aaa.bbb.ccc.ddd/29,type=veth
ostype: ubuntu
rootfs: local:100/vm-100-disk-1.raw,size=100G
swap: 1024

101.conf :
arch: amd64
cpulimit: 20
cpuunits: 1024
hostname: s2-mp3
memory: 20480
net0: name=eth0,bridge=vmbr1,gw=198.204.224.153,hwaddr=26:E9:8D:B1:93:D7,ip=aaa.bbb.ccc.ddd/29,type=veth
ostype: ubuntu
rootfs: local:101/vm-101-disk-1.raw,size=50G
swap: 1024

IP were censored for obvious reason.
 
Last edited:
So maybe its a config file inside the CT. Maybe a large /etc/hosts or /etc/network/interfaces file inside the container?
 
dietmar said:
So maybe its a config file inside the CT. Maybe a large /etc/hosts or /etc/network/interfaces file inside the container?
Click to expand...

confirmed, the /etc/hosts causes the trouble.
I just mounted my image, reverted every changes that I made, then unmount, start, then it all worked correctly.

Thanks a bunch man!
 
You must log in or register to reply here.
Top Bottom