-
Notifications
You must be signed in to change notification settings - Fork 190
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
SFTP statvfs extension fails when mod_vroot is in use #1792
Comments
Hmm. Interesting that a failed In the mean time, as a workaround, you might disable that extension, and see if that makes SSHFS happier:
|
Good hint. I already tried that without success, but I think I forgot to remount the share in order to start a new round of negotiation. I added the new setting and remounted the share now. The first impression is promising. Hopefully, tomorrow I have more information. I agree, it feels like #1780 and an improper path resolution when Thanks a lot for your quick response 😃. |
Hi @Castaglia,
I have attached the corresponding parts of the trace log. |
The interesting question for me is whether you were seeing similar path resolution issues, when using |
… Issue #1780 in the `statvfs(2)` system calls in mod_sftp.
Hopefully #1795 will at least make the |
Hi @Castaglia |
I built a version before the FSIO changes based on The trace log gives:
The sftp log gives:
The problem does not seem to introduced by the FSIO changes. I have also deactivated |
Could you provide the ProFTPD configuration you're using? I'm wondering if there's something else that might be blocking that And thanks for mentioning/confirming that this behavior occurs even with |
I set the This is my current configuration:
|
I also switched every folder and the corresponding file to mode |
@Castaglia You were right. The setting |
Ah, good. I'll add some debug logging in With that addition of |
First of all: Sorry for causing all the trouble. Our use case utilizes a lot of feature of the ProFTPD and the service is under heavy load. Even under those circumstances, your implementation does a really good job. Thank you very much for all your efforts spent over the years. I must do some more testing with SSHFS. Currently we are resorting to NFS. Unfortunately, SSHFS in combination with ProFTPD is really slow. We tested it against an OpenSSH server. I will give you the measurements in the next days. I think the main problem is that the ProFTPD does not implement the SFTP extension Maybe you have an idea. |
Glad to hear it! No worries about any trouble caused. I strive to keep ProFTPD very flexible, configuration-wise. Unfortunately that means a lot of edge cases and combinations which I don't always test well, and have to rely on reports like these to fix those edge cases. Mostly I wanted to confirm that the specific scope for this ticket, that of having a working
I will take a look into this, and at the OpenSSH source code, to see if implementing the |
…nt issue related to the `AllowStoreRestart` directive when used with SFTP. Add some debug logging in the checking of this configuration in mod_xfer, to make future diagnosis easier.
…nt issue related to the `AllowStoreRestart` directive when used with SFTP. (#1797) Add some debug logging in the checking of this configuration in mod_xfer, to make future diagnosis easier.
Thanks a lot @Castaglia. We did a new test run and the issue did not occur. It can be closed 👍. |
What I Did
I have mounted a share via SSHFS from our ProFTPD server, but the application is not able to write into the files even with the correct permissions set. The files are accessible and can be modified manually without any issues. The share is mounted via systemd:
When I do a
tail –f
on an existing file within the share, we get:I enabled the trace log and we see the following error in the log:
This is the full trace of the tail operation:
I am not sure, if the issue is related to the combination of using
mod_sftp
together withmod_vroot
or is related to #1780ProFTPD Version and Configuration
I am on the latest code base within this and the
mod_vroot
repository.Any help is greatly appreciated.
The text was updated successfully, but these errors were encountered: