/fg Save Crash [1.10.2 sponge]

[YOYOK9]

Was running tests on my lobby server and did a /fg save and I noticed my servers cpu usage drop to zero then a minute later the server just crashed.

Mods Folder:
SpongForge-1.10.2-2202-5.1.0-BETA-2053
Foxcore-0.10.3-208-server
Foxguard-0.20.2-api5-347-server

Nucleus-0.20.0.s5.101.10.2-plugin
Nucleusmixins-0.15.0-s5-mixins
projectportals-5.1.0-0.13.6
SimplePermissions-0.9.14
Spongycord-1.1.1
Worldedit-forge-mc1.10.2-6.1.4-dist

CrashReport:
http://pastebin.com/YvvJH9Wp

[YOYOK9]

Also just noticed that when my servers restart the handlers still appear when I created do /fg list handlers but when I do /fg list regions none of my regions appear/work but it says their names are still being used. (have default config/haven't changed anything)

[gravityfox]

This becomes irrelevant with the new storage system, but i'll leave this open until that's merged.

[d4rkfly3r]

So, after much time researching about this (see #67), this is our conclusion:

We determined that this error is caused by MapDB not being able to use Random Access Files. This only seems to really occur when the server is being run off of an NFS, which doesn't support this. I am unsure if you are using an NFS, and if you aren't then it probably is something like the server being out of storage space, or not having permissions. There is nothing that we can really do about this, although the upcoming FoxGuard releases no longer use MapDB, so should not have this problem.

If you are using a server hosting company, and you are getting this error, and they say that they are not using NFS to back it, please ask for all the details of whatever they are using and report it.

Thanks for your patience, and we apologize for the inconvenience this has caused.

[szmarczak]

Any updates?

[d4rkfly3r]

Hello!

Please be aware that many of the open issues may be closed soon, in preparation of the beta release of FoxGuard 2.0. We have not yet determined if we are going to create a new repo, or use the current one, however, if we use the current one, this issue will be closed.

If the issue occurs again at a later date in FoxGuard 2.0, please make a new issue and reference this one.

Thank you!
Joshua