Error: startup for container '100' failed

[jensus11]

Hi there,

I have already written in the German forum but unfortunately have not received an answer. That's why I'm trying this here now.

I installed new updates today, which went through without any problems.
But since then an LXC container has not started. Neither manually nor automatically.

When I click on the status message, the following comes up.

run_buffer: 316 Script exited with status 1
lxc_init: 816 Failed to run lxc.hook.pre-start for container "100"
__lxc_start: 2007 Failed to initialize container "100"
TASK ERROR: startup for container '100' failed

What can I do?

 

[Dunuin]

You should check the syslog. That error basically is always the same and it is impossible to tell what causes the LXC not to start.

 

[jensus11]

Ok, where can I find the syslog?

 

[Dunuin]

/var/log/syslog and /var/log/syslog.1

 

[jensus11]

The syslog can also be seen in the WebGui under the node.

Oct 11 09:54:01 proxmox systemd[1]: Started PVE LXC Container: 100.
Oct 11 09:54:02 proxmox kernel: EXT4-fs (dm-8): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
Oct 11 09:54:02 proxmox pvedaemon[681110]: startup for container '100' failed
Oct 11 09:54:02 proxmox pvedaemon[463813]: <root@pam> end task UPID:proxmox:000G6496:0180BF2C:6193EDM9:vzstart:100:root@pam: startup for container '100' failed
Oct 11 09:54:03 proxmox systemd[1]: pve-container@100.service: Main process exited, code=exited, status=1/FAILURE
Oct 11 09:54:03 proxmox systemd[1]: pve-container@100.service: Failed with result 'exit-code'.
Oct 11 09:54:03 proxmox systemd[1]: pve-container@100.service: Consumed 1.389s CPU time.

 

[jensus11]

This thread can be closed. The hard drive storage was not big enough.
No space left on device.

 

[Radomir]

@jensus11 i had the simillar issue, thanks for this reply. Can you plese tell me how did you find out that storage was a issue?

 

[mr_fusion]

For future readers: I faced this error message also, for one of my containers. Problem here was, that i edited the container config by hand:

root@pve:~# cat /etc/pve/lxc/105.conf
arch: amd64
cores: 1
features: nesting=1
hostname: testnode
memory: 2048
nameserver: 192.168.2.1
net0: name=eth0,bridge=vmbr0,gw=192.168.2.1,hwaddr=12:34:56:78:ca:fe,ip=192.168.2.5/24,type=veth
onboot: 1
ostype: debian
rootfs: local-lvm:vm-105-disk-0,size=32G
startup: order=128,up=55
swap: 4096
lxc.cgroup.devices.allow: c 189:* rwm
lxc.mount.entry: /dev/bus/usb/003/002 dev/bus/usb/003/002 none bind,optional,create=file
lxc.cgroup2.devices.allow: c 188:* rwm
lxc.mount.entry: /dev/ttyUSB0 dev/ttyUSB0 none bind,optional,create=file
root@pve:~#

And i had also added via gui device passtrough for /dev/ttyUSB0

Solution: in the gui remove /dev/ttyUSB0 and container can boot up again and also the serial device is piped to the container like expected (i had a hardware change, after that it stopped working. Before that it worked.)