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
Strange server behavior and crashes. #34
Comments
This is the full server log of the events described above: |
i have the same problem but in my case some link ID`s are Permanently Broken |
I've just compiled a mod update that mainly adds a Block Teleporter and some utility features. But alongside my efforts to make everything in the mod compatible with being teleported around, I also rewrote code related to the errors and crashes you had and they shouldn't happen anymore. You can download it here and the required library version here (the topmost .jar file under Assets). I may later add a beta release on curse forge as well. Issues that are probably not fixed yet are:
|
Our backup mechanism is pretty much the standard for minecraft servers. We ensure that minecraft isn't saving to its files, then we copy the files and afterwards we enable the saving. This way we don't copy files that are being written to at the same time causing corruption. If your mod is writing to files while the server saving is disabled this may cause corrupted backups however we have not rolled back to a backup since we added your mod so even if those files were corrupted during the backup copy phase this should not affect the live server. In case you are curious this is our backup script: https://pastebin.com/6Rb5n99C
The block at I'm not sure what was at I'll have to ask her when she gets back what was at that location.
Done, downloaded and updated; Seems to work so far, however at this time I have not tested much as JennyLeeP is the one that started using the mod the most. I'll have to ask her if things seem better at her base: We'll be testing the new version and I'll probably report back here. Thanks a bunch! |
So far ... well ... things didn't go too well. JennyLeeP was rebuilding here stuff as expected it would be broken but hopefully fixed after she rebuild everything (once again). She left for a little bit and while I tried to rejoin the server after a little bit away it decided to immediately crash with the following crashlog: The server log has all kinds of interesting lines such as:
But these were during the rebuilding. A second or two after my client connects the shit hits the fan and various things are barked in the console. I'm not sure what to make of the info Here is the full log: latest.log I'm not sure if JennyLeeP rebuild everything or just parts of her build. |
The block in question {x=29, y=63, z=-2229} that Noxy is referencing at my base was a control panel. I have rebuilt all 4 systems multiple time snow and I can confirm that the issues have not been resolved. Most of the issues I have witnessed so far happen on chunk unload. |
Deactivating the force chunk loading in forge prevented the game from crashing instantly |
So, now I got the Signal Link ID file to save alongside the regular world save whenever there were new connections added (previously it would only save during server shutdown). This should fix ID collisions in the future. I figured out that the new crash was indirectly caused by the Link ID collision as well, so I additionally improved the way these collisions are handled to prevent such crashes. Haven't made much progress with the invalid TileEntity thing except adding more debug logging. The problem is that I can't reproduce it in my dev environment or my test mod packs. According to your logs it happens only rarely. The circuit designer being affected confirms that it caused GUI insta-close issue, I made a workaround fix for that. New updates: |
I have the same problem with CD4017BE_lib-1.12.2-6.5.1.jar and RedstoneControl-1.12.2-0.3.1.3.jar:
I can not click on any buttons and levers on panels. It happens every day. |
Note: changes from CD4017BE_lib 6.6.3 may have solved #34
We've been experiencing strange behavior with the mod on our server. For the most part it seems to work fine when you start a new Redstone Control build but after the chunk has unloaded (server restart, people moving away from that chunk, or people logging off) the data of the blocks seem to be potentially invalid or forgotten (I'm not sure what is happening)?
The first indication of something wrong in our log is the following:
Where the last line is the person breaking and replacing the block that is behaving strangely (I think the error happens on breaking of the block).
This strange behavior also applies to the
Processor Assembly
andCircuit Designer
which on the client when opening the interface immediately closes the interface again until you break and replace those blocks.On one particular frustrating experience the server actually barked a bit more that just the three lines above:
This was during an attempted fixing of the strangely broken Redstone Control build. During this rebuild the client (JennyLeeP) also crashed with the following crash (multiple times):
https://pastebin.com/05UySxF5
After a bit of fiddling later the client (JennyLeeP) had to go for a minute and logged off. About a minute later after she logged back on the server crashed with the following crash:
https://pastebin.com/G2V4zus2
I'm not sure if this all is related to a single issue or multiple problems. Hope you can fix these as currently the mod seems unusable on our server.
The text was updated successfully, but these errors were encountered: