Debian 10 template

[SamTzu]

Yes. Something somewhere is leaking. It's not just with Debian 10.
I'm getting this on a Proxmox 5 host that has hardly any load at all with containers that have zero load:
Sep 04 05:41:19 pve12a kernel: Memory cgroup out of memory: Kill process 13694 (systemd-journal) score 279 or sacrifice child Sep 04 05:41:19 pve12a kernel: Killed process 13694 (systemd-journal) total-vm:242692kB, anon-rss:268kB, file-rss:4kB, shmem-rss:149864kB Sep 04 05:41:20 pve12a kernel: Memory cgroup out of memory: Kill process 15469 (mysqld) score 246 or sacrifice child Sep 04 05:41:20 pve12a kernel: Killed process 15469 (mysqld) total-vm:711344kB, anon-rss:51612kB, file-rss:0kB, shmem-rss:0kB Sep 06 16:10:23 pve12a kernel: Memory cgroup out of memory: Kill process 1381 (mysqld) score 153 or sacrifice child Sep 06 16:10:23 pve12a kernel: Killed process 1381 (mysqld) total-vm:711148kB, anon-rss:79876kB, file-rss:0kB, shmem-rss:0kB

 

[Eraser]

I was googling for Debian 10 template problems when I found this topic. I just created a new CT with the Debian 10 template. I booted the system, logged in through the Proxmox web console and run two commands:
#apt update
#apt upgrade
After the upgrades finished I did a #reboot and the CT never booted again. Proxmox says it failed to start.

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

The systemctl status command says:

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

Since i'm no pro at this I will just use Debian 9. But I thought maybe you guys can use this information to verify that there is something wrong with the Debian 10 template. I would assume an apt upgrade should be safe to run right?

 

[oguz]

hi,

I was googling for Debian 10 template problems when I found this topic. I just created a new CT with the Debian 10 template. I booted the system, logged in through the Proxmox web console and run two commands:
#apt update
#apt upgrade
After the upgrades finished I did a #reboot and the CT never booted again. Proxmox says it failed to start.

please open a new thread, as your problem is unrelated to the topic.

the template provided by us doesn't cause a problem like this.
however if i had to take a guess, you might be running an older version of PVE (in which debian containers with version >= 10 aren't supported). try updating your system and see if that solves the problem. if not, open a new thread please.

 

[SamTzu]

Same problem with Proxmox 6 & Debian 10 template. (Tested on 2 different Hardware.) Byobu keeps "leaking" all over the place. It's easy to test. Just install Byobu on Debian 10 LXC template type "byobu" and then do "ls -ahl /" and "cat /etc/gai.conf".

Byobu just uses tmux or screen as a terminal so this problem goes deeper in Debian 10 and since this problem occured on Proxmox 5 (with Debian 10 LXC template) I don't think it's the kernel's fault.

 

[oguz]

Same problem with Proxmox 6 & Debian 10 template. (Tested on 2 different Hardware.) Byobu keeps "leaking" all over the place. It's easy to test. Just install Byobu on Debian 10 LXC template type "byobu" and then do "ls -ahl /" and "cat /etc/gai.conf".

i didn't see any "leak" or text mixing up while trying to reproduce this.

how are you connecting to the terminal? (vnc, ssh, pct enter, etc.)

 

[SamTzu]

I use SSH over VPN. I'm pretty sure Byobu is the key to finding out what is really going on.

 

[SamTzu]

As a side note the memory issues were caused by combination of ZFS and Ballooning. Both of those techs compete with each other for available memory and even when everything seems to work out you end up having this:

kernel: Memory cgroup out of memory: Kill process 13694 (systemd-journal) score 279 or sacrifice child.