#i've been battling with a **slow crash** that happens whenever I launch my **quilt minecraft server*

31 messages · Page 1 of 1 (latest)

frosty salmon
#

when launched,

  • it's in the yellow for almost no time at all
  • you're able to read the motd for about 10 seconds once it goes into the green
  • the server then "goes offline" --returning "can't connect to server"--, still in the green, for a good 5 minutes
  • the server shuts down
frosty salmon
#

more info: it does this for any map that wasn't recently created by the server; this includes maps that I carry over from my instance & the old testing world

#

stats also look like this while in this soft crash phase

#

so it's not being overloaded or anthing

sonic merlin
#

on cpu

frosty salmon
#

that’s crazy unfortunate

sonic merlin
#

how many mods and what plan u using

frosty salmon
#

I’ll monitor the graphs closely when starting it up tmrw to confirm that

#

I think I posted the modlist, no?

#

oh i didnt

#

1 sec

#

all of m

#

premium… 6 gig? I gotta check

sonic merlin
#

that's a lot

#

ok yea

frosty salmon
#

it had been running p smoothly for a while

sonic merlin
#

your a bit short

#

i expect

sonic merlin
frosty salmon
#

i updated create, create deco… that’s it

sonic merlin
#

so unless you where doing some expensive action

#

it's justyou have too much for the server to handle

frosty salmon
#

too bad the only next step for cpu upgrades is extreme

#

I usually see the ram maxing out but not usually the cpu, at all

#

I stripped almost all region files from the selected world, proving there was nothing in the world that was bothering it

#

(still yielding this issue)

#

same w/ a redstone ready flatworld I generated a few hours ago with just like… 25 chunks loaded, dragn’dropped from my computer; it still didn’t take it

#

however, even with terralith and all those constituants, it could super easily start, generate & handle a world if I just selected a non-existent world so it’d generate its own