Server goes unresponsive after random amount of time has passed, I have tried modded and unmodded servers same issue persists. I am hosting locally connecting directly to server address 0. No crash logs or errors in latest.log I have been trying to debug using spark but since this happens randomly I can not pinpoint what is causing the issue, can not run spark profile after server times out. Running forge 47.1.106 MC 1.20.1
Got it, thanks for the details! Let’s start by checking the server logs to see if there’s anything unusual just before the server goes unresponsive. Could you upload or paste the relevant parts of your latest.log file? Focus on the sections right before the server times out.
This post was produced by an AI controlled by CubeCoders Limited - Feedback
For security reasons, I can’t access external links. Please copy and paste the relevant sections of your latest.log here, especially the part right before the server goes unresponsive.
This post was produced by an AI controlled by CubeCoders Limited - Feedback
It looks like your server’s tick times and TPS are consistently good, which is a positive sign. The Horse moved wrongly! warnings are generally harmless and indicate minor desyncs.
Given that the server becomes unresponsive without logs indicating a crash or error, the issue might be related to resource limits, such as memory or CPU, or potentially network issues.
Let’s check a few things:
Memory Usage: Ensure the server has enough allocated memory, and monitor it while the server is running.
CPU Usage: Monitor the CPU usage during server operation to see if there are any spikes.
Network: Verify your network stability. You can use a tool like ping or tracert to check for any irregularities.
You can also try the following command to see if any ports are being blocked:
ampinstmgr ports [INSTANCENAME]
Replace [INSTANCENAME] with the name of your Minecraft instance.
Can you confirm if these resource usages are within normal ranges or share any unusual findings?
This post was produced by an AI controlled by CubeCoders Limited - Feedback
Thanks for the info. Since your resource usage is within normal ranges, it might be a specific mod causing the issue, especially since it happens both modded and unmodded. Here are a few more things to consider:
Update Mods and Forge: Ensure all mods and Forge are up to date.
Check Mod Compatibility: Some mods might not play well together. Try running the server with a minimal set of mods and gradually add them back.
Test Without Mods: Although you mentioned it happens unmodded as well, make sure to test with a clean installation to rule out any lingering issues from previous mods.
Lastly, let’s run ampinstmgr dumpfirewall to check AMP’s view of the firewall situation:
ampinstmgr dumpfirewall
Share the output from this command to see if there are any unexpected firewall rules.
This post was produced by an AI controlled by CubeCoders Limited - Feedback
Understood, thanks for clarifying. Since the problem persists with and without AMP and across different configurations, we might need to delve deeper.
Check Java Version: Ensure you are using the latest stable version of Java. Minecraft servers typically run best on the latest LTS version of Java. Verify the Java version with:
java -version
Garbage Collection: Java’s garbage collector can sometimes cause hiccups. You might want to experiment with different garbage collection settings. For example:
-Xmx20G -Xms20G -XX:+UseG1GC
Network Configuration: Ensure there are no network issues. This includes checking for any ISP-related issues, router configurations, or even trying a different network.
Operating System Logs: Check Windows Event Viewer for any system logs or errors that coincide with the server becoming unresponsive.
If none of these help, it might be beneficial to run a detailed profiler on your server to catch the issue as it happens. Spark is a good choice, but considering the randomness, you might want to run it continuously with lower overhead.
If you have any specific findings or need further assistance with a particular aspect, let me know!
This post was produced by an AI controlled by CubeCoders Limited - Feedback
Im not seeing anything in windows event viewer related to java around the time of the crash. I am running java 17 eclipse I have tried different GC’s and same result
Alright, thanks for the detailed troubleshooting. Given that none of the usual suspects seem to be the cause, let’s try running a continuous profiler with Spark to see if we can capture more detailed information.
Here’s how you can run Spark in continuous mode:
Install Spark:
/spark
Run Spark in Background:
Set Spark to start profiling continuously. You can do this by starting it with a command and letting it run in the background:
/spark profiler --continuous --interval 60
Check Spark Output:
After the server becomes unresponsive again, check Spark’s output to see if it has captured anything unusual.
Post-Analysis:
If Spark captures any relevant data, please share the findings here, and we can analyze it further.
While Spark is running continuously, ensure you keep an eye on the server’s performance to avoid any additional load. This might give us more insights into the root cause of the issue.
This post was produced by an AI controlled by CubeCoders Limited - Feedback
@Bkoe Can you try using the Adoptium JDK instead please? Whatever the newest version is that will work with your MC server which will likely be version 21.
@Mike I am currently running 17.0.11 by Eclipse Adoptium; OS Windows 11 arch amd64 version 10.0 for Minecraft Forge 1.20.1. Should I upgrade to 21? As far as I knew for 1.20.1 I should be on 17
Java 21 used less ram thats for sure but same issue, server still timed out. Could it be the watchdog or would there be an error in the logs if that were the case?
It stalls in place, AMP thinks the server is still running but its stalled out. Even when Im not playing and I close all running programs my friends join and it stalls on them too.
This post was produced by an AI controlled by CubeCoders Limited -