You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Then, I lost the SSH connection because I lost WLAN connectivity because I entered suspend mode on my notebook. After that, I got this error on o.fs.listdir:
I was not able to get around this error without closing and restarting the Python interactive interpreter itself. Note that this error takes a while. Directly after loosing connectivity, or enabling VPN, the listdir call hangs multiple minutes before I loose patience. I tried unsuccessfully:
o.close()
o.fs.close() # no attribute "close"
Simply reopening the same SSH connection: fsspec.open("ssh://user@127.0.0.1").fs.listdir('/')
o.fs.client.close(). This fixes the hang, but now I get the Socket is closed error, which I also got after ~30 minutes (timeout?), with no way to reopen the same connection again.
quit ipython3 and reopen it: works fine
I am especially stumped as to why the last one did not work. It seems that SSH connections are somehow cached ad some layer.
Close this SSHClient and its underlying Transport.
This should be called anytime you are done using the client object.
Warning
Paramiko registers garbage collection hooks that will try to automatically close connections for you, but this is not presently reliable. Failure to explicitly close your client after use may lead to end-of-process hangs!
The fsspec SFTP implementation never calls this close method on the Client. As far as I can see, the client is only opened, never closed.
I would expect all other remote file systems to have similar issues, i.e., how can I ensure that the connection is properly closed?
Edit: I noticed that there is some kind of caching going on. This would explain why simply trying to reopen the SSH mount did not work.
The text was updated successfully, but these errors were encountered:
I did open an SSH file system and used it successfully:
Then, I lost the SSH connection because I lost WLAN connectivity because I entered suspend mode on my notebook. After that, I got this error on
o.fs.listdir
:I was not able to get around this error without closing and restarting the Python interactive interpreter itself. Note that this error takes a while. Directly after loosing connectivity, or enabling VPN, the listdir call hangs multiple minutes before I loose patience. I tried unsuccessfully:
o.close()
o.fs.close() # no attribute "close"
fsspec.open("ssh://user@127.0.0.1").fs.listdir('/')
o.fs.client.close()
. This fixes the hang, but now I get theSocket is closed
error, which I also got after ~30 minutes (timeout?), with no way to reopen the same connection again.I am especially stumped as to why the last one did not work. It seems that SSH connections are somehow cached ad some layer.
I also looked into the paramiko API specification and found this:
The fsspec SFTP implementation never calls this
close
method on the Client. As far as I can see, the client is only opened, never closed.I would expect all other remote file systems to have similar issues, i.e., how can I ensure that the connection is properly closed?
Edit: I noticed that there is some kind of caching going on. This would explain why simply trying to reopen the SSH mount did not work.
The text was updated successfully, but these errors were encountered: