[SOLVED] pct start failed PVE4.4

[zenny]

Hi,

The pct start failed after an upgrade as follows (only has pve-no-subscription repo enabled.

# pct start 250
Job for lxc@250.service failed. See 'systemctl status lxc@250.service' and 'journalctl -xn' for details.
command 'systemctl start lxc@250' failed: exit code 1

root@lhotse:~# systemctl status lxc@250.service
● lxc@250.service - LXC Container: 250
   Loaded: loaded (/lib/systemd/system/lxc@.service; disabled)
  Drop-In: /usr/lib/systemd/system/lxc@.service.d
           └─pve-reboot.conf
   Active: failed (Result: exit-code) since Sat 2017-10-28 18:52:48 CEST; 14s ago
           └─pve-reboot.conf                                                                                                                                                                                                        [0/1234]
   Active: failed (Result: exit-code) since Sat 2017-10-28 18:52:48 CEST; 14s ago
     Docs: man:lxc-start
           man:lxc
  Process: 7819 ExecStart=/usr/bin/lxc-start -n %i (code=exited, status=1/FAILURE)

Oct 28 18:52:48 lhotse lxc-start[7819]: lxc-start: tools/lxc_start.c: main: 366 The container failed to start.
Oct 28 18:52:48 lhotse lxc-start[7819]: lxc-start: tools/lxc_start.c: main: 368 To get more details, run the container in foreground mode.
Oct 28 18:52:48 lhotse lxc-start[7819]: lxc-start: tools/lxc_start.c: main: 370 Additional information can be obtained by setting the --logfile and --logpriority options.
Oct 28 18:52:48 lhotse systemd[1]: lxc@250.service: control process exited, code=exited status=1
Oct 28 18:52:48 lhotse systemd[1]: Failed to start LXC Container: 250.
Oct 28 18:52:48 lhotse systemd[1]: Unit lxc@250.service entered failed state.

root@lhotse:~# pveversion -V
proxmox-ve: 4.4-96 (running kernel: 4.4.83-1-pve)
pve-manager: 4.4-18 (running version: 4.4-18/ef2610e8)
pve-kernel-4.4.79-1-pve: 4.4.79-95
pve-kernel-4.4.67-1-pve: 4.4.67-92
pve-kernel-4.4.83-1-pve: 4.4.83-96
pve-kernel-4.4.40-1-pve: 4.4.40-82
pve-kernel-4.4.62-1-pve: 4.4.62-88
lvm2: 2.02.116-pve3
corosync-pve: 2.4.2-2~pve4+1
libqb0: 1.0.1-1
pve-cluster: 4.0-53
qemu-server: 4.0-113
pve-firmware: 1.1-11
libpve-common-perl: 4.0-96
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-76
pve-libspice-server1: 0.12.8-2
vncterm: 1.3-2
pve-docs: 4.4-4
pve-qemu-kvm: 2.9.0-5~pve4
pve-container: 1.0-101
pve-firewall: 2.0-33
pve-ha-manager: 1.0-41
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-4
lxcfs: 2.0.6-pve1
criu: 1.6.0-1
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1~pve80
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.9-pve15~bpo80

# dpkg -l | grep base-files
ii  base-files                           8+deb8u9                           amd64        Debian base system miscellaneous files

Thus, it is not related with what has been discussed at https://forum.proxmox.com/threads/lxc-start-fails-unsupported-debian-version-9-1.35860/ and https://forum.proxmox.com/threads/d...-start-after-upgrade-to-latest-updates.35774/ as they are PVE5 related.

Thanks!

 

[zenny]

SOLVED:

root@lhotse:~# lxc-start -F -n 250  --logfile=lxc.log --logpriority=debug                                                                                                                                                                  
unable to open file '/fastboot.tmp.11088' - Disk quota exceeded
error in setup task PVE::LXC::Setup::pre_start_hook
lxc-start: conf.c: run_buffer: 405 Script exited with status 1.
lxc-start: start.c: lxc_init: 450 Failed to run lxc.hook.pre-start for container "250".
lxc-start: start.c: __lxc_start: 1321 Failed to initialize container "250".
lxc-start: tools/lxc_start.c: main: 366 The container failed to start.
lxc-start: tools/lxc_start.c: main: 370 Additional information can be obtained by setting the --logfile and --logpriority options.

Increased the disk quota for the container and the problem resolved. Posting this for future references.