Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fake crash message #2392

Closed
andfont opened this issue Aug 1, 2019 · 4 comments
Closed

fake crash message #2392

andfont opened this issue Aug 1, 2019 · 4 comments
Labels
version: 1.14 Game version 1.14

Comments

@andfont
Copy link

andfont commented Aug 1, 2019

paper 153 server 1.14.4
Error:
01:59:17] [Paper Watchdog Thread/ERROR]: --- DO NOT REPORT THIS TO PAPER - THIS IS NOT A BUG OR A CRASH - git-Paper-152 (MC: 1.14.4) ---
[01:59:17] [Paper Watchdog Thread/ERROR]: The server has not responded for 10 seconds! Creating thread dump
[01:59:17] [Paper Watchdog Thread/ERROR]: ------------------------------
[01:59:17] [Paper Watchdog Thread/ERROR]: Server thread dump (Look for plugins here before reporting to Paper!):
[01:59:17] [Paper Watchdog Thread/ERROR]: ------------------------------
[01:59:17] [Paper Watchdog Thread/ERROR]: Current Thread: Server thread
[01:59:17] [Paper Watchdog Thread/ERROR]: PID: 26 | Suspended: false | Native: false | State: RUNNABLE
[01:59:17] [Paper Watchdog Thread/ERROR]: Stack:
[01:59:17] [Paper Watchdog Thread/ERROR]: java.lang.StringBuilder.toString(StringBuilder.java:407)
[01:59:17] [Paper Watchdog Thread/ERROR]: me.manreg.Util.MaterialLocation(Util.java:3071)
[01:59:17] [Paper Watchdog Thread/ERROR]: me.manreg.SFStorage.LimpiarBloquesOT(SFStorage.java:286)
[01:59:17] [Paper Watchdog Thread/ERROR]: me.manreg.PlayerListener$51.run(PlayerListener.java:2592)
[01:59:17] [Paper Watchdog Thread/ERROR]: org.bukkit.craftbukkit.v1_14_R1.scheduler.CraftTask.run(CraftTask.java:84)
[01:59:17] [Paper Watchdog Thread/ERROR]: org.bukkit.craftbukkit.v1_14_R1.scheduler.CraftScheduler.mainThreadHeartbeat(CraftScheduler.java:452)
[01:59:17] [Paper Watchdog Thread/ERROR]: net.minecraft.server.v1_14_R1.MinecraftServer.b(MinecraftServer.java:1147)
[01:59:17] [Paper Watchdog Thread/ERROR]: net.minecraft.server.v1_14_R1.DedicatedServer.b(DedicatedServer.java:420)
[01:59:17] [Paper Watchdog Thread/ERROR]: net.minecraft.server.v1_14_R1.MinecraftServer.a(MinecraftServer.java:1074)
[01:59:17] [Paper Watchdog Thread/ERROR]: net.minecraft.server.v1_14_R1.MinecraftServer.run(MinecraftServer.java:918)
[01:59:17] [Paper Watchdog Thread/ERROR]: java.lang.Thread.run(Thread.java:748)
[01:59:17] [Paper Watchdog Thread/ERROR]: ------------------------------
[01:59:17] [Paper Watchdog Thread/ERROR]: --- DO NOT REPORT THIS TO PAPER - THIS IS NOT A BUG OR A CRASH ---
Description:
We are creators of servers and we normally use SPIGOT but we are looking at PAPER, in our SPIGOT servers our complements work perfectly for us but in PAPER it is not giving A FALSE ERROR of some of OUR PLUGINS because we are programmers, please how can WE DELETE THIS FALSE ERROR, BUG MENSAGE? Thank you!

@electronicboy
Copy link
Member

This is not a false error, and it states not to report it to us;
Your server is taking too long to tick, given the fact that watchdog reports are typically useless for determining what went wrong, paper produces incremental warnings when the server isn't ticking, that way we actually have information to go off

You can disable these warnings by configuring the watchdog-delay in paper.yml to be longer than your existing time, however; disabling this will impact your ability to seek support for watchdog crashes

@andfont
Copy link
Author

andfont commented Aug 1, 2019

I think that the control values that you have implemented by default are too short and in spigt there is already the time-out of processes this over control does not convince me much, I also think that you would have to increase those values from 10,000 to 30,000 at least in DELAY etc .. for now I will continue with spigot I am not convinced by those exagent messages that come to my console greetings.

@electronicboy
Copy link
Member

If your server hasn't ticked in 10 seconds, you have problems

These incremental warnings just means that we actually have something to go off when your server does take the full 60 seconds (or whatever you've set), without it any watchdog crash is literally a shot in the dark as to determining the cause, and 99% of the time misses the actual issue; It's the difference between having a flight recorder and not, hopefully it never trips, but when it does, at least there is some recording to see what occured

You're more than welcome to configure this, just you shoot yourself in the foot in terms of being able to see what is going on in the server before watchdog does come to stop the server

@electronicboy
Copy link
Member

as a piece of advice, what you /really/ should be doing here is looking into timings as to why you're tripping these early warning messages in the first place, as this is a sign of major TPS loss

@kashike kashike added the version: 1.14 Game version 1.14 label Aug 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
version: 1.14 Game version 1.14
Projects
None yet
Development

No branches or pull requests

3 participants