Opened 17 years ago

Last modified 11 years ago

#3470 closed Bug report

Edited files get lost on server timeout

Reported by: polajoo Owned by:
Priority: normal Component: Other
Keywords: Cc: polajoo, Alexander Schuch, Tim Kosse
Component version: Operating system type:
Operating system version:

Description

When editing a file, if you save the file, switch back to filezilla, the client will then re-upload the file.

However, if it is unsuccessful, it puts it in the "failed" queue but appears to delete the file, because you cannot then re-upload the file.

To recreate:

  1. Right-click and edit a file
  2. Make some changes, save the file
  3. Switch back to filezilla
  4. Disconnect your net connection
  5. Click Yes to upload the file
  6. Wait for it to be put in "failed" queue
  7. Re-connect your net connection
  8. Try and re-queue the file, it will fail

Attachments (1)

Untitled-1.jpg (34.1 KB ) - added by polajoo 17 years ago.
Error message when you try and re-queue a file you've just edited and saved

Download all attachments as: .zip

Change History (9)

comment:1 by Alexander Schuch, 17 years ago

Which version of FileZilla are you using? And which platform are you running it at?

comment:2 by polajoo, 17 years ago

Latest (3.0.8.1) on Windows XP.

This has happened since v3 came out, but I've only just had the inclination to report it today after losing a substantial amount of coding. My own fault, but lost nonetheless. :)

A workaround is just to up the max retries on failure, but I thought you'd appreciate the report anyway.

comment:3 by Alexander Schuch, 17 years ago

Current version is FileZilla 3.0.9.1, but according to the changelog, nothing regarding your issue has been changed. But it might be worth a try anyway.

by polajoo, 17 years ago

Attachment: Untitled-1.jpg added

Error message when you try and re-queue a file you've just edited and saved

comment:4 by polajoo, 17 years ago

Sorry - I took the fact that the program didn't prompt me to upgrade meant I was running latest.

Just upgraded to 3.0.9.1 and can confirm behaviour is identical.

Error message when you try and re-queue the file for upload is

"Not all items could be requeued for viewing / editing."
File Added: Untitled-1.jpg

comment:5 by polajoo, 17 years ago

Have just seen that you've added that message to the bugs page, but it doesn't tell me where to pick up the logs from.

I've just created a log session, but can't find a .log file or similar in the program files dir.

Where do I pick it up from?

comment:6 by Alexander Schuch, 17 years ago

A message log is available in the message pane at the upper part of FileZilla. You have to copy and paste the text from there - logging to file is not yet supported.

comment:7 by polajoo, 17 years ago

Ok.

Trace: CFtpControlSocket::FileTransfer()
Status: Starting download of /wwwroot/style.css
Trace: CFtpControlSocket::ParseSubcommandResult(0)
Trace: FileTransferSubcommandResult()
Trace: CFtpControlSocket::SendNextCommand()
Trace: FileTransferSend()
Trace: CFtpControlSocket::SendNextCommand()
Trace: CFtpControlSocket::TransferSend()
Command: PASV
Trace: CFtpControlSocket::OnReceive()
Response: 227 Entering Passive Mode (84,18,207,6,14,146))
Trace: CFtpControlSocket::TransferParseResponse()
Trace: CFtpControlSocket::SendNextCommand()
Trace: CFtpControlSocket::TransferSend()
Command: RETR style.css
Trace: CTransferSocket::OnConnect
Trace: CFtpControlSocket::OnReceive()
Response: 150 Opening ASCII mode data connection for style.css (3102 Bytes).
Trace: CFtpControlSocket::TransferParseResponse()
Trace: CFtpControlSocket::SendNextCommand()
Trace: CFtpControlSocket::TransferSend()
Trace: CTransferSocket::OnClose
Trace: CTransferSocket::TransferEnd(1)
Trace: CFtpControlSocket::TransferEnd()
Trace: CFtpControlSocket::OnReceive()
Response: 226 Transfer complete.
Trace: CFtpControlSocket::TransferParseResponse()
Trace: CFtpControlSocket::ResetOperation(0)
Trace: CControlSocket::ResetOperation(0)
Trace: CFtpControlSocket::ParseSubcommandResult(0)
Trace: FileTransferSubcommandResult()
Trace: CFtpControlSocket::ResetOperation(0)
Trace: CControlSocket::ResetOperation(0)
Status: File transfer successful
Trace: CRealControlSocket::OnClose()
Error: Disconnected from server
Trace: CFtpControlSocket::ResetOperation(66)
Trace: CControlSocket::ResetOperation(66)
Trace: CRealControlSocket::OnClose()
Error: Disconnected from server
Trace: CFtpControlSocket::ResetOperation(66)
Trace: CControlSocket::ResetOperation(66)
Status: Resolving IP-Address for ftp.domainname.co.uk
Trace: ControlSocket.cpp(1003): CRealControlSocket::ContinueConnect(0) m_pEngine=0p12de558 caller=0p1311ca0
Error: Invalid hostname or host not found
Trace: CFtpControlSocket::ResetOperation(70)
Trace: CControlSocket::ResetOperation(70)
Error: Critical error
Error: Could not connect to server
Status: Resolving IP-Address for ftp.domainname.co.uk
Trace: ControlSocket.cpp(1003): CRealControlSocket::ContinueConnect(0) m_pEngine=0p12de558 caller=0p1311ca0
Error: Invalid hostname or host not found
Trace: CFtpControlSocket::ResetOperation(70)
Trace: CControlSocket::ResetOperation(70)
Error: Critical error
Error: Could not connect to server
Status: Resolving IP-Address for ftp.domainname.co.uk
Trace: ControlSocket.cpp(1003): CRealControlSocket::ContinueConnect(0) m_pEngine=0p12de558 caller=0p1311ca0
Error: Invalid hostname or host not found
Trace: CFtpControlSocket::ResetOperation(70)
Trace: CControlSocket::ResetOperation(70)
Error: Critical error
Error: Could not connect to server

The problem with the log is it does not show the delete operation that is done to the file, or the fact that it has found a file that's due for re-upload, so the log doesn't really show much.

comment:8 by Tim Kosse, 17 years ago

Thanks for reporting. This issue has been fixed in the SVN
repository and will be available with the next version.

Note: See TracTickets for help on using tickets.