FTP upload silently fails when nodes < happiness #1081

Closed
opened 2010-06-15 22:21:56 +00:00 by slush · 4 comments
slush commented 2010-06-15 22:21:56 +00:00
Owner

When I upload file using FTP (SFTP not affected), the upload successfully passes these phases:

*) Upload locally to tmp dir

*) Upload to helper (if used)

*) Converted to CHK_encoding (when using helper)

And then the FTP transfer silently fails, pretending that upload successfully finished. When I refresh the directory listing, the file isn't there.

Expected behaviour (from my view of common user):
FTP upload should finish after all phases of tahoe upload.

Used software: Node - Windows7 with patched Twisted. Helper - Debian without patch.

I tried scenario many times with different files and happiness and both with or without helper.

Note: Using SFTP in same scenario (nodes < happiness) leads to RemoteException in SFTP client which indicates that something went wrong.

How to reproduce:

a) Wait until count of nodes is less than current happiness in config.

b) or set happiness in config to something large.

Reproducibility: always

When I upload file using FTP (SFTP not affected), the upload successfully passes these phases: *) Upload locally to tmp dir *) Upload to helper (if used) *) Converted to CHK_encoding (when using helper) And then the FTP transfer silently fails, pretending that upload successfully finished. When I refresh the directory listing, the file isn't there. Expected behaviour (from my view of common user): FTP upload should finish after all phases of tahoe upload. Used software: Node - Windows7 with patched Twisted. Helper - Debian without patch. I tried scenario many times with different files and happiness and both with or without helper. Note: Using SFTP in same scenario (nodes < happiness) leads to [RemoteException](wiki/RemoteException) in SFTP client which indicates that something went wrong. How to reproduce: a) Wait until count of nodes is less than current happiness in config. b) or set happiness in config to something large. Reproducibility: always
tahoe-lafs added the
code-frontend
major
defect
1.7β
labels 2010-06-15 22:21:56 +00:00
tahoe-lafs added this to the undecided milestone 2010-06-15 22:21:56 +00:00
tahoe-lafs modified the milestone from undecided to soon 2010-06-15 23:10:18 +00:00
tahoe-lafs changed title from FTP upload silently fails when nodes<happiness to FTP upload silently fails when nodes < happiness 2010-06-15 23:10:18 +00:00

I think we should treat this as a v1.7 issue as far as documenting that it can happen and instructing people on how to avoid it or to diagnose that this is the cause of their problem (but not treat it as a v1.7 issue as far as changing any code to improve it).

So, ideally we would update some docs, probably in source:docs/frontends/FTP-and-SFTP.txt, explaining that if you have insufficient servers for servers-of-happiness then uploads will silently fail. (This will be along with docs changes per #1024 and #1082 which will hopefully make users more aware of the servers-of-happiness issues in general.) The FTP-and-SFTP docs should point users to other docs such as running.html / using.html which explain how to set up multiple servers, how to see how many servers you have set up, how to configure servers-of-happiness, and how to see what your current servers-of-happiness configuration is.

Then, having written this doc, we'll move this ticket from the "1.7" Milestone to the "soon" Milestone and ship Tahoe-LAFS v1.7 final!

Then we'll see if we can somehow change our code to signal failure reliably to the user of an FTP or SFTP frontend so that they can detect and diagnose failures.

I think we should treat this as a v1.7 issue as far as documenting that it can happen and instructing people on how to avoid it or to diagnose that this is the cause of their problem (but not treat it as a v1.7 issue as far as changing any code to improve it). So, ideally we would update some docs, probably in source:docs/frontends/FTP-and-SFTP.txt, explaining that if you have insufficient servers for servers-of-happiness then uploads will silently fail. (This will be along with docs changes per #1024 and #1082 which will hopefully make users more aware of the servers-of-happiness issues in general.) The FTP-and-SFTP docs should point users to other docs such as running.html / using.html which explain how to set up multiple servers, how to see how many servers you have set up, how to configure servers-of-happiness, and how to see what your current servers-of-happiness configuration is. Then, having written this doc, we'll move this ticket from the "1.7" Milestone to the "soon" Milestone and ship Tahoe-LAFS v1.7 final! Then we'll see if we can somehow change our code to signal failure reliably to the user of an FTP or SFTP frontend so that they can detect and diagnose failures.
zooko modified the milestone from soon to 1.7.0 2010-06-17 04:32:46 +00:00
davidsarah commented 2010-06-19 03:02:13 +00:00
Author
Owner

Documented in changeset:29a9059c94eef955.

Documented in changeset:29a9059c94eef955.
tahoe-lafs modified the milestone from 1.7.0 to 1.7.1 2010-06-19 03:02:13 +00:00
tahoe-lafs modified the milestone from 1.7.1 to 1.8.0 2010-07-17 06:04:12 +00:00
zooko modified the milestone from 1.8.0 to soon 2010-08-14 06:55:47 +00:00
tahoe-lafs modified the milestone from soon to 1.9.0 2011-01-13 06:01:04 +00:00

not making it into 1.9

not making it into 1.9
warner modified the milestone from 1.9.0 to 1.10.0 2011-10-13 17:06:40 +00:00
warner added
code-frontend-ftp-sftp
and removed
code-frontend
labels 2014-12-02 19:43:35 +00:00

The FTP frontend has been removed.

The FTP frontend has been removed.
exarkun added the
wontfix
label 2021-01-15 20:27:37 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#1081
No description provided.