[SOLVED] Proxmox Ubuntu LXC can't be started

Sep 18, 2019
28
2
3
25
Good morning guys,
10 Minutes ago my ubuntu LXC where I use nextcloud snap died. On the webinterface the webserver from the LXC didn't anwser so I connected via SSH to the LXC and rebooted. Since that the machine is dead and can't be started.

Any ideas? Thanks for your help!

Output from Proxmox GUI Task Viewer:
Code:
()
run_buffer: 323 Script exited with status 1
lxc_init: 797 Failed to run lxc.hook.pre-start for container "112"
__lxc_start: 1896 Failed to initialize container "112"
TASK ERROR: startup for container '112' failed

lxc-start -n 112 -F -lDEBUG -o lxc-112.log
Code:
lxc-start: 112: conf.c: run_buffer: 323 Script exited with status 1
lxc-start: 112: start.c: lxc_init: 797 Failed to run lxc.hook.pre-start for container "112"
lxc-start: 112: start.c: __lxc_start: 1896 Failed to initialize container "112"
lxc-start: 112: tools/lxc_start.c: main: 308 The container failed to start
lxc-start: 112: tools/lxc_start.c: main: 314 Additional information can be obtained by setting the --logfile and --logpriority options

pveversion -v
Code:
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.4.78-2-pve: 5.4.78-2
pve-kernel-5.4.78-1-pve: 5.4.78-1
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.10-1-pve: 5.3.10-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-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.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-3
libpve-http-server-perl: 3.1-1
libpve-storage-perl: 6.3-3
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.3-pve3
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-7
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-2
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.5-pve1

After rebooting the PVE host the container still can't be started.
 
Last edited:
Sep 18, 2019
28
2
3
25
Thanks for your quick reply! Here it is:

Code:
lxc-start 112 20210112085832.260 INFO     confile - confile.c:set_config_idmaps:2055 - Read uid map: type u nsid 0 hostid 100000 range 65536
lxc-start 112 20210112085832.260 INFO     confile - confile.c:set_config_idmaps:2055 - Read uid map: type g nsid 0 hostid 100000 range 65536
lxc-start 112 20210112085832.260 INFO     lsm - lsm/lsm.c:lsm_init:29 - LSM security driver AppArmor
lxc-start 112 20210112085832.260 INFO     conf - conf.c:run_script_argv:340 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "112", config section "lxc"
lxc-start 112 20210112085832.683 DEBUG    conf - conf.c:run_buffer:312 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 112 lxc pre-start produced output: unable to open file '/fastboot.tmp.13693' - Disk quota exceeded

lxc-start 112 20210112085832.684 DEBUG    conf - conf.c:run_buffer:312 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 112 lxc pre-start produced output: error in setup task PVE::LXC::Setup::pre_start_hook

lxc-start 112 20210112085832.693 ERROR    conf - conf.c:run_buffer:323 - Script exited with status 1
lxc-start 112 20210112085832.694 ERROR    start - start.c:lxc_init:797 - Failed to run lxc.hook.pre-start for container "112"
lxc-start 112 20210112085832.694 ERROR    start - start.c:__lxc_start:1896 - Failed to initialize container "112"
lxc-start 112 20210112085832.694 INFO     conf - conf.c:run_script_argv:340 - Executing script "/usr/share/lxcfs/lxc.reboot.hook" for container "112", config section "lxc"
lxc-start 112 20210112085833.195 INFO     conf - conf.c:run_script_argv:340 - Executing script "/usr/share/lxc/hooks/lxc-pve-poststop-hook" for container "112", config section "lxc"
lxc-start 112 20210112085833.617 ERROR    lxc_start - tools/lxc_start.c:main:308 - The container failed to start
lxc-start 112 20210112085833.617 ERROR    lxc_start - tools/lxc_start.c:main:314 - Additional information can be obtained by setting the --logfile and --logpriority options
lxc-start 112 20210112085911.108 INFO     confile - confile.c:set_config_idmaps:2055 - Read uid map: type u nsid 0 hostid 100000 range 65536
lxc-start 112 20210112085911.108 INFO     confile - confile.c:set_config_idmaps:2055 - Read uid map: type g nsid 0 hostid 100000 range 65536
lxc-start 112 20210112085911.109 INFO     lsm - lsm/lsm.c:lsm_init:29 - LSM security driver AppArmor
lxc-start 112 20210112085911.109 INFO     conf - conf.c:run_script_argv:340 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "112", config section "lxc"
lxc-start 112 20210112085911.543 DEBUG    conf - conf.c:run_buffer:312 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 112 lxc pre-start produced output: unable to open file '/fastboot.tmp.14113' - Disk quota exceeded

lxc-start 112 20210112085911.545 DEBUG    conf - conf.c:run_buffer:312 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 112 lxc pre-start produced output: error in setup task PVE::LXC::Setup::pre_start_hook

lxc-start 112 20210112085911.554 ERROR    conf - conf.c:run_buffer:323 - Script exited with status 1
lxc-start 112 20210112085911.554 ERROR    start - start.c:lxc_init:797 - Failed to run lxc.hook.pre-start for container "112"
lxc-start 112 20210112085911.554 ERROR    start - start.c:__lxc_start:1896 - Failed to initialize container "112"
lxc-start 112 20210112085911.554 INFO     conf - conf.c:run_script_argv:340 - Executing script "/usr/share/lxcfs/lxc.reboot.hook" for container "112", config section "lxc"
lxc-start 112 20210112085912.566 INFO     conf - conf.c:run_script_argv:340 - Executing script "/usr/share/lxc/hooks/lxc-pve-poststop-hook" for container "112", config section "lxc"
lxc-start 112 20210112085912.473 ERROR    lxc_start - tools/lxc_start.c:main:308 - The container failed to start
lxc-start 112 20210112085912.473 ERROR    lxc_start - tools/lxc_start.c:main:314 - Additional information can be obtained by setting the --logfile and --logpriority options
 
Sep 18, 2019
28
2
3
25
OMG :D
Yesterday at night I started the preview generator job for nextcloud... And it filled up the disk which is written in the log Disk quota exceeded.
My new motto is RTFL instead of RTFM :D
Thank you, LXC is up and running after resizing the disk.
 
  • Like
Reactions: oguz

oguz

Proxmox Staff Member
Staff member
Nov 19, 2018
2,963
334
88
great! please mark the thread as [SOLVED] :)
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

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 your own in 60 seconds.

Buy now!