setting '[ftpd]enabled = true' caused 'tahoe run' to fail silently #1360

New Issue

tahoe-lafs · 2011-02-04T23:41:17Z

davidsarah commented

2011-02-04 23:41:17 +00:00

I added the following, taken from source: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.

I added the following, taken from source: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.

tahoe-lafs added the

labels 2011-02-04 23:41:17 +00:00

tahoe-lafs added this to the undecided milestone 2011-02-04 23:41:17 +00:00

warner commented

2011-03-25 23:18:30 +00:00

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.