Opened at 2011-02-04T23:41:17Z
Closed at 2020-01-16T20:21:47Z
#1360 closed defect (fixed)
setting '[ftpd]enabled = true' caused 'tahoe run' to fail silently
Reported by: | davidsarah | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | undecided |
Component: | code-frontend-ftp-sftp | Version: | 1.8.2 |
Keywords: | ftpd error | Cc: | |
Launchpad Bug: |
Description (last modified by warner)
I added the following, taken from docs/frontends/FTP-and-SFTP.rst#configuring-ftp-access, to a previously-working tahoe.cfg in order to enable the FTP frontend:
[ftpd] enabled = true port = tcp:8021:interface=127.0.0.1 accounts.file = private/ftp.accounts
then ran "path_to\bin\tahoe run ."
tahoe run exited immediately with no output. Commenting out enabled = true in the [ftpd] section allowed it to work again. The ftp.accounts file is working with SFTP.
This is on Windows Vista, using Tahoe v1.8.2. Running the test suite gives no test failures, and I've no reason to think that any of the dependencies are broken.
Change History (3)
comment:1 Changed at 2011-03-25T23:18:30Z by warner
comment:2 Changed at 2014-12-02T19:45:03Z by warner
- Component changed from code-frontend to code-frontend-ftp-sftp
- Description modified (diff)
comment:3 Changed at 2020-01-16T20:21:47Z by exarkun
- Resolution set to fixed
- Status changed from new to closed
"tahoe run" no longer exits silently in this case. Instead, it reports an error.
I'm guessing the root cause is probably a Twisted that lacks the necessary patch (Twisted-10.0 does not have it, Twisted-10.1 does). When the FTP server code detects this, it raises an AssertionError, which causes "tahoe run" to exit with rc=1. However, because stdout and stderr are being directed to an obscure logfile (logs/tahoesvc.log), you don't get to see the error message from the console. #355 is about fixing the logging problem. So in some sense, this is a duplicate of #355.