Version:
1.4.1
What is the bug:
Actual Version: 1.5.0 / 1.5.1
So after updating to 1.5.0 / 1.5.1 my server began resetting randomly - I noticed this has been happening with many others and began my own attempts to track it down. My host provider and I tried troubleshooting and discovered that the server console is not responding to commands in the console - IE: they're just not showing up - nada - which got us to thinking that perhaps THIS is the cause of the crash detection part of Multicraft (the platform that many providers use to host servers) from thinking that servers are unresponsive and restarting them. Obviously my host isn't about to disable the crash detection component for an entire node of servers, but if this is the actual cause of the problem, perhaps we can figure out why - 1.4.1 did not have this issue, and the console responded normally.
See: http://support.feed-the-beast.com/t...5-0-1-5-1-unresponsive-console-commands/14150
Mod & Version:
Paste.feed-the-beast.com log:
Can it be repeated:
Known Fix:
1.4.1
What is the bug:
Actual Version: 1.5.0 / 1.5.1
So after updating to 1.5.0 / 1.5.1 my server began resetting randomly - I noticed this has been happening with many others and began my own attempts to track it down. My host provider and I tried troubleshooting and discovered that the server console is not responding to commands in the console - IE: they're just not showing up - nada - which got us to thinking that perhaps THIS is the cause of the crash detection part of Multicraft (the platform that many providers use to host servers) from thinking that servers are unresponsive and restarting them. Obviously my host isn't about to disable the crash detection component for an entire node of servers, but if this is the actual cause of the problem, perhaps we can figure out why - 1.4.1 did not have this issue, and the console responded normally.
See: http://support.feed-the-beast.com/t...5-0-1-5-1-unresponsive-console-commands/14150
Mod & Version:
Paste.feed-the-beast.com log:
Can it be repeated:
Known Fix: