[SOLVED] I can't start LCX

[sozie]

Good morning,


I am taking the liberty of contacting you because I definitely have a problem with a container. I think proxmox doesn't like the number "101 ^^". I'm just having problems with this container.

Job for pve-container@101.service failed because the control process exited with error code.
See "systemctl status pve-container@101.service" and "journalctl -xe" for details.
TASK ERROR: command 'systemctl start pve-container@101' failed: exit code 1

root@vps1:~# systemctl status pve-container@101.service
● pve-container@101.service - PVE LXC Container: 101
   Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2020-04-05 20:49:04 CEST; 8min ago
     Docs: man:lxc-start
           man:lxc
           man:pct
  Process: 20629 ExecStart=/usr/bin/lxc-start -n 101 (code=exited, status=1/FAILURE)

Apr 05 20:49:03 vps1 systemd[1]: Starting PVE LXC Container: 101...
Apr 05 20:49:04 vps1 lxc-start[20629]: lxc-start: 101: lxccontainer.c: wait_on_daemonized_start: 856 No such file or directory - Failed to receive the container sta
Apr 05 20:49:04 vps1 lxc-start[20629]: lxc-start: 101: tools/lxc_start.c: main: 330 The container failed to start
Apr 05 20:49:04 vps1 lxc-start[20629]: lxc-start: 101: tools/lxc_start.c: main: 333 To get more details, run the container in foreground mode
Apr 05 20:49:04 vps1 lxc-start[20629]: lxc-start: 101: tools/lxc_start.c: main: 336 Additional information can be obtained by setting the --logfile and --logpriorit
Apr 05 20:49:04 vps1 systemd[1]: pve-container@101.service: Control process exited, code=exited, status=1/FAILURE
Apr 05 20:49:04 vps1 systemd[1]: pve-container@101.service: Failed with result 'exit-code'.
Apr 05 20:49:04 vps1 systemd[1]: Failed to start PVE LXC Container: 101.

I've already looked at a topic from a person with the same problem, but I haven't been able to solve it despite several attempts. I have no error when I "mount" & "unmount" the container manually.

Kind regards,
Rémi.

 

[Stoiko Ivanov]

Check the debug logs when starting the container - as described in our reference documentation:
https://pve.proxmox.com/pve-docs/chapter-pct.html#_obtaining_debugging_logs
(and hinted in the error-message you got)

I hope this helps!

 

[sozie]

Good morning, sir,

From what I read, it seems to be a compatibility issue with Debian, which was basic in version 10, is now in 10.3.

On the other hand, I have some templates that seem incompatible even though they are downloaded directly from Proxmox, like Centos 8.

I'll give you a copy of the logs if you ever need them (https://pastebin.com/raw/VTXrwQTB).

 

[Stoiko Ivanov]

hmm - sounds like you need to upgrade your pve installation - please post the output of `pveversion -v`
(alternatively just upgrade to the latest version and try again)

I hope this helps!

 

[sozie]

Hello again,

I've already tried several times to upgrade (apt-get upgrade) but it seems to want to put me only the enterprise version, which is therefore refused.

proxmox-ve: 6.0-2 (running kernel: 5.0.15-1-pve)
pve-manager: 6.0-4 (running version: 6.0-4/2a719255)
pve-kernel-5.0: 6.0-5
pve-kernel-helper: 6.0-5
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph: 14.2.8-pve1
ceph-fuse: 14.2.8-pve1
corosync: 3.0.2-pve2
criu: 3.11-3
glusterfs-client: 5.5-3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.10-pve1
libpve-access-control: 6.0-2
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-2
libpve-guest-common-perl: 3.0-1
libpve-http-server-perl: 3.0-2
libpve-storage-perl: 6.0-5
libqb0: 1.0.5-1
lvm2: 2.03.02-pve3
lxc-pve: 3.1.0-61
lxcfs: 3.0.3-pve60
novnc-pve: 1.0.0-60
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.0-5
pve-cluster: 6.0-4
pve-container: 3.0-3
pve-docs: 6.0-4
pve-edk2-firmware: 2.20190614-1
pve-firewall: 4.0-5
pve-firmware: 3.0-2
pve-ha-manager: 3.0-2
pve-i18n: 2.0-2
pve-qemu-kvm: 4.0.0-3
pve-xtermjs: 3.13.2-1
qemu-server: 6.0-5
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.1-pve1

 

[Stoiko Ivanov]

ok - that should explain it - there was a fix for pve-container in version 3.0-4.
you need to add the pve-no-subscription repository if you don't have a subscription (and remove the pve-enterprise entry)
see our wiki: https://pve.proxmox.com/wiki/Package_Repositories
add the repository, upgrade and try again

I hope this helps!

 

[sozie]

Hello again!

Yes, I did have a little problem with the rests. It's working perfectly.

Thank you for your help!

 

[Stoiko Ivanov]

Glad that worked out