Error: command 'systemctl start pve-container@114' failed: exit code 1

[Fathi]

Hello,
Yesterday, I updated my proxmox test server via apt-get dist-upgrade and rebooted. After what, none of the containers starts.

From cli, I tried to start one in foreground and this is what i got:
root@pve-10-101:~# /usr/bin/lxc-start -n 114 -F -lDEBUG -o /dev/shm/err.log --logpriority TRACE
lxc-start: 114: lxccontainer.c: do_lxcapi_start: 984 Permission denied - Failed to make / rslave at startup
lxc-start: 114: tools/lxc_start.c: main: 371 The container failed to start.
lxc-start: 114: tools/lxc_start.c: main: 375 Additional information can be obtained by setting the --logfile and --logpriority options.
root@pve-10-101:~# cat /dev/shm/err.log
lxc-start 114 20180329091937.592 INFO lxc_start_ui - tools/lxc_start.c:main:280 - using rcfile /var/lib/lxc/114/config
lxc-start 114 20180329091937.592 INFO lxc_confile - confile.c:set_config_idmaps:1556 - Read uid map: type u nsid 0 hostid 100000 range 65536
lxc-start 114 20180329091937.592 INFO lxc_confile - confile.c:set_config_idmaps:1556 - Read uid map: type g nsid 0 hostid 100000 range 65536
lxc-start 114 20180329091937.592 TRACE lxc_commands - commands.c:lxc_cmd:290 - command get_init_pid tries to connect command socket
lxc-start 114 20180329091937.592 TRACE lxc_commands - commands.c:lxc_cmd:295 - command get_init_pid failed to connect command socket: Connection refused
lxc-start 114 20180329091937.592 TRACE lxc_commands - commands.c:lxc_cmd:290 - command get_cgroup tries to connect command socket
lxc-start 114 20180329091937.592 TRACE lxc_commands - commands.c:lxc_cmd:295 - command get_cgroup failed to connect command socket: Connection refused
lxc-start 114 20180329091937.592 TRACE lxc_commands - commands.c:do_lxc_cmd_get_cgroup_path:439 - command get_cgroup failed for container "114": Connection refused.
lxc-start 114 20180329091937.592 TRACE lxc_commands - commands.c:lxc_cmd:290 - command get_state tries to connect command socket
lxc-start 114 20180329091937.592 TRACE lxc_commands - commands.c:lxc_cmd:295 - command get_state failed to connect command socket: Connection refused
lxc-start 114 20180329091937.592 TRACE lxc_start - start.c:lxc_init_handler:592 - unix domain socket 4 for command server is ready
lxc-start 114 20180329091937.592 ERROR lxc_container - lxccontainer.c:do_lxcapi_start:984 - Permission denied - Failed to make / rslave at startup
lxc-start 114 20180329091937.593 ERROR lxc_start_ui - tools/lxc_start.c:main:371 - The container failed to start.
lxc-start 114 20180329091937.593 ERROR lxc_start_ui - tools/lxc_start.c:main:375 - Additional information can be obtained by setting the --logfile and --logpriority options.

Can someone tell me how to fix this ?
TIA

 

[tom]

please also post your:

> pveversion -v

 

[Fathi]

please also post your:

> pveversion -v

root@pve-10-101:~# pveversion -v
proxmox-ve: 5.1-32 (running kernel: 4.13.13-2-pve)
pve-manager: 5.1-41 (running version: 5.1-41/0b958203)
pve-kernel-4.13.13-2-pve: 4.13.13-32
libpve-http-server-perl: 2.0-8
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-19
qemu-server: 5.0-18
pve-firmware: 2.0-3
libpve-common-perl: 5.0-25
libpve-guest-common-perl: 2.0-14
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-17
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-3
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-5
pve-container: 2.0-18
pve-firewall: 3.0-5
pve-ha-manager: 2.0-4
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.1-2
lxcfs: 2.0.8-1
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.3-pve1~bpo9

 

[wbumiller]

lxc-pve: 2.1.1-2

Try updating to lxc-pve-2.1.1-3.

 

[Fathi]

Try updating to lxc-pve-2.1.1-3.

It worked.
Thank you.

 

[Jacob]

What's the best method to update the package? I'm having the same issue but running apt-get upgrade lxc-pve the system tells me I am already running the latest version.

 

[billbillw]

Same problem here...this seems to be a frequent problem with the update/upgrade process.

 

[Fathi]

What's the best method to update the package? I'm having the same issue but running apt-get upgrade lxc-pve the system tells me I am already running the latest version.

If you don't have a subscription to the proxmox repo then you have to enable the "no sbscription" repo to get any update for Proxmox packages.

 

[billbillw]

What's the best method to update the package? I'm having the same issue but running apt-get upgrade lxc-pve the system tells me I am already running the latest version.

Jacob, I'm not sure if was the absolute best thing to do, but I had the same problem as you. I solved it by clearing the apt list and re-running apt update/apt full-upgrade.
This is the command to remove the apt list:

rm /var/lib/apt/lists/*

After I did it, I 'might' have read that it wasn't recommended, so you may want to wait for some of the proxmox staff to chime in.

 

[Jacob]

That's what ended up being my solution as well. I had to go through the apt-sources.list and find out the ones that led to the enterprise version and change them to the no-sub version and then update from there. I "should" have it all cleared out now, at least all my containers start finally.

 

[Fathi]

It worked.
Thank you.

Hello, same problem here. There seems no 2.1.1-3 lxc-pve available. How did you upgrade to it ?
TIA

 

[Jacob]

That's because the package is up to lxc-pve: 3.0.2

What is the issue you are having? Have you switched over to the non-enterprise channel for updates and run update and upgrade?
Is this a new install of the latest distro or an older install that went bad?

 

[Fathi]

this is a server with proxmox 5.1 which I didn't update since 270+ days. I configured /etc/pve/status.cfg to send to an influxdb, updated and rebooted it.
After reading this forum, I added the no subscription apt repo and did another update which solved my problem.
Before that, I was using only the official repos.