pterodactyl / panel

Pterodactyl® is a free, open-source game server management panel built with PHP, React, and Go. Designed with security in mind, Pterodactyl runs all game servers in isolated Docker containers while exposing a beautiful and intuitive UI to end users.
https://pterodactyl.io
Other
6.69k stars 1.7k forks source link

Restarting servers on the node several times a day #3983

Closed AndreyEremin02 closed 2 years ago

AndreyEremin02 commented 2 years ago

Current Behavior

Several times a day, all servers located on the node start restarting due to this error.

Expected Behavior

The absence of such random crashes and reboots.

Steps to Reproduce

After installation, the error is reproduced automatically, several times a day.

Panel Version

1.7.0

Wings Version

1.6.1

Games and/or Eggs Affected

counter-strike: global offensive

Docker Image

ghcr.io/pterodactyl/games:source

Error Logs

Wings - https://ptero.co/oqigebelog
Panel - http://bin.ptdl.co/4asy1

Is there an existing issue for this?

Mutex21 commented 2 years ago

Check the ram & swap ram usage. I reverted back on 1.5.3 wings and now is fine. With default kernel or custom like xanmod recompiled, the results are the same. Wings 1.6.1 cause for me a lot of problems with srcds servers (half-life | counter-strike 1.6)), assuming the swap memory increase to 100% (memory leak). I tested on 3 gaming dedicated servers with the different docker versions, but the same version wings (1.6.1) and that's happened. With the 1.6.1 wings, a lot of ram/swap ram are allocated and with each hour increasing and when the swap usage is 100%, the docker is restarting with the same situation as yours.

memory

DaneEveritt commented 2 years ago

Did you consider opening a bug report since that is not intentional behavior, and in fact the default for 99% of users on 1.6.1 has been a significant decrease in memory and CPU usage.

Please don't blindly encourage people to downgrade, it rolls back important security and performance fixes and a single user and graph are hardly conclusive indicators of an issue. We also provide profiling tools rather than just looking at a graph that only shows your system using swap.

DaneEveritt commented 2 years ago

There is no information in this bug report that is actionable, therefore I am closing it.