sbackup over ssh not working

Asked by Steve Cohen

I have two PCs, each running Ubuntu 10.04 and sbackup, one is mine, the other, my wife's.

I wish to use sbackup so that each backs up to the other, using ssh, so I have some protection against disk crashes.

What I find is that it works one way but never the other.

Each of us has home directories on the other's computer, that is
/home/steve
and
/home/martha

and under each is a backup subdirectory with owner-write permissions.

Steve's computer is 192.168.1.41 and Martha's is 192.168.1.40.

On Steve's PC, the sbackup setup is this:

ssh://steve:stevespassword@192.168.1.40/home/steve/backup

and on Martha's it is :

ssh://martha:marthaspassword@192.168.1.41/home/martha/backup

It works flawlessly from Steve's PC to Martha's, but never from Martha's to Steve's.

Sbackup-config always tells me that it lacks permissions, yet there is no reason that should be the case.

Furthermore raw ssh and sftp work fine from Martha's machine to Steve's.

I see nothing in Steve's logs when these connection attempts fail.

What could account for these symptoms?

Question information

Language:
English Edit question
Status:
Expired
For:
sbackup Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Jean-Peer Lorenz (peer.loz) said :
#1

Thank you for using SBackup and for taking the time reporting this issue.

>It works flawlessly from Steve's PC to Martha's, but never from Martha's to Steve's.
Since it basically works, I don't think it is directly related to or caused by sbackup. Please double check your permission settings and ssh configuration.

Revision history for this message
Steve Cohen (stevecoh1) said :
#2

On 01/02/2011 11:53 AM, Jean-Peer Lorenz wrote:
> Your question #138516 on Simple Backup changed:
> https://answers.launchpad.net/sbackup/+question/138516
>
> Status: Open => Answered
>
> Jean-Peer Lorenz proposed the following answer:
> Thank you for using SBackup and for taking the time reporting this
> issue.
>
>> It works flawlessly from Steve's PC to Martha's, but never from Martha's to Steve's.
> Since it basically works, I don't think it is directly related to or caused by sbackup. Please double check your permission settings and ssh configuration.
>
Been there, done that, sorry.

I would not agree that "it basically works".

In one direction it works perfectly. In the other direction it doesn't
work at all.

As I said in my original posting, using ssh I am able to create a file
in the same directory as sbackup is trying to create one in. I am able
to sftp into the same directory. What part of that suggests to you that
ssh settings or permissions might be at fault?

Perhaps you might be able to help me by telling me how to turn on any
logging that would let me see what is going on.

Revision history for this message
Launchpad Janitor (janitor) said :
#3

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Jean-Peer Lorenz (peer.loz) said :
#4

Hello sTiVo,

sorry for the long delay. Any news on this?

You could set the output level to 'debug' when configuring your profile and post the resulting log. How do you authenticate? Using certificates or username and passwords?

> In one direction it works perfectly.
What I was meant to say was that backups over ssh obviously do work, don't they.

Thanks for your help.

Revision history for this message
Jean-Peer Lorenz (peer.loz) said :
#5

Status changed because more information were requested.

Revision history for this message
Steve Cohen (stevecoh1) said :
#6

Thanks for getting back to me.

> You could set the output level to 'debug' when configuring your profile and post the resulting log.

I don't see this option in the Simple Backup Config UI. Is this done by editing a configuration file? If so, please provide details. If I can get a log I will be happy to post it.

>How do you authenticate? Using certificates or username and passwords?
Passwords supplied in the ssh url, i.e. ssh://user:password@192.168.1.40/home/user/backup

>What I was meant to say was that backups over ssh obviously do work, don't they.
In other words, you mean to say that it does work in at least SOME if not ALL situations? Right?

Revision history for this message
Jean-Peer Lorenz (peer.loz) said :
#7

You can set the level of output on the 'Report' tab withing sbackup-config-gtk. Choose 'debug' level in order to collect maximum information. Another question: What is the _exact_ error message printed out when connecting fails?

> Passwords supplied in the ssh url, i.e. ssh://user:password@192.168.1.40/home/user/backup
That's a pretty common usecase.

> In other words, you mean to say that it does work in at least SOME if not ALL situations? Right?
No, please don't get me wrong. I'm taking your issue serious and hope that we can find a solution for this. The (original) question or thought was: do backups over ssh (using sbackup) work at all? If so (and according to you it does work in one case without a flaw) the problem is more complex than to blame sbackup. Ok, enough explanations.

Unfortunately, I've no clue what could cause your issue or how to continue from here...I guess we should have a look at your logs at first.

Best regards.
jean-peer

Revision history for this message
Steve Cohen (stevecoh1) said :
#8

I think we understand each other but there is a bit of a language problem. I now understand that you are taking the issue seriously, although your previous wording had led me to doubt that. But enough of that.

Now, I wonder if I am using the same version of the software that you are referring to. You mention sbackup-config-gtk.

The Ubuntu 10.04 launcher for what I am running has this command line:

     su-to-root -X -c /usr/sbin/simple-backup-config

and it identifies itself as Version 0.10.4

In this version I do not see a "Report" tab. So I still don't know how to get a log.

Revision history for this message
Launchpad Janitor (janitor) said :
#9

This question was expired because it remained in the 'Needs information' state without activity for the last 15 days.

Revision history for this message
Steve Cohen (stevecoh1) said :
#10

Not finished. As you can see, the last comment was mine and I'm still waiting for an answer to that question. Thanks.

Revision history for this message
Launchpad Janitor (janitor) said :
#11

This question was expired because it remained in the 'Open' state without activity for the last 15 days.