A
abeeson
Guest
Hey all,
We have been running an FTB Beyond server for a while now (since at least a few versions back) and the latest release and beta 1.8.x have been awesome in terms of fixing issues, however whilst its fixed a bunch of problems including a bizarre FPS drop on the client side, it has introduced a bug that is causing our server to lock up after a few hours (or a bit more, haven't nailed the timing down yet)
At first i thought it was the scheduled restarts, but it doesn't seem to be.
Is anybody else seeing this? I've had a quick look at the logs, and it doesn't seem to have anything obvious in there, next time it occurs i'm going to do a deep dive to try to figure it out, but wondering if anybody else has seen anything similar?
The server will either log you in, and just render one chunk (or none) or it'll say logging you in and then error with a generic fault.
The console allows you to type, but no command will return anything, except for stop, which will print "stopping server" but then not actually do anything, you end up having to kill the server with a full kill -9 to SIGKILL it, which is not exactly a clean way to stop the host....
We have been running an FTB Beyond server for a while now (since at least a few versions back) and the latest release and beta 1.8.x have been awesome in terms of fixing issues, however whilst its fixed a bunch of problems including a bizarre FPS drop on the client side, it has introduced a bug that is causing our server to lock up after a few hours (or a bit more, haven't nailed the timing down yet)
At first i thought it was the scheduled restarts, but it doesn't seem to be.
Is anybody else seeing this? I've had a quick look at the logs, and it doesn't seem to have anything obvious in there, next time it occurs i'm going to do a deep dive to try to figure it out, but wondering if anybody else has seen anything similar?
The server will either log you in, and just render one chunk (or none) or it'll say logging you in and then error with a generic fault.
The console allows you to type, but no command will return anything, except for stop, which will print "stopping server" but then not actually do anything, you end up having to kill the server with a full kill -9 to SIGKILL it, which is not exactly a clean way to stop the host....