PufferPanel Suddenly Shuts Down on Ubuntu 22.04 LTS Container in Proxmox

Question

PufferPanel Suddenly Shuts Down on Ubuntu 22.04 LTS Container in Proxmox

Minionguyjpro opened this issue 9 months ago · comments

Please use our Discord for issues, questions, or help with installation or configuration of PufferPanel.
This issue tracker is only for confirmed bug reports. Please consider joining our Discord and asking there before opening an issue here.
Please delete these 3 lines before submitting your issue.

Describe the bug
After some time, my Minecraft server suddenly shuts down. I saw PufferPanel also shutted down.

To Reproduce
Steps to reproduce the behavior:

Setup Proxmox
Run an Ubuntu 22.04 LTS container with LXC
Run PufferPanel and setup a Minecraft server
Play for some time
Shuts down at a random momennt

Expected behavior
It shouldn't shutdown and continue

Screenshots

Desktop (please complete the following information):

OS: [e.g. iOS] Linux
Browser [e.g. chrome, safari] firefox
Version [e.g. 22] 118

Smartphone (please complete the following information):

Device: [e.g. iPhone6] Samsung Galaxy A12
OS: [e.g. iOS8.1] Android 13
Browser [e.g. stock browser, safari] Stock browser, Samsung Internet Browser
Version [e.g. 22] Don't know

Additional context
Add any other context about the problem here.

Joshua Taylor · Answer 1 · Thu Oct 19 2023 22:28:26 GMT+0800 (China Standard Time)

oom-kill means your system is running out of memory and is killing things that are using it. This isn't an issue with the panel. You need to increase the memory allocated to your machine or lower the memory used by your servers.

Minionguyjpro · Answer 2 · Thu Oct 19 2023 22:29:32 GMT+0800 (China Standard Time)

This is weird though, as Proxmox reports it uses only 1% memory and when I am in the server it only uses like 1/4th of the memory.

Joshua Taylor · Answer 3 · Thu Oct 19 2023 22:32:33 GMT+0800 (China Standard Time)

We do not control the oom-killer and it's a system-level thing. There's nothing we can really do about it.

https://www.kernel.org/doc/gorman/html/understand/understand016.html these rules are kicked in, so if the oom-kill went into effect, then you did hit something that took all the memory. And the kernel chose to kill the panel.

Minionguyjpro · Answer 4 · Fri Oct 20 2023 13:37:13 GMT+0800 (China Standard Time)

I did chose to sort of disable oom-killer, and change some memory overcoming option. I also lowered the memory by 256MB RAM of the server, so that would be available to the system. Op do 19 okt. 2023 16:32 schreef Joshua Taylor ***@***.***>:

…

We do not control the oom-killer and it's a system-level thing. There's nothing we can really do about it. https://www.kernel.org/doc/gorman/html/understand/understand016.html these rules are kicked in, so if the oom-kill went into effect, then you did hit something that took all the memory. And the kernel chose to kill the panel. — Reply to this email directly, view it on GitHub <#1278 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APYNRKUADJ6ER5BG4WFKT2LYAE2YXAVCNFSM6AAAAAA6HJZ7KKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZRGEYTKOJSHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

Torsten Widmann · Answer 5 · Fri Oct 20 2023 17:59:16 GMT+0800 (China Standard Time)

are you using lxc or kvm? i cant confirm this with kvm.

running Pufferpanel with Ubuntu 22.04 in a kvm vm on proxmox 8

Minionguyjpro · Answer 6 · Sat Oct 21 2023 22:28:01 GMT+0800 (China Standard Time)

are you using lxc or kvm? i cant confirm this with kvm.

running Pufferpanel with Ubuntu 22.04 in a kvm vm on proxmox 8

I run it in an LXC container, but sort of disabled it and changed some things.

Minionguyjpro · Answer 7 · Wed Nov 01 2023 03:44:50 GMT+0800 (China Standard Time)

I had this issue again, but I hope it is now fixed now I increased the SWAP from 512MB to 2GB.