[SOLVED] LXC fails to start

A

avidesh

New Member
Dec 28, 2023
20
1
3
Hello, I am relatively a newbie. I have a single node proxmox setup Virtual Environment 8.2.4 on X86 with 128gb SSD
I have a frigate LXC that has been running for a while. upon proxmox restart, this LXC fails to start. When I search around I found a few commands to get a detailed debug message. I have posted it here.

Code: 
root@pve:~# pct start 104 --debug
run_buffer: 571 Script exited with status 1
lxc_init: 845 Failed to run lxc.hook.pre-start for container "104"
__lxc_start: 2034 Failed to initialize container "104"
art-hook" for container "104", config section "lxc"
DEBUG    utils - ../src/lxc/utils.c:run_buffer:560 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 104 lxc pre-start produced output: closing file '/etc/network/interfaces.tmp.4167' failed - No space left on device

DEBUG    utils - ../src/lxc/utils.c:run_buffer:560 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 104 lxc pre-start produced output: error in setup task PVE::LXC::Setup::pre_start_hook

ERROR    utils - ../src/lxc/utils.c:run_buffer:571 - Script exited with status 1
ERROR    start - ../src/lxc/start.c:lxc_init:845 - Failed to run lxc.hook.pre-start for container "104"
ERROR    start - ../src/lxc/start.c:__lxc_start:2034 - Failed to initialize container "104"
INFO     utils - ../src/lxc/utils.c:run_script_argv:587 - Executing script "/usr/share/lxcfs/lxc.reboot.hook" for container "104", config section "lxc"
startup for container '104' failed

appreciate some help in resolving this issue.
 
  • Like
Reactions: huubknops
Thanks. I freed up space. Now I see that the local-lvm has 29gb free now (45%). but the error persists, even after restarting proxmox.
 
avidesh said:
closing file '/etc/network/interfaces.tmp.4167' failed - No space left on device
Click to expand...
avidesh said:
Now I see that the local-lvm has 29gb free now (45%).
Click to expand...
Wrong "full." your CONTAINER disk is full, not the host store. you need to either increase the container disk size, OR mount the disk manually (pct mount vmid) and clear up stuff.
 
  • Like
Reactions: huubknops, avidesh and leesteken
alexskysilk said:
Wrong "full." your CONTAINER disk is full, not the host store. you need to either increase the container disk size, OR mount the disk manually (pct mount vmid) and clear up stuff.
Click to expand...
issue solved. thank you.
Learnt a few things about lvm disks and container disks sizing. also learnt a few Pct commands by using those :)
 
You must log in or register to reply here.
Top Bottom