Container not starting after Ubuntu upgrade

mmillner99

New Member
May 26, 2022
1
0
1
Hi all,

My Ubuntu container will no longer start after Ubuntu upgrade. I ran some informational commands after doing some searching on the error.
I rebooted proxmox and the VM's start fine. It's only this one container which will not start.

Any help would be appreciated.

lxc-start 101
lxc-start: 101: lxccontainer.c: wait_on_daemonized_start: 859 No such file or directory - Failed to receive the container state
lxc-start: 101: tools/lxc_start.c: main: 306 The container failed to start
lxc-start: 101: tools/lxc_start.c: main: 309 To get more details, run the container in foreground mode
lxc-start: 101: tools/lxc_start.c: main: 311 Additional information can be obtained by setting the --logfile and --logpriority options
----
journalctl -b | grep 101
May 26 08:55:24 proxmox kernel: Linux version 5.13.19-2-pve (build@proxmox) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP PVE 5.13.19-4 (Mon, 29 Nov 2021 12:10:09 +0100) ()
May 26 08:55:24 proxmox kernel: sched_clock: Marking stable (1101473587, 8315366)->(1120465858, -10676905)
May 26 08:55:36 proxmox pvesh[955]: Starting CT 101
May 26 08:55:36 proxmox pve-guests[956]: <root@pam> starting task UPID:proxmox:000003F0:000006D5:628F94E8:vzstart:101:root@pam:
May 26 08:55:36 proxmox pve-guests[1008]: starting CT 101: UPID:proxmox:000003F0:000006D5:628F94E8:vzstart:101:root@pam:
May 26 08:55:36 proxmox systemd[1]: Started PVE LXC Container: 101.
May 26 08:55:36 proxmox pve-guests[1008]: startup for container '101' failed
May 26 08:55:37 proxmox pvesh[955]: Starting CT 101 failed: startup for container '101' failed
May 26 08:55:37 proxmox systemd[1]: pve-container@101.service: Main process exited, code=exited, status=1/FAILURE
May 26 08:55:37 proxmox systemd[1]: pve-container@101.service: Failed with result 'exit-code'.


----------
pveversion
pve-manager/7.1-7/df5740ad (running kernel: 5.13.19-2-pve)

-----------
I'm able to mount and unmount
pct mount and umount complete without error
-------------
systemctl status lxc@101.service
lxc@101.service - LXC Container: 101
Loaded: loaded (/lib/systemd/system/lxc@.service; disabled; vendor preset: enabled)
Active: inactive (dead)
Docs: man:lxc-start
man:lxc
------------------
cat /etc/pve/lxc/101.conf
arch: amd64
cores: 2
features: nesting=1
hostname: PIhole
memory: 16384
net0: name=eth0,bridge=vmbr0,firewall=1,gw=192.168.100.2,hwaddr=0A:CB:A5:11:6D:90,ip=192.168.100.253/24,type=veth
onboot: 1
ostype: ubuntu
rootfs: local:101/vm-101-disk-0.raw,size=60G
swap: 512
unprivileged: 1
I resized the drive to make sure it wasn't disk full
----------------------
lxc-start -n 101 -F -l DEBUG -o /tmp/lxc101.log
lxc-start: 101: conf.c: run_buffer: 321 Script exited with status 255
lxc-start: 101: start.c: lxc_init: 846 Failed to run lxc.hook.pre-start for container "101"
lxc-start: 101: start.c: __lxc_start: 2002 Failed to initialize container "101"
lxc-start: 101: tools/lxc_start.c: main: 306 The container failed to start
lxc-start: 101: tools/lxc_start.c: main: 311 Additional information can be obtained by setting the --logfile and --logpriority options
 

oguz

Proxmox Staff Member
Staff member
Nov 19, 2018
5,011
633
118
hi,

thanks for the outputs and configuration file.

My Ubuntu container will no longer start after Ubuntu upgrade.
which ubuntu version did you upgrade to?

what do you get after running pct start 101 --debug ? (you can use [code][/code] tags when posting the output)
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, 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!