[SOLVED] CT Fails start "Error: startup for container '102' failed"

[guff666]

I have an LXC CT that's failing to start and I can't see how to debug why. The journal (see below) indicates that it starts but then fails to run it's startup script. The container does mount an NFS filesystem on another server, but it's not critical and shouldn't cause a failure to boot.

Is there any way to access the underlying vm-102-disk-0 so I can interrogate the syslog?

Gareth
PS It's not the end of the world if I need to recreate the CT, but I'd like to know why it's barfing.

===
The config is:

arch: amd64
cores: 1
features: mount=nfs
hostname: cfg-backup
memory: 512
net0: name=eth0,bridge=vmbr0,firewall=1,gw=172.29.12.1,hwaddr=02:2E:FB:1D:BB:F5,ip=172.29.12.20/24,type=veth
onboot: 1
ostype: debian
rootfs: local-lvm:vm-102-disk-0,size=8G
swap: 512

Starting this causes the following error:

run_buffer: 321 Script exited with status 1
lxc_init: 846 Failed to run lxc.hook.pre-start for container "102"
__lxc_start: 2002 Failed to initialize container "102"
TASK ERROR: startup for container '102' failed

journalctl -xe shows:

Aug 01 11:37:49 pve14 pvedaemon[12397]: starting CT 102: UPID:pve14:0000306D:00049E5F:>
Aug 01 11:37:49 pve14 pvedaemon[2079]: <root@pam> starting task UPID:pve14:0000306D:00>
Aug 01 11:37:49 pve14 systemd[1]: Started PVE LXC Container: 102.
░░ Subject: A start job for unit pve-container@102.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pve-container@102.service has finished successfully.
░░
░░ The job identifier is 783.
Aug 01 11:37:50 pve14 kernel: EXT4-fs (dm-12): mounted filesystem with ordered data mo>
Aug 01 11:37:51 pve14 pvedaemon[2080]: unable to get PID for CT 102 (not running?)
Aug 01 11:37:51 pve14 pvedaemon[12397]: startup for container '102' failed
Aug 01 11:37:51 pve14 pvedaemon[2081]: unable to get PID for CT 102 (not running?)
Aug 01 11:37:51 pve14 pvedaemon[2079]: <root@pam> end task UPID:pve14:0000306D:00049E5>
Aug 01 11:37:52 pve14 systemd[1]: pve-container@102.service: Main process exited, code>
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit pve-container@102.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Aug 01 11:37:52 pve14 systemd[1]: pve-container@102.service: Failed with result 'exit->
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pve-container@102.service has entered the 'failed' state with result 'exit>
Aug 01 11:37:52 pve14 systemd[1]: pve-container@102.service: Consumed 1.063s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pve-container@102.service completed and consumed the indicated resources.

 

[guff666]

I solved it myself. The root disk had run out of space.