PID limit on Pterodactyl (HAProxy)

[MG141]

Expected Behavior

Server should operate normally as excepted even with HAProxy enabled

Actual Behavior

With HAProxy enabled on Pterodactyl panel a server randomlly loops and takes up all the avaliable CPU (with PID limit disabled). If PID limit is enabled it gets hit and server is killed.

It loops with players online or with no players. Looping is random. Sometimes it takes a few days, sometimes just a few minutes.

With HAProxy enabled. About 6 endpoints are opened at the start up process. Sometimes velocity is unable to even close with endpoints and server needs to be hard shutdown (killed) in order to restart.

Steps to Reproduce

Run Velocity server on Pterodactyl server
Enable HAproxy in the .toml configuration file
Wait

Plugin List

AutoUodateGeyser
CleanPing
Custom F3 Brand
FooodGate
ForceResourcePack
Geyser
JPremium
LuckPerms
mdMOTD
plan
SkinsRestorer
Sonar
Tebex
Velocity-hub
Voicechat
VotifierPlus

Velocity Version

[11:14:35 INFO]: Velocity 3.4.0-SNAPSHOT (git-8f65a814-b558)

Additional Information

No response

[MG141]

Ok.

The issue seems to be coming from "Enable-reuse-port" option. It seems like running pterodactyl with docker and this setting enabled, loops and overloads the CPU no matter that the system is powered by Linux OS. It does happen randomly though with no way to predict it. I narrowed it down that it can happen from anywhere as fast as 15 minutes to up to 24 hours.

[Timongcraft]

Well I have had that option enabled since it was was added and never had problems like that, I don't use HAProxy and many of your plugins though. Could you try to create a a minimal setup to reproduce the issue?