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
11 is broken on NFS #735
Comments
strace reveals its not even using flock. its creating a LOCK file which suceeds
compared with a working tmpfs mount, i see no difference
|
I saw your message on Interestingly my production install has always used an NFS share and it seems to still be working correctly with If it helps, my mount point looks like this: nas:/homes/username on /home/username type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=x.x.x.x,local_lock=none,addr=y.y.y.y) Thanks for digging into this in more detail. |
i got a workaround that works for me. but i'm not sure if its safe yet. the underlying issue is that the way they use the db library (wrong, according to the libs dev), but i really dont know and my head hurts. i'll keep this open in the hopes that i remind myself to report after some production tests. |
Thank you for your work on this. It is quite a rabbit hole you've gone down. I agree that you should keep this issue open in hopes that a solution if found. Cross-linking your work with the leveldb folks for posterity: |
This issue has been automatically marked as stale because it has been inactive for 28 days. To reactivate the issue, simply post a comment with the requested information to help us diagnose this issue. If this issue remains inactive for another 7 days, it will be automatically closed. |
This issue has been automatically closed due to inactivity. If you are still experiencing problems, please open a new issue. |
Regression description
when upgrading from 10 to 11 and /data is on NFS you'll get
foundryvtt/foundryvtt#9766
mentiones this is due to the change to leveldb.
leveldb upstream works fine on NFS so this is suspicious.
according to discord this bug is intentional to cause issues for professional setups.
However, that's discord, and i feel like the more likely explanation is that they're wrapping leveldb in some exclusive locking to avoid accidentally starting multiple instances.
opening this issue here because it's more likely there's other people in this community with the same issue.
unfortunately their javascript is somewhat obfuscated, making it harder to find the issue.
Worked up to version
10
Stopped working in version
11
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: