Connection times out and won't automatically reconnect

[dhinged]

When FileZilla's been sitting for a while and it times out (by server settings or whatever) and I double-click a folder or file, it just says Connection timed out in red and doesn't automatically reconnect. Is it possible to have it do this? Also, to have it automatically plop me in the same folder I am in?

[botg]

Please post a Log showing the problem.

[dhinged]

This requires a log? I thought this was normal behavior when the server times out. I'm trying to figure out how to have it auto-reconnect and go to the same folder I was last in.

[boco]

FileZilla does automatically reconnect at the next action. There seems to be something preventing this in your case, thus a log is required.

[dhinged]

Here is a typical example of the log (specific names and locations masked):

Status: Connecting to ###.###.###.###...
Response: fzSftp started
Command: open "root@###.###.###.###" 22
Command: Pass: ********
Status: Connected to ###.###.###.###
Status: Renaming '/var/www/html/***/html' to '/var/www/html/***/wordpress'
Command: mv "html" "wordpress"
Status: /var/www/html/***/html -> /var/www/html/***/wordpress
Error: Network error: Software caused connection abort
Error: Network error: Software caused connection abort
Status: Retrieving directory listing...
Command: cd "wordpress"
Error: Failed to retrieve directory listing

The mv line was before I left my computer; I came back and tried to go into the new wordpress folder; that's when I get the Failed message. Even if the server times me out, FileZilla should reconnect automatically, preventing me from clicking into the connection again manually every time.

[boco]

You are using SFTP. Using my SFTP server, I cannot reproduce it, unfortunately.

The error lines, were they already displaying when you came back? If not, the server either may not have notified the client about the connection drop, or the message got lost. FileZilla not knowing that it has been disconnected could prevent it from attempting reconnection.

[dhinged]

You are using SFTP. Using my SFTP server, I cannot reproduce it, unfortunately.

The error lines, were they already displaying when you came back? If not, the server either may not have notified the client about the connection drop, or the message got lost. FileZilla not knowing that it has been disconnected could prevent it from attempting reconnection.

Either way, can't FileZilla tell when I double-click a file or folder whether it needs to reconnect? Doesn't it ping the server and get a response indicating connection status that it can then use to reconnect?

[botg]

Doesn't it ping the server and get a response indicating connection status that it can then use to reconnect?

That would delay every command by half a second or more on long-latency connections.

[botg]

Just tried it myself. Connected to an SFTP server, disabled network adapter and got "Error: Network error: Software caused connection abort". Reenabled the network. Double-clicked a directory and it reconnected automatically.

[dhinged]

OK I discovered it will auto-reconnect if I double-click a file or folder, but not when I type in a filepath in the address bar on the remote server.

What it seems like it should do, no matter what command I send to the server, is if it gets a response that it's not connected, re-connect automatically and then run the command. If it gets a response back that it can't reconnect, then throw the error. What I'm saying is I shouldn't have to manually reconnect every time (if it can automatically reconnect) just because it isn't connected when I type in a filepath or double-click a file or folder. If it can't automatically reconnect, fine, I'll manually connect.

[botg]

OK I discovered it will auto-reconnect if I double-click a file or folder, but not when I type in a filepath in the address bar on the remote server.

I just tried it and could not spot a difference. It re-connects in both cases.

[dhinged]

So I just tried again; I had been away from FileZilla for a while, then went back and typed in /var/www/html into the "Remote site" address bar on the right, and got this output:

Status: Directory listing successful
Error: Network error: Software caused connection abort
Error: Network error: Software caused connection abort
Status: Retrieving directory listing...
Command: cd "/var/www/html"
Error: Failed to retrieve directory listing

You guys never run into the "Software caused connection abort" error? Maybe it's just the way our server is configured; we're using CentOS 6.3.

[boco]

No, I can't reproduce it. The only thing I could imagine is when the NIC/NIC driver doesn't report the link-down or connection-down state to the OS (correctly), making FileZilla think it's still connected. However, that was the case with the old 10MBit NICs, usually. Modern NICs should behave correctly.

[dhinged]

Well, I'm using Rackspace if that helps any. I can show you file settings if you want to tell me where I should look if it's something I can adjust server-side such as sshd settings or server/client timeout settings or something.

[dhinged]

No, I can't reproduce it. The only thing I could imagine is when the NIC/NIC driver doesn't report the link-down or connection-down state to the OS (correctly), making FileZilla think it's still connected. However, that was the case with the old 10MBit NICs, usually. Modern NICs should behave correctly.

Regardless of whether it thinks it's up or not, it should attempt to reconnect after it gives me the "Software caused connection abort".

Here's what just happened right now:

Error: Network error: Software caused connection abort
Status: Retrieving directory listing...
Command: cd ".."
Error: Failed to retrieve directory listing

It got the first error an hour ago while I way, then the second one just now when I clicked the .. folder on the remote server. If I then click one of the folders in the file tree in the box above that, then it reconnects. Did I just find the bug?