Server crash ($10 Reward)

All i can see is that the server runs out of memory. Don't you have problems with too many entities? If not i guess it's a serious memory leak caused by 1 of the plugins. Don't u maybe have your own plugin? Idk how it's possible to run out of 8gb.

 

Show your timings via /timings

 

Also change your start script so that your -Xms tag is at like 1 gb instead of matching the -Xmx tag so that it can release the ram as it doesn't need it so that other programs on the server can use it

 

Support is only given to buyers

 

I think the problem is with VotingPlugin. I'd remove it and switch to another plugin (I'm going to shamelessly plug SuperbVote, which I made).

 

Looks like world save is pretty hefty. What’s the combined size of your worlds?

 

Timings don’t really show much. I’d say remove plugins one by one and debug it out. Start with jobs

 

1. If you think the problem is Featherboard use Liteboard, Featherboard is really bad my biggest regret and has lot of performance issues.

2. Use Paper 1.12.2 if you want to have a lot more performance, if you see your actual performance isnt enough updating will fix lot of your issues.
I went from 80% - 90% usage to 20% - 30% with 30 online in Survival (Tested in HTOP, 8 cores)

3. Dont use flags! In my experience they gave me less performance than more, and your issue is likely about memory, so stop using flags. Java manages everything better than humans do.

4. Deactivate metrics and update from all your plugins, and check to disable functions you dont use from them.

5. Make world saving every 1-2 hours, if your world is too big maybe is making memory leaks. (I dont really know though, but making the world save every 1 - 2 hours will obviously help)

6. AutoRestart your server every night! This is really important to keep everything fresh because almost every plugin (and spigot) has memory leaks that leads to server starvation, restarting will clear the memory and make the server start "fresh" i personally use autorestart reloaded for this and restart everyday in the morning.

7. Keep all your plugins updated.- And dont use old public plugins! (Atleast you know it wont harm your server).
PD: if you use essentials i recommend updating it to essentialsx if you didnt yet.

In my personal experience, the best thing i ever did was updating from 1.8 to 1.12, if you see a performance increase in Paper 1.12.2 and want to add compatibility with 1.7/1.8 and pre-1.9 combat i have a special plugin pack configured and programmed to make your pvp the most similar as posible to pre-1.9 (KB is based on 1.7 tho) and add compatibility with older versions. You can download it in my pluginpack discord http://discord.gg/cjt9bPA we give general support too.

And i want to add; Its not any plugin; I use the same with no problems; Plugins show that they are using lot of resources because the server is lagging and that makes all the processes to make something similar to "collapse".

I had problem with this too; this is my personal experience.

Hope this helps. And i dont want any money, but if you wish to donate; http://paypal.me/mchurruarin

 

I looked at the crash log itself and discovered a bunch of threads tied up calling into VotingPlugin. That's why the server is complaining that it can't launch any more threads. I'm fairly confident the issue lies there.

 

I think thats normal if many people votes, as the server is lagging, the votes maybe take time to process.

 

No, this is not normal. Did you even examine the log yourself?

I'll include one of the threads, tell me if this is "normal":

Code (Text):

BLOCKED Craft Scheduler Thread - 2197: [com.Ben12345rocks.VotingPlugin.Util.PlaceHolders.PlaceHolders.getPlaceHolder(PlaceHolders.java:54), com.Ben12345rocks.VotingPlugin.PlaceHolderAPI.expansion.VotingPliuginExpansion.onPlaceholderRequest(VotingPliuginExpansion.java:75), me.clip.placeholderapi.PlaceholderAPI.setPlaceholders(PlaceholderAPI.java:212), me.clip.placeholderapi.PlaceholderAPI.setPlaceholders(PlaceholderAPI.java:188), be.maximvdw.placeholdercore.placeholders.PlaceholderAPIPlaceholderPack$1.getResult(PlaceholderAPIPlaceholderPack.java:37), be.maximvdw.placeholdercore.placeholders.PlaceholderAPIPlaceholderPack$1.getResult(PlaceholderAPIPlaceholderPack.java:26), be.maximvdw.featherboard.cJ.a(cJ.java:224), be.maximvdw.featherboard.l.a(l.java:38), be.maximvdw.featherboard.bH.a(bH.java:19), be.maximvdw.featherboard.bH.a(bH.java:56), be.maximvdw.featherboard.api.scoreboard.ScoreboardLine.updatePlaceholders(ScoreboardLine.java:78), be.maximvdw.featherboard.api.scoreboard.ScoreboardGroup$AnimationUpdater.run(ScoreboardGroup.java:7), org.bukkit.craftbukkit.v1_8_R3.scheduler.CraftTask.run(CraftTask.java:71), org.bukkit.craftbukkit.v1_8_R3.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:53), java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149), java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624), java.lang.Thread.run(Thread.java:748)]

Examining the code itself, I get the impression that the author of this plugin does not know much about safe concurrent programming in Java, or even much about recommended practices for Java projects in general.

 

Oh yeah, thats a exception.

 

Not bad advice.

The flags that any random shmuck off the net throws out will ruin your performance. Use Aikar's flags instead. He has extensive experience with the inner workings of the Minecraft server and did extensive research into Java's garbage collector, so his advice is probably the best you'll get when it comes to Java flags. He also works on Paper.

The OP is already using Aikar's flags, and in any event this isn't a memory leak issue.

...this makes almost no sense at all.

Autorestarts should not be needed in any sane server setup.

Good advice.