Centos 6 LXC issue

Maeg

New Member
May 30, 2019
11
0
1
35
Hi guys.
I'm having some trouble.
I migrate Centos 6 (Redhat 6) from openVZ using that article Convert guide
I've done recomendations from that thread
All good. CT works fine.
But there is strange situation - it works flawlessly if i done pct start and pct shutdown.
CT shutdowns good, and then start as normal.
But - if i try shutdown it via Web-GUI, or shutdown -P or halt from within CT - i have problem with /dev/pts as i wrote some time ago in that thread
I'm using CLI, but my co-workers prefer WebGui - so there is trouble.
Any thoughts?
Code:
root@px00:~#pct start 104
Job for pve-container@104.service failed because the control process exited with error code.
See "systemctl status pve-container@104.service" and "journalctl -xe" for details.
command 'systemctl start pve-container@104' failed: exit code 1

root@px00:~# journalctl -xe
дек 19 11:38:35 px00 kernel: audit: type=1400 audit(1576744715.362:39): apparmor="STATUS" operation="profile_replace" info="same
дек 19 11:38:35 px00 kernel: vmbr0: port 9(veth104i0) entered blocking state
дек 19 11:38:35 px00 kernel: vmbr0: port 9(veth104i0) entered disabled state
дек 19 11:38:35 px00 kernel: device veth104i0 entered promiscuous mode
дек 19 11:38:35 px00 kernel: eth0: renamed from vethVNH47C
дек 19 11:38:36 px00 lxc-start[7314]: lxc-start: 104: lxccontainer.c: wait_on_daemonized_start: 865 Received container state "AB
дек 19 11:38:36 px00 lxc-start[7314]: lxc-start: 104: tools/lxc_start.c: main: 330 The container failed to start
дек 19 11:38:36 px00 lxc-start[7314]: lxc-start: 104: tools/lxc_start.c: main: 333 To get more details, run the container in for
дек 19 11:38:36 px00 lxc-start[7314]: lxc-start: 104: tools/lxc_start.c: main: 336 Additional information can be obtained by set
дек 19 11:38:36 px00 systemd[1]: pve-container@104.service: Control process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit pve-container@104.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
дек 19 11:38:36 px00 systemd[1]: pve-container@104.service: Killing process 7327 (3) with signal SIGKILL.
дек 19 11:38:36 px00 systemd[1]: pve-container@104.service: Killing process 7394 (apparmor_parser) with signal SIGKILL.
дек 19 11:38:36 px00 systemd[1]: pve-container@104.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit pve-container@104.service has entered the 'failed' state with result 'exit-code'.
дек 19 11:38:36 px00 systemd[1]: Failed to start PVE LXC Container: 104.
-- Subject: Ошибка юнита pve-container@104.service
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Произошел сбой юнита pve-container@104.service.
--
-- Результат: failed.
 
Try pct set <vmid> -cmode <console | shell | tty> and see man pct for more information.
 

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 yours easily in our online shop.

Buy now!