Right now I'm not able to start any containers. I can add and remove containers but not start them. VM's though are fine.
I recently renamed my node to Atlas. I think I got all steps in that part covered. I followed the advice in this post https://forum.proxmox.com/threads/proxmox-node-name-change.14327/
Here's the errors I get when I try to start a container, even a freshly created one.
● pve-container@100.service - PVE LXC Container: 100
Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2018-04-06 23:12:46 CEST; 30s ago
Docs: man:lxc-start
man:lxc
manct
Process: 2996 ExecStart=/usr/bin/lxc-start -n 100 (code=exited, status=1/FAILURE)
Apr 06 23:12:46 atlas systemd[1]: Starting PVE LXC Container: 100...
Apr 06 23:12:46 atlas lxc-start[2996]: lxc-start: 100: lxccontainer.c: wait_on_daemonized_start: 751 No such file or directory - Failed to receive the container state
Apr 06 23:12:46 atlas lxc-start[2996]: lxc-start: 100: tools/lxc_start.c: main: 368 The container failed to start.
Apr 06 23:12:46 atlas lxc-start[2996]: lxc-start: 100: tools/lxc_start.c: main: 370 To get more details, run the container in foreground mode.
Apr 06 23:12:46 atlas lxc-start[2996]: lxc-start: 100: tools/lxc_start.c: main: 372 Additional information can be obtained by setting the --logfile and --logpriority options.
Apr 06 23:12:46 atlas systemd[1]: pve-container@100.service: Control process exited, code=exited status=1
Apr 06 23:12:46 atlas systemd[1]: pve-container@100.service: Killing process 2998 (lxc-start) with signal SIGKILL.
Apr 06 23:12:46 atlas systemd[1]: Failed to start PVE LXC Container: 100.
Apr 06 23:12:46 atlas systemd[1]: pve-container@100.service: Unit entered failed state.
Apr 06 23:12:46 atlas systemd[1]: pve-container@100.service: Failed with result 'exit-code'.
I recently renamed my node to Atlas. I think I got all steps in that part covered. I followed the advice in this post https://forum.proxmox.com/threads/proxmox-node-name-change.14327/
Here's the errors I get when I try to start a container, even a freshly created one.
● pve-container@100.service - PVE LXC Container: 100
Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2018-04-06 23:12:46 CEST; 30s ago
Docs: man:lxc-start
man:lxc
manct
Process: 2996 ExecStart=/usr/bin/lxc-start -n 100 (code=exited, status=1/FAILURE)
Apr 06 23:12:46 atlas systemd[1]: Starting PVE LXC Container: 100...
Apr 06 23:12:46 atlas lxc-start[2996]: lxc-start: 100: lxccontainer.c: wait_on_daemonized_start: 751 No such file or directory - Failed to receive the container state
Apr 06 23:12:46 atlas lxc-start[2996]: lxc-start: 100: tools/lxc_start.c: main: 368 The container failed to start.
Apr 06 23:12:46 atlas lxc-start[2996]: lxc-start: 100: tools/lxc_start.c: main: 370 To get more details, run the container in foreground mode.
Apr 06 23:12:46 atlas lxc-start[2996]: lxc-start: 100: tools/lxc_start.c: main: 372 Additional information can be obtained by setting the --logfile and --logpriority options.
Apr 06 23:12:46 atlas systemd[1]: pve-container@100.service: Control process exited, code=exited status=1
Apr 06 23:12:46 atlas systemd[1]: pve-container@100.service: Killing process 2998 (lxc-start) with signal SIGKILL.
Apr 06 23:12:46 atlas systemd[1]: Failed to start PVE LXC Container: 100.
Apr 06 23:12:46 atlas systemd[1]: pve-container@100.service: Unit entered failed state.
Apr 06 23:12:46 atlas systemd[1]: pve-container@100.service: Failed with result 'exit-code'.