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
[Only affects wings 1.11.9 and up] Unable to mount an NFS "folder" inside the pterodactyl server volume. #5040
Comments
I can confirm this. I have an NFS4 mounted disk at /var/srv/gstorage1/wings1 that is owned by my pterodactyl:pterodactyl user. When attempting to start any server with 1.11.11, I get the same error. Reverting back to 1.11.8 works fine. I haven't looked at the code yet, but my first guess is that wings is doing something with privileges that is changing its effective user id, and the NFS server is denying access. |
Yes, I've also downgraded the node that runs the server with the mount. The node is private anyways so it does not really matter for now. I do not think it's something to do with the user id, although I am not an expert by any stretch of imagination, so please excuse me if I'm wrong - since I do not really know how the internal processes of Wings work. From what I've seen in the log: Also, Wings apparently has a problem with calculating the volume size:
|
This probably has to do with the fact that we are using the unix file stuff now as a change from the old filepath. I am going to assume they are treated differently because it's externally mounted and the io package doesn't know how to handle the mount properly. |
Where exactly on the filesystem are you mounting to? I think I might know what the issue is. |
I am mounting exactly to /var/lib/pterodactyl/volumes/volume_id/data, of course, where "volume_id" is replaced by the actual volume_id. Edit: Just in case it helps, I am using this mount under the minio egg, where I am mounting the data folder inside the pterodactyl volume to my NAS with NFSv4. Oh, and I do not have Squash enabled on my NFS server. |
I have a similar problem with this error that "file not exist" when checking file permission while starting on a NFS share with the new Wings version but I mount to "/var/lib/pterodactyl" instead, any ideas? |
Hello, just checking in, any updates? |
Hey, same problem here - just killed all my servers as I rolled out the update via Ansible. This also seemed to cause a lot of corrupt backups, idk how this came. Stupid mistake from my side. |
Current Behavior
After mounting an NFS share into a server's volume (for example /var/lib/pterodactyl/volumes/volume_id/data) and after starting the server, the server throws this error:
Error Event [68d61a4e-0836-4694-99c0-6094e2819970]: failed to chown root server directory during pre-boot process: server/filesystem: chown: failed to chown during walk function: stat 0c89372c-9a08-4cee-b516-7dd0d4db3bca/part.602: file does not exist
I tried on two separate nodes and got the same result.
Expected Behavior
Mount an NFS share into a server's volume (for example /var/lib/pterodactyl/volumes/volume_id/data) start the server, the server will change its permissions and everything works fine - this was the behaviour before wings version 1.11.9
Steps to Reproduce
Panel Version
1.11.5
Wings Version
1.11.11
Games and/or Eggs Affected
No response
Docker Image
No response
Error Logs
Is there an existing issue for this?
The text was updated successfully, but these errors were encountered: