Custom Query (7794 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (121 - 123 of 7794)

Ticket Resolution Summary Owner Reporter
#4169 rejected "Failed Transfer" bug Denis Kristanda
Description

If maximum number of session (set on the server) is exceeded and the client get error "530 Not logged in, too many connection" , the "Queue Items" was wrongly moved to "Failed Transfer Tab" (bug) => The client should maintain the queue until got the connection or get other error message.

There is a 'closed' bug about the same item but the solution is not really fixing the bug: Ticket #3394: "Too many connections" wrongly marked "Failed Transfer" http://trac.filezilla-project.org/ticket/3394

That bug is closed with remark "Increase the number of retries and the reconnect delay in the settings dialog to avoid this problem."

The solution is not really solution because say I increase 3 retries with delay 30s each (total 90s) to 10 retries with 60s delay (total 600s), then after 600s the same thing will happen (not fixing the problem, just delaying the problem)

I use client version 3.2.0 and still see this daily.

Here is how I recreate the problem easily:

  1. Say the server maximum session from the same ip address is 8.
  2. Place on the server a folder with hundreds of file (big and small: 1kb size to 500MB size), say 200 or more files (make sure the transfer will last long enough to observed). I call it "folder A"
  3. Make a second folder "folder B" on server: just copy of 'folder a"
  4. Download "folder A" with OTHER FTP CLIENT. (I use cuteftp 8.3.2) just make sure I use some of the session handler)
  5. Now connect FILEZILA (set delay and retry to minimum) to server and download "folder B"
  6. The "queued files" tab is filled with the file list, but soon enough they are wrongly moved to "Failed Transfer" tab.

This 'bug' is quite annoying because I transfer a big size quite frequently that usually takes 2-3 hours download and unattended. With this bug, after 3 hours I come back to the console only find that some of the files are on "Failed Transfer" tab and have to wait another 1 or 2 hours to complete that transfer. (My current solution of this problem is to use cuteftppro that is not giving me the problem, but as open source fanatic I reckon FileZilla should be able to overcome this small problem - hope this can be solved before the trial period over.. ;-) )

NOTE: the problem is still occurring even only 1 client connect to the server (the above just to exaggerate) - the key is have to be a lot number of file with various mix of size

Thank you for the great product and great job for all the team !

LOG: .... Response: 331 User name okay, need password. Command: PASS Response: 530 Not logged in, only 8 sessions from same IP allowed concurrently. Error: Could not connect to server Status: Resolving address of [domainname] Status: Connecting to xx.xx.xx.xx:21... Response: 150 Opening BINARY mode data connection for [filename] ([size] Bytes). Status: Connection established, waiting for welcome message... Response: 220 FTP Server ready... Command: USER [username] Response: 331 User name okay, need password. Command: PASS Response: 530 Not logged in, only 8 sessions from same IP allowed concurrently. Error: Could not connect to server Status: Resolving address of [domainname] Status: Connecting to xx.xx.xx.xx:21... Status: Connection established, waiting for welcome message... Response: 220 FTP Server ready... Command: USER [username] Response: 331 User name okay, need password. Command: PASS Response: 530 Not logged in, only 8 sessions from same IP allowed concurrently. Error: Could not connect to server Status: Resolving address of [domainname] Status: Connecting to xx.xx.xx.xx:21... Status: Connection established, waiting for welcome message... Response: 220 FTP Server ready... Command: USER [username] Response: 331 User name okay, need password. Command: PASS Response: 530 Not logged in, only 8 sessions from same IP allowed concurrently. Error: Could not connect to server Status: Resolving address of [domainname] Status: Connecting to xx.xx.xx.xx:21... Status: Connection established, waiting for welcome message... Response: 220 FTP Server ready... Command: USER [username] Response: 331 User name okay, need password. Command: PASS Response: 530 Not logged in, only 8 sessions from same IP allowed concurrently.

.....

#5113 rejected log files need extra abilities ? dasd
Description

hello,

Logging System in filezilla server is very poor. It would be nice to log per user, per group, and per actions. I would like to see, from the log file, what files has a client download. Also it would be nice for the user to make his own perriod of every log file not only per day. I have read and some other ideas in other tickets. I think the Logging System needs a review...

thanks Chrysostomos Kolovos

#2683 wontfix public upload folder xpyr
Description

I want the ability to have an upload folder that when someone attempts to list anything in their, it will show as empty. Even though their could be files and directories already their, it should not show up when a list is performed. The user should be able to upload to this folder as well but can't see that the file they upload. Here is an example:

/ Can see the list of files/directories in here including upload. /upload/ Can't list anything in here unless they know the name of it. But when they do try to list, it doesn't give the ftp client a permission denied message, just shows nothing. /upload/test/ Can see everything and any directories in it but can't upload anything.

I've tried setting files to be write and not read with no list permissions, and even just write and no list permissions can still can't accomplish what I want to do.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.