Server crashing for being out of memory constantly
This has been happening since yesterday, no idea what triggered it but somehow Pterodactyl keeps killing my server because it thinks I am out of memory
21 Replies
container@pterodactyl~ Server marked as offline...
[Pterodactyl Daemon]: ---------- Detected server process in a crashed state! ----------
[Pterodactyl Daemon]: Exit code: 137
[Pterodactyl Daemon]: Out of memory: true
Thanks for asking your question!
Make sure to provide as much helpful information as possible such as logs/what you tried and what your exact issue is
Make sure to mark solved when issue is solved!!!
/close
!close
!solved
!answered
Requested by marijnisn00b#0
Thats the error message I keep getting
Using Fabric 1.20.1
Seems like the log wasnt saved
startup flags?
it doesnt if tis a oom
java -Xms128M -Xmx8192M -Dterminal.jline=false -Dterminal.ansi=true -jar fabric-server-launch.jar
Now using Lilypad hosting btw
how much ram do u pay for from ur host
8 gigs
try setting it to 6.5-7
I can ask to change the startup flags, rn I dont have access to it
@Josh does lilypad provide/cover overhead?
we can yup
adding some now
try now @MarijnIsN00B
Will do, ty
Is it possible that its somehow the servers mods?
I was using EnviroMC before this and I was paying for 6 gigs, changed it to 5 gigs and would still get this crash
pterodactyl/docker + setting xmx=container size
does it/causes it usually
Ah okay
Is it possible to just not let Pterodactyl kill my server?
hopefully what I've just done will mean it won't have to
I sure hope that too lol
This issue has been haunting me for the past few days
Its the first time I try using actual proper paid hosts and its been the worst season until now that Ive ever hosted
Pterodactyl keeps killing my server because it thinks I am out of memoryPterodactyl isn't killing your server, the Linux kernel is no way on Linux to disable the OOM killer from my understanding. It's Linux's last ditch effort to bring back the system if you've ran out of memory you can stop the container from running out of memory by adding swap to the container tho
there are 2 oom killers
pterodactyls (usually turned off, but it doesnt really matter iirc it only kills instances if the machine itself is running out)
docker also has one
but host dont and shouldnt disable it (iirc pterodactyl uses it), as it could lead to abuse
not even sure if u can disable it unless u modify wings
I think you can disable it via wings settings
but yeah we keep it on
yeah its just simpler and easier to maintain
and manage