backups hangs on remote ssh if server is not available

[netac]

Running 'sftp -oServerAliveInterval=15 -oServerAliveCountMax=1 <email address hidden>' failed (attempt #1)
Running 'sftp -oServerAliveInterval=15 -oServerAliveCountMax=1 <email address hidden>' failed (attempt #2)
Running 'sftp -oServerAliveInterval=15 -oServerAliveCountMax=1 <email address hidden>' failed (attempt #3)
Running 'sftp -oServerAliveInterval=15 -oServerAliveCountMax=1 <email address hidden>' failed (attempt #4)

Maybe handy to check this ones before running the backup.

[Philippe Delodder (lodder)]

For each folder we could do a test if the connection is available?

[Rob Oakes (robertsoakes)]

Testing the folder would be good, but we need a better test connection than that we currently use. The current method will lead to the same sort of time out that the individual who reported the bug noticed. Reimplementing the test connection has been something I've been looking at for a while, but I still haven't figured out a good way to do without completely subclassing many of the duplicity backends.

[Philippe Delodder (lodder)]

Ok I'll have a look at it then ;) maby i can figure it out ;)
--
Philippe Delodder
<email address hidden>
http://www.delodder.be

2009/9/29 Rob Oakes <email address hidden>:
> Testing the folder would be good, but we need a better test connection
> than that we currently use.  The current method will lead to the same
> sort of time out that the individual who reported the bug noticed.
> Reimplementing the test connection has been something I've been looking
> at for a while, but I still haven't figured out a good way to do without
> completely subclassing many of the duplicity backends.
>
> --
> backups hangs on remote ssh if server is not available
> https://bugs.launchpad.net/bugs/438628
> You received this bug notification because you are a member of Time
> Drive - Devel, which is subscribed to Time Drive.
>
> Status in Time Drive: New
>
> Bug description:
> Running 'sftp  -oServerAliveInterval=15 -oServerAliveCountMax=1 <email address hidden>' failed (attempt #1)
> Running 'sftp  -oServerAliveInterval=15 -oServerAliveCountMax=1 <email address hidden>' failed (attempt #2)
> Running 'sftp  -oServerAliveInterval=15 -oServerAliveCountMax=1 <email address hidden>' failed (attempt #3)
> Running 'sftp  -oServerAliveInterval=15 -oServerAliveCountMax=1 <email address hidden>' failed (attempt #4)
>
> Maybe handy to check this ones before running the backup.
>

[netac (bart-osn)]

http://www.endperform.org/2009/01/python-example-check-for-open-ssh/

Lodder wrote:
> For each folder we could do a test if the connection is available?
>
> ** Changed in: time-drive
> Assignee: (unassigned) => Lodder (lodder)
>
> ** Changed in: time-drive
> Milestone: None => 0.3
>
>

[Rob Oakes (robertsoakes)]

The link that netac just submitted looks promising and might work as a solution for ssh connections. My first preference would be to use the existing Duplicity backend class, though. That would save from having to implement separate code for each of the various types of connections we support: ssh, webdav, ftp, etc.

[Philippe Delodder (lodder)]

Well it could be use to check if the port is open for every protocol,
I'll work out a way to test but I think we should consider this for
0.4 and we would need to change the ui also:
https://blueprints.launchpad.net/time-drive/+spec/rework-remote-path
--
Philippe Delodder
<email address hidden>
http://www.delodder.be

2009/9/29 Rob Oakes <email address hidden>:
> ** Changed in: time-drive
>   Importance: Undecided => High
>
> ** Changed in: time-drive
>       Status: New => In Progress
>
> --
> backups hangs on remote ssh if server is not available
> https://bugs.launchpad.net/bugs/438628
> You received this bug notification because you are a member of Time
> Drive - Devel, which is subscribed to Time Drive.
>
> Status in Time Drive: In Progress
>
> Bug description:
> Running 'sftp  -oServerAliveInterval=15 -oServerAliveCountMax=1 <email address hidden>' failed (attempt #1)
> Running 'sftp  -oServerAliveInterval=15 -oServerAliveCountMax=1 <email address hidden>' failed (attempt #2)
> Running 'sftp  -oServerAliveInterval=15 -oServerAliveCountMax=1 <email address hidden>' failed (attempt #3)
> Running 'sftp  -oServerAliveInterval=15 -oServerAliveCountMax=1 <email address hidden>' failed (attempt #4)
>
> Maybe handy to check this ones before running the backup.
>