Used to work but now container cannot start after new build

[mihalski]

I've used your wonderful script before and it worked perfectly.. However I've tried multiple times today and even though it appears to build without error it fails to start with the following erroor:

root@pve:~# 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 Sat 2020-01-11 17:35:17 AEST; 16s ago
     Docs: man:lxc-start
           man:lxc
           man:pct
  Process: 17171 ExecStart=/usr/bin/lxc-start -n 101 (code=exited, status=1/FAILURE)

Jan 11 17:35:16 pve systemd[1]: Starting PVE LXC Container: 101...
Jan 11 17:35:17 pve lxc-start[17171]: lxc-start: 101: lxccontainer.c: wait_on_daemonized_start: 856 No such file or directory - Failed to receive the container state
Jan 11 17:35:17 pve lxc-start[17171]: lxc-start: 101: tools/lxc_start.c: main: 330 The container failed to start
Jan 11 17:35:17 pve lxc-start[17171]: lxc-start: 101: tools/lxc_start.c: main: 333 To get more details, run the container in foreground mode
Jan 11 17:35:17 pve lxc-start[17171]: lxc-start: 101: tools/lxc_start.c: main: 336 Additional information can be obtained by setting the --logfile and --logpriority options
Jan 11 17:35:17 pve systemd[1]: pve-container@101.service: Control process exited, code=exited, status=1/FAILURE
Jan 11 17:35:17 pve systemd[1]: pve-container@101.service: Failed with result 'exit-code'.
Jan 11 17:35:17 pve systemd[1]: Failed to start PVE LXC Container: 101.

Trying to run the container in foreground mode didn't really give me much more:

root@pve:~# lxc-start -n 101 -F
lxc-start: 101: conf.c: run_buffer: 335 Script exited with status 25
lxc-start: 101: start.c: lxc_init: 861 Failed to run lxc.hook.pre-start for container "101"
lxc-start: 101: start.c: __lxc_start: 1944 Failed to initialize container "101"
lxc-start: 101: tools/lxc_start.c: main: 330 The container failed to start
lxc-start: 101: tools/lxc_start.c: main: 336 Additional information can be obtained by setting the --logfile and --logpriority options

Any ideas as to what the problem might be?

Thank you in advance.

Regards, Michal

[Tollbringer]

Have you made sure Proxmox is fully up-to-date?

Will

[dmstr82U2]

I'm having a similiar issue, I'm running version 6.1-3. It will install with no errors but, after I login, this is displayed "Clean up process", "No screen session found" (does this 4 times). Closing AP and exit with code:0, then prompts me to logon again.

P.S it does enable Samba.

[Tollbringer]

Please update Proxmox - 6.1-15 is the latest. Also, this will occur if you have not correctly set up the community edition - commonly referred to as the "nag" removal also.

sed -i "s/^deb/\#deb/" /etc/apt/sources.list.d/pve-enterprise.list

# Add PVE Community Repo
echo "deb http://download.proxmox.com/debian/pve $(grep "VERSION=" /etc/os-release | sed -n 's/.*(\(.*\)).*/\1/p') pve-no-subscription" > /etc/apt/sources.list.d/pve-no-enterprise.list

# Remove nag
echo "DPkg::Post-Invoke { \"dpkg -V proxmox-widget-toolkit | grep -q '/proxmoxlib\.js$'; if [ \$? -eq 1 ]; then { echo 'Removing subscription nag from UI...'; sed -i '/data.status/{s/\!//;s/Active/NoMoreNagging/}' /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js; systemctl restart pveproxy.service; }; fi\"; };" > /etc/apt/apt.conf.d/no-nag-script
apt --reinstall install proxmox-widget-toolkit 

Run this in the PVE shell, reboot. The "No subscription nag " should be gone. The refresh the updates and make sure you are on v6.1-15. Let me know if I can be of further assistance.

Tollbringer

[dmstr82U2]

Tollbringer, when I run the "apt --reinstall install proxmox-widget-toolkit" command after updating the "pve-no-enterprise.list" and "/etc/apt/apt.conf.d/no-nag-script" files with the information you have provided, I am presented with "E: Syntax error /etc/apt/apt.conf.d/no-nag-script:2: Extra junk after value". I have rebooted the server and also ran it in incognito with the same results.

[Tollbringer]

If you are around Discord I would love to help. Dr.Zzzs or DigiblurDIY channels!

[dmstr82U2]

Ok, I will login , when I get home.